← All legal documents

Who else handles your data

Draft, published while still under review. It may change before launch. Written against docs/legal/data-inventory.md.

Last updated: 21 September 2026 · Controller: Delphi Commerce Limited, 69 Shenley Avenue, Ruislip HA4 6BT · Contact: [email protected]

The processors

Every company below handles some part of your data on our instructions. Nobody else does, and we do not sell your data or use it for advertising.

WhoWhat they holdWhereDPA statusTheir terms
NeonThe whole databaseLondon (eu-west-2), encrypted at restStandard terms acceptedneon.com/dpa
Fly.ioThe running code, and debug page captures on a London volumeLondon (lhr)Standard terms acceptedfly.io/documents
KernelThe browser that signs in to TfL, and its cookies, one profile per customerUK egressStandard terms acceptedonkernel.com/docs/dpa
ResendEmail addresses and message contentsEU regionStandard terms acceptedresend.com/legal/dpa
StripeName, billing address, payment details and card detailsUnited KingdomStandard terms acceptedstripe.com/legal/dpa
Transport for LondonThe claim itselfUKNot applicable: TfL receives the claim, it does not process data for ustfl.gov.uk/corporate/privacy-and-cookies

Transport for London is in the table because your data reaches it, not because it works for us. When we submit a claim, TfL is the recipient and decides for itself what to do with what it is sent. That is the point of the service.

"Standard terms accepted" means the processor publishes a data processing agreement that its own terms incorporate, and which applied when the account was opened. It is not a separately negotiated contract, and none of these five has signed one with us.

What that means in practice

Neon holds everything the service knows: your email address, your card label, your journeys, our delay estimates, your claims and the audit trail. It is a London region and encrypted at rest.

Fly.io runs the code, and the debug page captures live on a volume attached to it. Those captures are copies of your own signed-in TfL pages, so they are treated as personal data and deleted after 30 days.

Kernel provides the cloud browser you sign in to TfL through, and keeps that browser's cookies in a profile of your own, separate from every other customer's, so the one sign-in you give holds for the whole check: the pages we read and any claim we file. It does not save you from signing in next time. TfL asks for a fresh sign-in and a new text code every time, and we cannot start a check without you. The profile holds a live TfL session while a check runs. Closing your account deletes it.

Resend sends the emails: the sign-in link, the message telling you a check is ready for your sign-in, and the results of a claim. It sees your email address and what we wrote to you. Its EU region is the only processing in this table outside the United Kingdom, and the safeguard for that transfer is the standard contractual clauses in Resend's data processing agreement, as amended by the UK Addendum.

Stripe

The Stripe account went live on 18 September 2026.

The billing code is built: Checkout, a subscription per card, and the webhook that keeps our records in step with Stripe's. It has been tested against a Stripe sandbox, not against real cards, so nobody has been charged and Stripe holds nothing for this service today. The row above describes what Stripe will hold once billing goes live for customers: your name, your billing address, your payment details and your card details.

Those never reach our servers. You would enter a card on Stripe's own page, and what comes back to us is whether the subscription is paid, not the card.

Changing this list

If we add a processor, or move one, we will tell you by email before it starts handling your data.