Privacy policy
Plain English. No dark patterns. If something is unclear, email support@catchmytrain.uk.
TL;DR
- Your saved routes (origin, destination, names you give them) live on your device.
- Your TfL personal API key (optional) lives in the iOS Keychain on your device. We never send it to our backend.
- Live train data is fetched from Transport for London (TfL), by default routed through a small caching proxy hosted at
catchmytrain.uk(Cloudflare Workers). You can point it at your own server, or set it to empty to call TfL directly. - The proxy logs anonymous request URLs (line / station identifiers) for caching. It does not see your name, your TfL key, your routes, or your location.
- We use your precise location only when you opted into "Current location" as a journey's origin, and only while you have the app open. It is sent to TfL's journey planner (over HTTPS) to compute walking time. The exact fix is held only in memory for the duration of the request. A rounded copy of it (~11 km โ enough to know which sunrise/sunset to use) is cached on your device so the widget can show the right time-of-day palette without re-prompting.
- We do not use third-party analytics, advertising, or tracking SDKs.
- We do not have user accounts. There is nothing to log in to.
What we collect
| Data | Where it lives | When | Why |
|---|---|---|---|
| Saved routes (origin, destination, name, icon, buffer) | On device, in the App Group container | When you create a route | So we can show your commute |
| Display name (for "shared by โฆ") | On device | When you fill it in | Attribution on routes you share |
| TfL personal API key | On device, in the iOS Keychain | When you paste one in Settings | Higher TfL rate limit (optional) |
| Precise location (exact GPS fix) | In memory only, when foregrounded | When a route has origin = Current location | Walk-time calculation |
| Approximate location (rounded to ~11 km) | On device, in the App Group container | Whenever a fix is read | Solar dawn/day/dusk/night palette for the widget |
| Last known journey snapshot | On device, in the App Group container | After each refresh | So the widget renders instantly |
| Onboarding answers (which commuter type, which pains) | On device, in the App Group container | Once, when you finish onboarding | So future updates can personalise without re-asking |
| Live Activity push token | On device + sent to catchmytrain.uk while a Live Activity is running | When you enable "Live train on the Lock Screen" | So the Worker can push per-minute ETA updates to the activity |
| Shared route payload (display name, route label, stations, walk/buffer) | Sent to catchmytrain.uk, stored in Cloudflare KV for up to 90 days | When you tap "Share route" on a route you own | So the recipient's device can fetch and decode the route from a short URL |
What our backend sees
By default, TfL API calls route through a small caching proxy at
catchmytrain.uk (Cloudflare Workers). The proxy:
- Receives HTTPS requests like
/tfl/Line/elizabeth/Arrivals/910GACTNML. - Caches TfL's response briefly so repeat requests across users are faster and TfL is hit less.
- Returns TfL's response to your device.
- Does not receive your name, your TfL key, your stored saved-routes list, or any account identifier (there are no accounts).
- Sees your precise location only when a route is configured with origin = "Current location". In that case the journey-planner request URL contains your GPS fix as
lat,lonin the path (e.g./tfl/Journey/JourneyResults/51.5234,-0.1789/to/940GZZLUPAC), the same way TfL itself sees it. The Worker neither stores nor forwards this beyond the immediate request. If you'd rather the proxy never see your location at all, use a postcode as the origin (the postcode reaches the planner instead) or clear Settings โ Server URL to callapi.tfl.gov.ukdirectly. - Cloudflare records standard request metadata (IP address, timestamp, request URL) in operational logs โ which for "Current location" routes therefore includes the
lat,lonsegment of the request URL. We do not export, copy or otherwise further process these logs. Cloudflare's standard retention on the Free plan is approximately 3 days for Workers request logs and up to 6 months for aggregate HTTP analytics, governed by Cloudflare's privacy policy.
You can change the backend URL in Settings โ Server URL,
point it at your own Worker, or set it to empty to call
api.tfl.gov.uk directly from your device.
What the backend sees when Live Activities are on
Live Activities (Lock Screen + Dynamic Island) are off by default. When you turn them on, the app sends the Worker a small recipe for each running activity:
- The APNs push token Apple gave the activity (an opaque per-activity identifier).
- The TfL line and stop ID for the boarding station, and the boarding station's human-readable name.
- The final station's name and a small set of journey constants (walk + buffer minutes, number of changes, your route's nickname).
- The end timestamp of the current watch window, so the Worker can dismiss the activity past it without the app being open.
The Worker uses this recipe to recompute the ETA from live TfL arrivals every minute and push the updated state directly to your device. The recipe is held in Cloudflare KV for the duration of the activity (auto-expiring after 6 hours). It contains no name, no email, no account identifier, and no precise location โ but it does include the name of the line and station you're commuting from and to.
Turning the toggle off (Settings โ "Live train on the Lock Screen") immediately dismisses any running activity and removes the recipe from the Worker.
What we do not collect
- We do not have user accounts.
- We do not use third-party analytics, advertising, attribution, or crash-reporting SDKs.
- We do not track you across apps or websites.
- We do not sell or share data with advertisers.
Sharing a route
When you tap "Share route", the app posts a small JSON payload to
catchmytrain.uk/r and gets back a short URL like
https://catchmytrain.uk/r/aB3xK9_. That's the URL you
share.
The payload contains:
- Your display name (as you typed it in Settings).
- The route's label, icon name, walk buffer, and round-trip settings.
- The origin and destination station names + TfL stop IDs.
It does not contain your TfL API key, your precise location, or any account identifier (there are no accounts).
The Worker stores this payload in Cloudflare KV for up to 90 days, keyed by an 8-character id derived from a hash of the payload itself (so re-sharing the same route to a second friend reuses the same URL rather than creating a new entry). The recipient's device tapping the link fetches the payload, decodes it locally, and asks them to confirm before adding the route.
If the Worker is unreachable at share time, the app falls back to
the older self-contained catchmytrain:// link โ the
whole route embedded in the URL, no server involved.
Children
This app is rated 4+ but is not directed at children specifically. We collect no personal information from anyone, including children.
Scheduled push-to-start
If you set a watch-time window (Settings โ "Show me at"), the app also sends the Worker a schedule entry containing:
- The same recipe described above (line, stop ID, station names, journey constants).
- A push-to-start APNs token (an opaque per-app identifier Apple issues for ActivityKit, distinct from any user identifier).
- The start and end timestamps of the window, in your local time zone.
The Worker stores the entry in Cloudflare KV and uses it to start a Live Activity on your device at the start of the window, so the Lock Screen comes pre-warmed without you opening the app. Entries are deleted automatically at the end of their window, when you turn the toggle off, or when you remove the route. They contain no name, email, account, or precise location.
Local backups & sync
Some on-device data may be included in standard iOS backups:
- iCloud Backup copies most app container files to your iCloud account (encrypted with your Apple ID). This is the default on iOS.
- Encrypted iTunes/Finder backups include the Keychain item that holds your TfL key. Unencrypted iTunes/Finder backups do not.
- iCloud Keychain is not used by
this app โ the TfL key lives in the device Keychain with
kSecAttrAccessibleAfterFirstUnlock, which excludes it from iCloud Keychain sync.
To opt the app out of iCloud Backup entirely, toggle Settings โ [your name] โ iCloud โ iCloud Backup โ Catch My Train off in iOS.
Your rights
You can wipe every piece of data this app has stored on your device from inside the app: Settings โ Reset Catch My Train. This deletes your routes, TfL key, server URL, display name, Live Activity settings, and all local caches in one tap. Live Activities are ended (which tells the Worker to forget the recipe) and the App Group container is emptied.
If you'd rather, uninstalling the app does the same โ it removes the App Group container and the Keychain item belonging to it.
If you want any data the Cloudflare proxy may incidentally hold to be removed beyond Cloudflare's own retention, email nourelmenyawi@gmail.com with the IP address and rough timestamp of your request.
Contact
- Author: Nour El Menyawi
- Email: support@catchmytrain.uk
- Help & FAQ: catchmytrain.uk/support
Changes
If this policy changes materially, the "Last updated" date above will change and a note will appear in the app's About section.
Catch My Train ยท Home ยท Support