Security overview

How we protect your data.

TradeScale Plus stores commercially sensitive dealer data and personal data about your customers. This page is the honest, technical account of how we do it: what we encrypt, where it lives, who else touches it, and what we commit to.

Last updated: 15 October 2026 · Document owner: Ashley Mark Evans, Director, Trade Scale Plus Ltd

Where your data lives

All customer data, dealer data and account credentials are stored in Supabase, a managed PostgreSQL platform. The database is hosted in Ireland (AWS eu-west-1), within the European Economic Area, in a jurisdiction with a UK GDPR adequacy decision. Photos that dealers take for buyers through the website assistant are stored in Cloudflare's storage. Some providers in the United States process data to deliver the service; they are listed under Sub-processors below.

Postgres 17.6 EU-West-1, Ireland AES-256 at rest TLS in transit

Encryption

At rest

Database storage is encrypted with AES-256, the algorithm used by banks and government. Encryption keys are managed by Supabase and AWS Key Management Service. Storage volumes are encrypted before any data is written, so the database is never stored on disk unencrypted.

In transit

Every connection between your browser, our servers and the database is encrypted with TLS (HTTPS). Certificates are managed automatically with auto-renewal.

Per-dealer isolation

Our platform is multi-tenant: several dealers' data lives in the same database, and every table carries a dealer_id column. Separation works at two levels. Most of the dashboard, and all of the chat assistant on dealers' websites, run through our server, which checks every request against the signed-in user's dealer before it reads or writes anything. For anything a dashboard reads straight from the database, a Row-Level Security (RLS) policy enforced by Postgres itself adds a second lock. Row-Level Security is switched on for every table.

RLS policies look like this in practice:

create policy customers_dealer_read on customers for select using ( is_super_admin() or dealer_id in ( select dealer_id from dealer_users where user_id = auth.uid() ) );

With that policy, Dealer A's user cannot query Dealer B's rows directly from the database.

The chat assistant on dealers' websites runs on our server rather than in a dealer's login, so there the separation is done in our code: every lookup it makes (the stock, the conversation so far, bookings) is filtered by the one dealer it is answering for, and it is only ever given that dealer's data.

Authentication & access

Sub-processors

To deliver the service, we share specific data with the following sub-processors. Each processes data for us under its own data processing terms. The full list (and any changes) is maintained on this page and notified to dealers in advance.

Sub-processor Purpose Data shared Location
Supabase Primary database and authentication All application data Ireland (EU)
Stripe Payment processing Billing email + subscription metadata. Card details go direct to Stripe; we never see them. Ireland (EU)
Anthropic AI that writes the website assistant's replies (Claude) The visitor's messages, the dealer's stock and details, and any contact details given in the chat United States
Railway Application hosting (our Node.js server) Data passing through our server, and server logs United States
Cloudflare CDN, DDoS protection, edge TLS termination, and storage for photos dealers take for buyers (R2) HTTP traffic metadata; vehicle photos Global edge
Resend Email delivery: enquiry, booking and alert emails to dealers Email content, including the buyer's contact details United States
Cross-border transfer disclosure

Some sub-processors are based in the United States (Anthropic, Railway and Resend), and Cloudflare's network is global. When personal data is transferred to them, we rely on the transfer safeguards in their data processing terms, such as the UK International Data Transfer Addendum to the EU Standard Contractual Clauses or, where the provider is certified, the UK extension to the EU-US Data Privacy Framework. Copies of each provider's terms are available on request. Each uses the data only to provide its service to us, and our AI provider's commercial terms do not allow it to train its models on our data.

Payment data

We never see your card details. Stripe operates the entire payment flow: when you enter your card on a Stripe-hosted checkout page, the data goes directly to Stripe and never passes through our servers. Stripe is PCI-DSS Level 1 certified. We only receive a Stripe customer reference and subscription metadata.

Backups & recovery

Breach notification

If we discover a personal data breach that affects you or your customers, we will:

Your rights as a dealer

Data portability

You can export your leads as a CSV file from your dashboard at any time, and we'll send your conversations, enquiries and bookings in a standard format (CSV or JSON) on request. If you ever stop using TradeScale Plus, you take your data with you.

If we ever shut down

If Trade Scale Plus Ltd ceases to operate the service, we commit to giving paying customers at least 90 days' notice and providing a full data export in standard formats. You're never locked in.

Right to erasure

Either you or your customers can request deletion of personal data. We honour requests within 30 days, deleting the data from our database (backups expire within 7 days), except where the law requires us to keep it. Copies that have already left our systems, such as a lead email in your own inbox, are yours to delete; our email and AI providers keep their own records for a limited period under their terms (our AI provider deletes within 30 days).

What we don't claim

Trade Scale Plus Ltd is a young company. We want to be straight about what we have and haven't achieved:

We list these because we would rather be straight with you about where we are.

Reporting a security issue

If you discover a security vulnerability, please report it to security@tradescaleplus.com. We commit to acknowledging within 48 hours and to keeping you informed of remediation. We will not pursue legal action against good-faith researchers who:

Compliance summary