Privacy policy

This page describes what TrainRunningStatus.live collects and what it does with it. It is written to be read, not to be survived, so it is short — because there genuinely is not much to describe.

There are no accounts

You cannot sign up and we do not ask for your name, email address or phone number to use the site. We hold no profile of you.

What is stored on your device

A few things are saved in your browser's local storage so the site is less tedious to use. These stay on your device, are not sent to us, and are not readable by other websites:

• trains you have recently looked up, so they are one tap away next time;
• stations you recently picked in the trains-between-stations search;
• whether you switched on an arrival alert for a particular stop.

Clearing your browser data removes all of it. Nothing here identifies you.

What our server records

When you load a page, our server keeps an ordinary web log entry and a counter of how many times we have queried the upstream railway feed. The counter records the train number requested and the time — it does not record who asked. Standard server logs include the requesting IP address, as they do on essentially every website; we use them to keep the service up and to stop automated abuse, and we do not use them to build any profile.

The site sits behind Cloudflare, which handles security and delivery and processes request data for that purpose.

Location

The site does not request your location, and the optional feature that would let passengers share a live position is currently switched off. If we turn it on we will update this page first, ask for permission in the browser at the time, and use the position only to improve the reported location of that train.

Analytics

Since 27 August 2026 this site uses Google Analytics 4 to count visits and see which pages people find useful. It records things like the page you viewed, roughly where in the world you are, and whether you arrived from a search engine — and it sets cookies on your device to tell one visit from the next. We use it to decide what to build, not to identify you: we never send it your name, email address or anything you type into the site, because we do not have any of it.

Google processes that data as described in Google’s privacy policy. If you would rather not be counted, Google publishes an opt-out browser add-on, and blocking cookies or using a tracker-blocking browser also works — the site itself does not need any of it to function.

Advertising

We do not currently show ads, and no advertising scripts run on this site. We may add advertising in future to cover the cost of the data feed and hosting. If we do, we will update this page before it goes live and say plainly which network is used. Advertising networks generally use cookies or similar technologies to serve and measure ads; where local law requires consent for that, you will be asked before any such cookie is set.

What we never do

• We do not sell or rent data about you.
• We do not run session recording, and we do not record what you type.
• We do not email you, because we do not have your address.

Children

This is a general-audience travel utility and is not directed at children. We do not knowingly collect information from children.

Your choices

You can clear the site's local storage at any time from your browser settings, and you can use the site with cookies blocked — the running-status lookup works either way. If you want to ask what we hold about a specific request, or want a log entry removed, write to us via the contact page and include enough detail for us to find it.

Changes

If this policy changes we will update the date at the top. Material changes — such as introducing advertising — will be described here before they take effect.

Questions about anything here can go to the contact page. See also our disclaimer about the accuracy of train information.