Retention schedule
Draft, published while still under review. It may change before launch. Written against what the code actually does (docs/legal/data-inventory.md).
Last updated: 21 September 2026 · Controller: Delphi Commerce Limited, 69 Shenley Avenue, Ruislip HA4 6BT · Contact: [email protected]
What this covers
Everything the service holds about you, how long we hold it, and what makes it go when the time comes. It is the detail behind the "How long we keep it" section of our privacy policy.
Where a period is kept by something the service does automatically, the last column says so. Where it depends on somebody doing it, the last column says that instead, because a schedule you cannot check is not worth reading.
The schedule
| What we hold | How long we keep it | What makes that happen |
|---|---|---|
| Your email address | As long as you have an account, and then six years | Closing your account keeps the address, because the claim records and the authority trail we keep afterwards are tied to it. Six years after closure the same automatic sweep deletes it, here and in the sign-in system. |
| Your Oyster or contactless card number | As long as you have an account | Closing your account deletes it, together with the journeys it was read from. |
| Your journey history: the date, time, start and end station, fare and card of each journey | 8 weeks | A sweep that runs when our worker starts and again after every status check, so it cannot be left undone. A check also reads at most 8 weeks back, which is all TfL itself keeps, so nothing older ever reaches us in the first place. Closing your account deletes all of them without waiting for the sweep. |
| Copies of the TfL pages we read during a check, and the CSV files we download from them | 30 days | A sweep that runs when our worker starts and again after every status check, so it cannot be left undone. Closing your account deletes them without waiting for it. |
| Our estimate of whether a journey was delayed, and the evidence behind it | With the journey it describes | Deleted in the same sweep that removes the journey, and on the same transaction, so an estimate never outlives what it describes. |
| Your refunds, including TfL's own record of how long each delay was | Kept after your account closes, and finally deleted six years after closure | Deliberate. You and TfL may both need the record later, so nothing deletes it when you close your account. At six years a sweep deletes it, with everything else below and the account itself. That sweep runs when our worker starts and again after every status check, so it cannot be left undone. |
| Your standing authority: the wording you accepted, when you accepted it, and the limits you set | Six years after your account closes | Kept through account closure, then deleted by the same automatic sweep, on the same transaction as the records above. |
| The record of every delay we showed you, every approval you gave, every claim we submitted and everything we refused to do | Six years after your account closes | The same sweep, the same transaction. Until then that record is only ever added to, never edited. |
| The progress of a check, including the live-view link while one is running | The link is cleared the moment the check ends | Cleared on the path where a check finishes and on the path where it fails, so it cannot be left sitting in our database. The progress record itself goes when you close your account. |
| A sign-in in progress: hashed IP address, state and the live-view link | The link is cleared the moment the sign-in ends; the row itself for 30 days | The link is cleared automatically, the same way a check's is. The same sweep that runs when our worker starts and after every status check gives up on a sign-in nobody finished, deletes the browser profile behind it on the next sweep after that, and deletes the row itself 30 days after the sign-in ended. |
| Your membership on each card: which subscription pays for it, and whether it is active, past due, cancelling or ended | As long as the membership exists | Closing your account deletes it, together with the Stripe subscription it mirrors. |
| Your Stripe Customer id | As long as you have a subscription | Closing your account cancels every subscription, deletes the Stripe Customer, and clears the id. Stripe keeps its own record of the payments for as long as its own legal retention requires, regardless of what we do. |
Our copies of Transport for London's published network status and station information hold nothing about you. They are the same for every account, so no retention period applies to them.
Closing your account
Ask us to close your account and we do all of the following.
What we delete
- The browser profile holding your signed-in TfL cookies, any browser still running on it, and any sign-in connection left over from an earlier version of the service. Once those are gone there is no route from us into your TfL account.
- Everything in your folder on our server: the browser profile, the saved cookies, the CSV files we downloaded and the copies of the pages we read.
- Your journeys, your card, our delay estimates, the approvals you gave and the records of the checks that read them.
- Your membership on every card. Before it goes, we cancel the Stripe subscription behind it and delete the Stripe Customer record, so you stop being billed and we stop holding a Stripe id that points at you. Stripe keeps its own record of what you paid for as long as its own legal retention requires; that is between you and Stripe, and closing your account with us does not reach it.
What we keep, and for six years only
- Your refunds: what we asked TfL for, and what TfL decided. You and TfL may both need this later.
- The record of who authorised what, and of anything we refused to do.
- The wording of any standing authority you accepted, and when you accepted it.
- Your account itself, marked closed, with your email address on it, because the records above are tied to it.
Six years is the period in which a dispute about a claim we filed could still be brought, which is why the records outlive the account. When it is up, all of it goes together: the claims, the audit trail, the standing authority, the account row and the email address on it, and the sign-in identity that carries the same address. Nothing of yours is left, here or in the sign-in system.
There are two cases where the deletion waits a little longer, and we would rather say so than let you find out. If closing your account left something behind that had to be removed by hand — a browser profile we could not reach at the time, or a payment subscription we could not cancel — the record naming it is the only thing that says it exists, so we keep the record until a person has dealt with it. And a sweep that suddenly matches far more accounts than this service can have closed six years ago stops and asks for a person, rather than deleting on the strength of what is much more likely to be our own mistake.
We record the closure date when you close the account, and the sweep measures the six years from that date and nothing else. It never reads the date out of the audit trail, because the audit trail is one of the things it deletes. An account closed before we started recording that date, and with no closure entry to take it from, is left alone for a person to decide rather than deleted on a guess.
We write the closure into that record before we delete anything, so the fact that you closed the account outlives the data it describes. The browser profile goes first: if that step fails, nothing of yours has been deleted yet and we can try again. Doing it the other way round could leave a browser holding your TfL session with nothing here to say that it exists.
There is one exception, and we would rather tell you about it than leave it out. If the profile cannot be reached at all, we can still close the account and delete everything else, and then remove the profile by hand. Taking that route is a deliberate choice by one of us, it names the profile in the closure record, and it exists so that a request to close your account is never held up by a problem at our end.