Privacy
The short version
- No account, no ads, no cookies.
- Your location never leaves your phone.
- Favourites and your ticket are saved on your phone.
- Tapping the yellow button sends a small record so we can improve the times. It's kept for 12 months.
- We count visits to each page, without cookies.
- If you send feedback, we keep your message (and your email, if you give it) until it has been dealt with.
The full detail is below.
What's saved on your phone
-
A single
localStorageflag (wtt_walking_enabled) that remembers whether you've turned location on (for sorting spots by distance and showing walking times). -
A
wtt_location_askedflag, so the question about walking times on your first visit is only asked once. Your answer is all it records; "Use my location" is still there if you said not now. -
A
wtt_favouriteslist of your starred spots, in the order they were starred. It is saved the first time the app opens, even if empty. If you used the app before stars became a list, it starts with the spot you had starred, or East Avenue if you had none, and the olderwtt_favourite_viewpointflag is removed. -
A
wtt_fact_indexnumber, so the fact line doesn't start on the same fact every time. -
A
wtt_tap_staterecord for the yellow "train is passing" button: whether the buttons are on or off (with when you last switched them off or said "Not now", and how many times you've answered or changed it), how many trains you've timed, a short key for each of the last 20 trains you timed (spot, direction and predicted time, so the same train isn't counted twice), a list of the spots where you've timed a train (kept even after those trains drop off the list of 20, so your ticket can name them), the times of your latest tap so its thank-you can be shown, how many visits have shown the full explanation of the button (it stops after two), and a random id made on your device (see below). -
A
wtt_seen_freight_regionslist insessionStorage(cleared when the tab closes), noting which freight regions have already been shown so a new one can be highlighted once. - The PWA's service worker caches the app shell (HTML, CSS, JS, icons) so the app works offline. None of this is shared with me.
Timing taps
At some spots a yellow button appears as a train is due. If you tap it, your phone sends one small record to this site's own function, which stores it so the bridge timings can be tuned. A tap sends exactly these fields:
viewpointIdanddirection— which spot and which way the train was going.msSinceTap— how long ago you tapped when the record was sent, in milliseconds, so the server can work out the tap time.predictedAtShowMsandpredictedAtTapMs— when the app predicted the train when the button appeared and when you tapped.source— whether that prediction came from signalling data (berth) or TfL (tfl).berthStepMs— when the signalling step behind the prediction fired, if there was one.tflExpectedArrivalMs— TfL's expected arrival time for that train, if known.vehicleIdandberthTrainId— TfL's and the signalling system's ids for the train, if known.atViewpoint— justyes,noorunknown: whether you were within about 150 metres of the spot. It isunknownunless location is on and your phone has found its location.deviceId— a random code made on your device and kept inwtt_tap_state, so repeat taps from one phone can be told apart. It isn't linked to you.
No coordinates are sent, and there is no account. The server adds the time it received the tap and the tap time worked out from it. Taps are kept for 12 months and then deleted. If you choose "Not now" or "No thanks", or turn off Show the yellow button on your ticket page (open it from the ticket button at the top of the screen), no buttons appear and nothing is sent.
Your location
On your first visit the home screen asks whether to show walking
times. If you tap Yes, or later
Use my location on the home screen or
Enable walking time on a spot, your browser hands
your latitude and longitude to this app's JavaScript code. Those
coordinates are used on your device only, to work out how far you
are from each spot, so the list can be sorted nearest first and
walking times shown. They are never transmitted
anywhere. They are not stored, logged, or sent. A tap sends
only whether you were near the spot (yes or
no), never the coordinates.
On the map page you can also tap a location button to show your position as a dot. The dot is drawn on your phone, and your position is never sent anywhere, including to the map provider.
You can turn this off at any time using the small Turn off button next to "Nearest first" on the home screen or next to the walking time on a spot. That stops the location watch and removes the localStorage flag. The app never asks your browser for your location until you tap Yes, Use my location on the home screen or the map page, or Enable walking time on a spot.
Services your phone talks to
This app is a handful of static files served from a CDN, plus two small functions. One, used only on the Suffragette-line spots, is stateless and proxies freight-data requests to Realtime Trains so that their API credentials stay server-side. The other stores the "train is passing" taps described above. Both log requests as part of normal Netlify operation; neither sees your coordinates or who you are.
Because the app runs entirely in your browser, a few network requests go to third parties. I don't see any of these, but they may log your IP and user agent on their own servers:
-
TfL Unified API (
api.tfl.gov.uk) — for live train arrivals. TfL's own privacy policy covers what they do with their logs. The home screen asks TfL for arrivals at the stations behind the spots listed, about every 30 seconds while it is open. -
Realtime Trains (via
/.netlify/functions/freight) — only while a Suffragette-line spot's countdown is open (Queens Road Station or Northcote Road Bridge), never from the home screen. Their privacy policy covers what they log. My proxy forwards your browser's freight request to their API and returns their response unchanged; no user-identifying data is added. -
Live signalling feed
(
e17trains-td-proxy.fly.dev, a small service I run on Fly.io) — only while a spot's countdown is open, never from the home screen. Your browser holds a connection open to it and receives train movements from Network Rail's signalling data, which sharpen the countdown. Your browser sends it nothing beyond the connection itself. The service records only that a connection opened or closed; Fly.io, which hosts it, may log your IP address. -
Google Fonts (
fonts.googleapis.comandfonts.gstatic.com) — to load the Baloo 2 and Nunito typefaces. -
OpenFreeMap (
tiles.openfreemap.org) — draws the map, and only when you open the map page. It sees your IP address and which part of the map you're looking at, and may be delivered through Cloudflare. Your location is never sent to it: the pins and your dot are drawn on your phone. See its privacy policy. Map data © OpenStreetMap contributors. -
Netlify — the CDN that serves this site. Netlify
logs requests as part of hosting the site, and stores the
"train is passing" taps (via
/.netlify/functions/tap). - Cloudflare — provides DNS for this domain and also runs the pageview analytics (see next section).
Feedback and spot suggestions
The feedback form sends what you type to Netlify, which hosts this site. Only I can read the messages.
- What's sent: what it's about, your message, and your email only if you fill it in. Netlify also notes the time and your IP address, to block spam.
- What it's for: improving the app, checking suggested spots, and replying if you asked. Your email is never used for anything else or shared.
- How long: until your message has been dealt with, then deleted. Ask through the form and yours will be deleted sooner.
Counting visits
This site uses Cloudflare Web Analytics, a privacy-friendly pageview count, to count how many people visit. It's designed around not identifying individual visitors:
- No cookies. Nothing is stored in your browser by the analytics beacon.
- No fingerprinting. No device, canvas, or font fingerprinting.
- No cross-site tracking. Cloudflare doesn't build a profile of you across the web.
- What it does see: the page URL, referrer (if any), user agent, and a coarse country estimate from your IP. Each spot has its own URL (for example
/walthamstow/east-avenue-bridge), so the count shows which spots are opened. - What it doesn't see: anything else you do inside the app — whether location is on, the facts you tap, the spots you star, the buttons you press.
Apart from a tap on the yellow button, and which spot's page you open (part of the pageview count), nothing you do inside the app — tapping the fact line, turning on location, starring a spot, watching the countdown — is tracked or reported back to me.
Cloudflare publish their own privacy policy covering what they keep and for how long.
What we never do
- No advertising or ad-network code.
- No account, login, or sign-up.
- No cookies set by this site itself.
- No third-party scripts beyond the Cloudflare pageview beacon and the Google Fonts loader.
Questions or corrections? Open an issue on GitHub.