Privacy Policy – London Metro (iOS and Android)
Last updated: 13 November 2026 (version 1.0)
Controller: Geitau 21 GmbH & Co. KG, Geitau 21, 83735 Bayrischzell, Germany. Email: office@exosphaera.dev. Further details in the legal notice.
UK representative (Art. 27 UK GDPR): [open – see docs/RECHT.md B3.6]
In short
- During a ride that you start, London Metro listens for the announcements on the train. Sound is analysed only on your device. It is never stored and never sent anywhere – not even to us.
- There is no account, no advertising, no analytics and no tracking. Optional support purchases run entirely through Apple or Google; we receive no payment data.
- Nothing about your journeys leaves your device without your explicit consent.
- If you choose, you can contribute ride profiles (sound levels, pressure and magnetic traces, stop times – no audio, no name, no account, no device identifier) to improve positioning for everyone.
- If you choose, you can send crash reports.
- Version 1.0: the options "Contribute ride profiles" and "Send crash reports" are not yet available in the app. Version 1.0 therefore sends no data about you or your journeys anywhere – apart from the technical requests in section 2. Sections 3 and 4 describe these options for when they are switched on in a later version; we will tell you in the app beforehand.
1. What happens on your device
During a ride the app processes on your device:
- Microphone: sound is analysed continuously in very short chunks (a few seconds at most, held only in memory): speech recognition of station announcements, door chimes, running noise and an estimated sound level. Speech recognition runs on the device only (Apple's or Google's on-device features, or a model built into the app); if it is not available on your device, the app works without announcements. Recognised words are only compared with a fixed list of station announcements and then discarded; at most the result is kept ("next station: Oxford Circus"). Raw audio and transcripts are never stored or transmitted. Voices are not recognised or told apart. On iPhone the app listens only while it is open on screen; when you switch to another app or lock the phone, listening pauses. On Android listening continues during a ride you started, with an ongoing notification and a Stop button, also when the screen is off.
- Motion, air pressure, magnetic field: to detect stops, departures, depth and sections of line.
- Location (satellite positioning; on Android also mobile cell identifiers): only while you use the app, for your starting point and sections above ground.
- Camera (optional, "See-through" view only): the image is only shown live; it is neither stored nor analysed.
- Routes and walking times: routes you plan, platforms and walking times inside stations are calculated and kept on your device. When you record a walk through a station, the app uses the step counter, air pressure and gyroscope (no satellite track, no time of day) and stores only the walking time, level changes and a rough sequence of directions per station.
- Ticket recommendation: your planned trips, days and zones are compared with a fares table on your device. Nothing about your plans leaves your device; the app does not sell tickets.
- Ride profiles: the app keeps features of your rides (e.g. sound level per section, pressure trace, stop times) on your device to improve positioning. Delete them in Settings ("Delete local data") or by deleting the app.
Legal basis: Art. 6(1)(b) UK GDPR / GDPR (providing the feature you start under the terms of use). Accessing the microphone, sensors and location is strictly necessary for this feature you requested (PECR Schedule A1 para. 4; § 25(2) no. 2 German TDDDG). You grant and withdraw permissions in your system settings; without the microphone the app keeps working with reduced accuracy.
Other passengers: other people's voices may be analysed for fractions of a second. They are not stored, not transmitted, not recognised and only checked for whether a station announcement is being made. The legal basis is Art. 6(1)(f) UK GDPR / GDPR; our legitimate interest is positioning in tunnels without signal using public announcements. As nothing is stored, we cannot identify other passengers (Art. 11).
2. What is transmitted even without consent
- Network model and fares table: at most once a week the app checks for a new version of the line model and fares table and downloads it from Firebase Hosting (Google). Google technically processes your IP address and device type/version to deliver it, detect abuse and produce statistics, and keeps these logs for a few months. Legal basis: Art. 6(1)(f) (interest: up-to-date line data).
- TfL live data: when you have signal, the app requests public service data from Transport for London (e.g. arrival times). TfL receives your IP address and is responsible for that itself (https://tfl.gov.uk/corporate/privacy-and-cookies/). Legal basis: Art. 6(1)(b).
- Speech models: Apple or Google download on-device speech models through the operating system under their own terms.
3. Contributing ride profiles (only with your consent)
If you switch on "Contribute ride profiles", the app sends at most one profile per ride (≤ 30 KB) over Wi-Fi only, at most five per day, to our database (Google Cloud Firestore, located in the EU). Contents: line and sections, sound levels and octave bands per section (5-second grid), air pressure and magnetic traces relative to the start of each section, running and stop times relative to the start of the ride, day of the week and a three-hour time window, device model class and app version; on Android also mobile cell identifiers in tunnel sections. Not included: audio, transcripts, name, account, device identifier, exact time, satellite track, Wi-Fi names. Purpose: improving the shared positioning and sound model (fingerprints of sections). Legal basis: your consent (Art. 6(1)(a) UK GDPR / GDPR; PECR Schedule A1 para. 2; § 25(1) TDDDG). You can withdraw it at any time in Settings; from then on nothing is sent. "Delete my recent contributions" deletes your contributions from the last 30 days (the app keeps their random identifiers locally for this purpose). We cannot link older contributions to you. You must be 16 or older to consent. Retention: we delete raw contributions once they have been included in the model, at the latest after 24 months. The resulting model only contains aggregated values per section. Abuse protection: so that only genuine app installations can write, we use Firebase App Check (Apple App Attest or Google Play Integrity) – only while contributing is switched on. Its tokens are valid for at most 7 days and are kept for at most 30 days to prevent reuse. Legal basis: Art. 6(1)(f) (interest: protecting the database from fake contributions).
4. Crash reports (only with your consent)
If you switch on "Send crash reports" (off by default), the app sends a report to Firebase Crashlytics (Google) when it crashes: where in the code the error occurred, app state, device model, operating system and a random Crashlytics installation identifier. No locations, stations, audio or transcripts. Purpose: finding and fixing bugs. Legal basis: consent (Art. 6(1)(a); § 25(1) TDDDG), which you can withdraw in Settings at any time. Google deletes reports after 90 days.
4a. Purchases (voluntary support)
If you support London Metro with a subscription or one-time purchase, the purchase is handled entirely by Apple (App Store) or Google (Google Play) as the seller; their privacy policies apply. The App checks on your device, directly with the App Store or Google Play, whether a support subscription is active – nothing is sent to us. We receive no payment or contact data. We only receive the reports that Apple and Google provide to developers (Apple: aggregated sales figures; Google Play: a list of orders with order number, product, date, country and amount). We use these only for accounting (Art. 6(1)(c) GDPR/UK GDPR: statutory bookkeeping obligations) and keep them for the statutory retention periods (up to 10 years under German tax law).
5. Service providers and international transfers
Firebase Hosting, Cloud Firestore, App Check and Crashlytics are operated by Google (Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland, and Google LLC, USA) as our processor under Art. 28 (Firebase Data Processing and Security Terms). Firestore data is stored in the EU; Hosting and Crashlytics may process data worldwide, including in the USA. Google LLC is certified under the EU-US Data Privacy Framework and its UK Extension; transfers rely on the corresponding adequacy decision and UK adequacy regulations. More: https://firebase.google.com/support/privacy For email we use Proton Mail (Proton AG, Switzerland; adequacy decision).
6. Contacting us by email
If you write to us, we use your details only to handle your request (Art. 6(1)(b) or (f); interest: answering you) and delete them when no longer needed, at the latest after statutory retention periods.
7. No analytics, no advertising, no automated decisions
The app contains no analytics, advertising or tracking services and no advertising identifier. There is no automated decision-making within the meaning of Art. 22.
8. Children
The app is not directed at children. Contributing and crash reports require you to be 16 or older.
9. Deleting your data
- Data on your device (ride profiles, routes, walking times, settings): Settings → "Delete local data", or delete the app.
- Contributed ride profiles (only once contributing is available): Settings → "Delete my recent contributions" deletes those from the last 30 days; switch off "Contribute ride profiles" to stop sending. Older contributions cannot be linked to you.
- Crash reports (only once available): switch off "Send crash reports"; Google deletes reports after 90 days.
- Emails: write to office@exosphaera.dev and we will delete our correspondence with you.
There is no account, so there is no account to delete.
10. Your rights
You have the rights under Arts. 15–21 UK GDPR / GDPR (access, rectification, erasure, restriction, portability, objection) and may withdraw consent at any time with effect for the future (Art. 7(3)). You may object to processing based on Art. 6(1)(f) on grounds relating to your particular situation (Art. 21). As we store no identifiers, we often cannot link data to a person (Art. 11); you delete local data yourself in the app. Complaints: Information Commissioner's Office (ICO), https://ico.org.uk/make-a-complaint/ – or our lead supervisory authority in Germany, Bayerisches Landesamt für Datenschutzaufsicht (BayLDA), Promenade 18, 91522 Ansbach.
11. Changes
If our processing changes, we update this policy and point this out in the app. We ask again for any new consent.