What we store, for how long, and what we never do with it.

The short version

• We store the order data you send us, because comparing it is the entire product.
• We do not train any model on your data, and we do not sell or share it.
• We never receive card numbers. Relay handles charge references, not payment credentials.
• You can ask for an export or a deletion at any time and we will do it by hand within seven days.

Who is who

If you are a Relay customer, you are the controller of the traveller data you send, and Relay is a processor acting on your instructions. If you are a traveller whose booking passed through a Relay customer, your relationship is with them; we will forward any request you send us to the relevant customer.

What we collect

Order data you send to the API

For each order: your own order identifier, and the three views of it — amounts, currencies, routes, departure dates, passenger names, refund and capture status, processor and supplier names, and charge identifiers. Passenger names and travel dates are personal data. We ask for them because a name or date mismatch is one of the failures Relay exists to detect; if you can detect what you need without sending names, send fewer fields — a field you omit is never treated as a mismatch.

Account data

Your email address, an optional display name and company name, and which authentication provider you used. Passwords, when used, are hashed by Supabase Auth and never visible to us.

Operational data

API key hashes, key last-used timestamps, webhook endpoints and their signing secrets, and records of raw provider webhooks when you connect a provider.

Enquiries

If you use the contact or API-access forms, we keep what you typed so we can reply.

What we do not collect

• No card numbers, CVVs, or bank credentials. Relay sees a charge reference such as ch_1P…, never the instrument behind it.
• No third-party analytics, advertising, or tracking pixels. There is no Google Analytics on this site. We considered it and decided against putting a third-party tracker on a product that handles other people's payment data.
• No cookies for advertising. The only browser storage we use is the session token that keeps you signed in, and a local preference or two in the console.

How long we keep it

• Orders — for as long as your account is open, so that history stays queryable. Sandbox data may be cleared periodically.
• Raw provider webhook payloads — kept append-only so a normalisation bug can be replayed rather than losing evidence. These can be purged on request.
• Account data — until you delete the account.
• Enquiries — until they are handled, then as long as is useful for follow-up.

On account deletion, order data is removed by database cascade — deleting the workspace deletes its orders, keys, webhooks and connections with it.

Who can see it

Your workspace's data is readable only by members of that workspace, enforced by row-level security in PostgreSQL (see Security). No other customer can query it. Relay staff — currently one person — can technically reach the database for support and debugging; we access customer data only when needed to fix something, and we would rather you ask us to look than assume we already have.

Subprocessors

• Supabase — database, authentication and function hosting (US East).
• Cloudflare — static site hosting and DNS.
• Stripe — subscription billing, if and when you pay us. Stripe handles card details directly; they never pass through Relay.

We will update this list before adding another one.

International transfers

Data is processed in the United States. If you are in the EEA or UK and that matters for your compliance position, raise it before sending live data — a different deployment region is a conversation, not a blocker.

Your rights

Access, correction, export, deletion, and objection. Email yduan2435@gmail.com or use the contact form. We respond within seven days and confirm in writing when it is done. There is no charge and no form to fill in.

Changes

If we change anything material, we will email account holders rather than quietly updating the date at the bottom of this page.

Last updated 1 September 2026. Contact: yduan2435@gmail.com