Catch My Train

Privacy policy

Last updated: 30 June 2026

Plain English. No dark patterns. If something is unclear, email support@catchmytrain.uk.

TL;DR

What we collect

DataWhere it livesWhenWhy
Saved routes (origin, destination, name, icon, buffer)On device, in the App Group containerWhen you create a routeSo we can show your commute
Display name (for "shared by โ€ฆ")On deviceWhen you fill it inAttribution on routes you share
TfL personal API keyOn device, in the iOS KeychainWhen you paste one in SettingsHigher TfL rate limit (optional)
Precise location (exact GPS fix)In memory only, when foregroundedWhen a route has origin = Current locationWalk-time calculation
Approximate location (rounded to ~11 km)On device, in the App Group containerWhenever a fix is readSolar dawn/day/dusk/night palette for the widget
Last known journey snapshotOn device, in the App Group containerAfter each refreshSo the widget renders instantly
Onboarding answers (which commuter type, which pains)On device, in the App Group containerOnce, when you finish onboardingSo future updates can personalise without re-asking
Live Activity push tokenOn device + sent to catchmytrain.uk while a Live Activity is runningWhen 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 daysWhen you tap "Share route" on a route you ownSo 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:

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 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

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:

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 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:

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

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