Privacy Policy

Beautiful Trains
Last updated: 13 November 2026


Who we are

Beautiful Trains is made by Dutch Spaghetti Software Ltd, 5 Central Way, Oxted RH8 0LS, United Kingdom. We are the data controller for the personal data described here. Privacy questions: hello@beautifultrains.app.


What this app does

Beautiful Trains shows live UK train departures and journey times using data from National Rail Enquiries and the Rail Data Marketplace, and can send you a notification when a journey you have set up is delayed or cancelled. It is available for iPhone and for Android; this policy covers both, and says where they differ. It uses your location, with your permission, to suggest your nearest station.


Data we collect, and why

Location

When you allow location access, the app works out your nearest station on your device, using the location services built into iOS or Android (on Android, Google Play services). The app never sends your coordinates to us or to anyone else. On Android the app asks for approximate and precise location together, so you can choose either, and only when you ask for your nearest station or reach the location step in setup, never when the app starts. Neither app uses your location in the background. If you open the nearest station's departure board, that station's three-letter code is recorded in analytics like any other board you open; nothing marks it as coming from your location. If you grant only approximate location (on iPhone, Precise Location off), the app says so and treats the suggestion as approximate. The analytics described below also record whether location permission is on, off or not yet asked.

Lawful basis: none is needed for your coordinates, because we never receive them; the station code is covered under Analytics below.

Journey alerts

If you set up a journey alert, our server stores the alert's stations, days of the week, departure time, how far ahead to notify you, whether it tracks one specific train, which changes to tell you about, any snooze you set, and your device's push identifier, so it can check your journey against live running information and send you a notification. The push identifier is the push-notification token Apple gives your iPhone or, on Android, the Firebase installation ID that Google's Firebase creates for the app when you first use alerts; Firebase also keeps that ID itself, to deliver notifications. Alerts are checked by our server (hosted by Supabase in London) and delivered by Apple Push Notification service on iPhone or Firebase Cloud Messaging (Google) on Android. The notification itself contains the departure time, the route and the delay or cancellation text.

To keep your alerts, the app tells our server, at most about once a day, that the device is still in use: a short request that carries the push identifier and nothing else about you. An alert is kept until you delete it, until Apple or Google tells us the push identifier is no longer valid, or until about 30 days pass without any of these happening while notifications are allowed: you open the app, you save an alert, or the app refreshes its widgets in the background (on iPhone this needs Background App Refresh on, and can happen even if you have no widget installed; on Android it happens only while one of the app's widgets is on your home screen). If you restore your phone from a backup, or your device is given a new push identifier, your alerts move to it automatically. On Android, your journey alerts and their settings (including the device's last push identifier) are included in Android's own app backup to your Google account, so they can come back on a new phone or after a reinstall. Apart from the purchase identifier described under Purchases, nothing else the app stores is backed up there. If you delete the app, its alerts stop and are removed from our server after about 30 days. You can delete an alert at any time in Settings → Journey Alerts in the app.

Lawful basis: performing the service you asked for (contract).

Analytics

We use PostHog (EU data centre) to understand how the app is used so we can improve it. Events can include raw three-letter station codes for departure boards, journey origins and destinations, restored journeys and journey-alert routes, together with operational details such as result counts, selected time mode, alert settings, subscription screens and purchase outcomes (started, shown, converted, dismissed, restored or failed), onboarding steps shown, completed or skipped (never the stations you chose as home or work), uses of Beautiful Trains+ features and whether you are subscribed, and whether the nearest-station lookup succeeded. It also records which screens you open (by name, such as Settings or Station information), station codes you look up in Station information and in historic journey times, which display, appearance and privacy settings you change (such as which regions' popular stations to show, or whether crash reports are sent; never your home or work station), how you opened the app (from a widget, a notification or a link), when you start setting up a journey alert, how many and which types and sizes of widget you have installed (never the stations they show), a once-a-day signal that a widget refreshed in the background, whether a purchase was made in Apple's or Google's test environment, which platform the app runs on (iOS or Android), and, on iPhone, whether the device is one of Apple's internal test devices. PostHog also records app lifecycle events (installed, updated, opened, backgrounded), and technical details such as device model, operating system and app version, language, time zone, screen size, network type and, on Android, your mobile network's name, plus whether notifications and location are enabled (and, on iPhone, Background App Refresh). It also receives timings of how long the app takes to start and to show departure boards and journey results (including how long our server spent on each step), and, on iPhone, Apple's daily summary of launch times, so we can find and fix slow spots.

The app creates a random identifier when first installed and gives it to PostHog and Sentry (and, while analytics is on, to RevenueCat, as described under Purchases), so events and crash reports from one installation can be linked. It is pseudonymous — it does not contain your name, Apple ID, Google account, email address or any device serial. On iPhone it is restored if you restore from a backup; on Android it is not backed up, so a reinstall or a new phone starts with a new one. Repeated route events can reveal travel patterns even though they are not linked to a person.

PostHog receives your IP address with each upload. We have configured PostHog to discard it. When the iPhone app starts it also downloads PostHog's public settings file (the same for every user), which reaches PostHog's servers as an ordinary web request and so includes your IP address, even if you have turned analytics off; this request does not include your installation identifier or any other identifier from your device. The Android app does not download it. We do not use PostHog's feature flags, but PostHog's app library makes a small feature-flag request of its own when it links the app to your installation's identifier (when analytics first starts, and again if you turn it back on), carrying that identifier. Turning analytics off stops the app sending PostHog any events (on iPhone, only the settings-file download above continues). It does not delete what was already sent. If you turn analytics back on, new events are linked to the same installation identifier as your earlier ones. Subscription events that RevenueCat sends to PostHog are described below.

RevenueCat also sends PostHog events about purchases and subscriptions (a purchase, a trial starting or converting, a renewal, cancellation, expiry, billing problem or refund). While analytics is on, these are linked to your installation's identifier. When analytics is off they still reach PostHog, but under RevenueCat's own random identifier instead of your installation's analytics identifier, so they cannot be linked to your other analytics events. Events sent before you turned analytics off stay linked.

You can turn analytics off in Settings → Privacy → "Share usage analytics". It is on by default. Turning it off stops the app sending analytics events and removes the installation identifier from RevenueCat (the effect on RevenueCat's events is described above). We do not use analytics to track you across other companies' apps or websites, and we do not use advertising identifiers.

Lawful basis: our legitimate interest in understanding and improving the app, relying on the statistical-purposes exception in the Privacy and Electronic Communications Regulations (as amended by the Data (Use and Access) Act 2025). This law lets apps collect usage statistics without asking first, provided we tell you and let you switch it off for free. You have the right to object at any time — the toggle above does exactly that.

Crash reports and performance

Sentry (EU data centre) receives crash reports, reports when the app stops responding, and diagnostics used to investigate reliability problems: device model, operating system and app versions, on iPhone whether the device is one of Apple's internal test devices, stack traces, train service IDs, recent diagnostic breadcrumbs that can contain raw station codes or route pairs, and the addresses of requests the app made (these can contain station codes) in breadcrumbs, failed-request reports and, for a sample of sessions, performance traces. Neither app adds your IP address to these reports, and our Sentry projects are set not to store the IP address a report arrives from. Crash reports carry the same pseudonymous installation identifier as analytics. Station and route context is used only to reproduce and fix faults. Our server also sends Sentry diagnostics about failed train-data requests, which include the stations or train involved but no device identifier.

You can turn crash reporting off in Settings → Privacy → "Send crash reports". It is on by default.

Lawful basis: our legitimate interest in finding and fixing faults. Storing crash data on your device relies on the exception in the Privacy and Electronic Communications Regulations for detecting technical faults; performance traces rely on the statistical-purposes exception described above. You can object at any time with the toggle above.

Feedback

If you send feedback from the app, we receive your message, the category you chose, the app and operating system versions (iOS or Android) and your device model, delivered to us by email through Resend. If you add a reply-to email address, we receive that too and use it only to reply to you. To limit abuse, the app also sends a one-way hash derived from your device (on iPhone, from the app's vendor identifier; on Android, from the Android ID), which lets us allow one submission per day; that hash is deleted within 37 days. Feedback emails are deleted after 12 months. Analytics also records that feedback was sent, its category and whether you added an email.

Lawful basis: performing the service you asked for (answering you) and our legitimate interest in preventing abuse.

Service protection and request logs

Our servers see your IP address when the app requests train data. We use it to limit excessive requests; those rate-limit records are deleted within 3 hours, except daily counts, which are deleted within 27 hours. If a request is blocked as abusive, its IP address is kept in a security log for 90 days. Separately, our hosting provider's request logs record your IP address, your device's user agent and the station codes or journey requested, for 7 days.

Approximate location. Those request logs also record an approximate location worked out from your IP address (city, country and network). It is kept for 7 days with the rest of the log and is used only to run the service and to keep it secure (for example, to investigate faults and abusive traffic). It is never your device's own location, which the app does not send.

Lawful basis: our legitimate interest in keeping the service available and secure.

Purchases

To check whether you have Beautiful Trains+, the app contacts RevenueCat each time it starts, sending a random RevenueCat identifier, your IP address and basic device and app details. If you subscribe to Beautiful Trains+, your purchase is processed by Apple (App Store) on iPhone or by Google (Google Play Billing) on Android, and managed through RevenueCat. RevenueCat keeps your purchase history so it can confirm and restore your subscription. We receive your subscription status and product, which are also recorded in analytics, but never your payment details. While analytics is on, the app also gives RevenueCat the installation's analytics identifier, so RevenueCat can send purchase and subscription events to PostHog against it. Turning analytics off removes the identifier from RevenueCat; what that means for those events is described under Analytics. Purchase history is linked to your Apple ID or Google account as part of the standard App Store or Google Play purchase process. On Android, RevenueCat's random identifier is also saved with Google's Block Store (part of Google Play services), so that after a reinstall RevenueCat can recognise your earlier purchases. The Android app has RevenueCat's collection of device identifiers (such as the advertising ID) turned off.

Lawful basis: contract.


Data we do not collect


Who processes your data, and where

Service What it does for us Where Privacy policy
Supabase Hosts our server, database and request logs: train-data requests, journey alerts, feedback rate-limiting London, UK (database); request logs: UK supabase.com/privacy
Apple Push Notification service Delivers journey-alert notifications on iPhone Apple (global) apple.com/legal/privacy
Firebase Cloud Messaging and Firebase Installations (Google) Create the Android push identifier and deliver journey-alert notifications on Android Google (global, including the United States) policies.google.com/privacy
PostHog Product analytics EU posthog.com/privacy
Sentry Crash reporting and performance EU (Germany) sentry.io/privacy
RevenueCat Subscription management United States revenuecat.com/privacy
Resend Delivers feedback to us by email EU (Ireland) resend.com/legal/privacy-policy
Apple App Store Takes payment on iPhone (Apple's own privacy policy applies; Apple is the controller for payments) Apple (global) apple.com/legal/privacy
Google Play Billing Takes payment on Android (Google's own privacy policy applies; Google is the controller for payments) Google (global) policies.google.com/privacy
National Rail Enquiries Live train data (our server asks on your behalf; they do not receive anything about you) UK nationalrail.co.uk
Rail Data Marketplace (Rail Delivery Group) Train formation, historical performance and station data (our server asks on your behalf; they do not receive anything about you) UK raildata.org.uk

International transfers. RevenueCat, Apple and Google process data in the United States. These transfers rely on the UK International Data Transfer Agreement or the UK Extension to the EU–US Data Privacy Framework, as applicable to each provider. PostHog, Sentry, Supabase and Resend store our data in the UK or the EU.


How long we keep data

Data Kept for
Journey alerts (route, schedule, settings, push identifier) Until you delete the alert, Apple or Google reports the push identifier invalid, or about 30 days pass without the app being opened, an alert saved, or a background refresh, while notifications are allowed; if you delete the app, after about 30 days
Alert snoozes Until about a day after the snooze ends, or until you have no alerts left
PostHog analytics events Up to 12 months
Sentry crash reports and diagnostics Up to 90 days
Feedback emails 12 months
Feedback device hash Up to 37 days
Feedback delivery logs at Resend Per Resend's own retention policy
Rate-limit records Up to 3 hours (daily counts: up to 27 hours)
Security log (blocked requests) 90 days
Hosting request logs 7 days
Purchase records Held by Apple or Google and by RevenueCat as needed to provide and restore subscriptions

Your rights

Under UK data protection law you have the right to access the personal data we hold about you, to have it corrected or erased, to restrict or object to its processing, and to data portability where it applies. You also have the right to complain to the Information Commissioner's Office (ico.org.uk).

In practice:

You are not required by law or contract to provide any of this data; if you decline location or notification permissions, or turn off analytics and crash reports, the app still works, with those features reduced. We make no automated decisions about you.


Children

Beautiful Trains is not directed at children under 13 (it is rated 4+ on the App Store because it has no objectionable content) and does not knowingly collect data from children.


Changes

We show the date of the latest version at the top of this page and, for significant changes, tell you in the app.


Contact

For privacy questions: hello@beautifultrains.app