Versione italiana

Privacy notice

TrainTable · version 1.1 · effective from 11 November 2026

TrainTable is an independent app that shows timetables, delays, platforms and strikes of Italian trains taken from public sources. It is not affiliated with any railway company and does not sell tickets. This notice explains which personal data we process, why, for how long and what your rights are, as required by Regulation (EU) 2016/679 (GDPR). The Italian version prevails if the two differ.

In short

1. Data controller

The data controller is mattia@trombella.org. For any privacy question or request, write to mattia@trombella.org.

No data protection officer (DPO) has been appointed: one is not required for this processing.

2. What we process and why

2.1 Your phone, for alerts

The phone is registered on the server only if you allow notifications. If you do not, the server does not receive this data.

Data
A random code the server assigns to the phone, the notification token provided by Google (Android) or Apple (iPhone), the operating system, the app language, which alerts you want (delays, platforms, cancellations, strikes), the registration date and the date of the last contact.
Why
To send you the alerts you asked for, in your language.
Legal basis
Performance of the service you request (Art. 6(1)(b) GDPR).
How long
As long as you use the app. The phone and everything linked to it are deleted if the app does not contact the server for 12 months, or 30 days after Google or Apple tell us the token is no longer valid, for example because you uninstalled the app.

2.2 Trains and routes you follow

Data
The routes between two stations and the recurring trains you save, with days, time window, delay threshold and active alerts; the trains you follow for a single day.
Why
To know which trains to check and when to alert you.
Legal basis
Performance of the service you request (Art. 6(1)(b)).
How long
Routes and recurring trains until you delete them in the app. Trains followed for a single day are deleted 30 days after the travel date.

2.3 Log of the alerts sent

Data
For each alert: the phone code, the train, the kind of change, the text, the time it was sent and the delivery outcome.
Why
To avoid sending you the same alert twice and to check that alerts arrive on time.
Legal basis
Performance of the service (Art. 6(1)(b)) and our legitimate interest in alerts working well (Art. 6(1)(f)).
How long
90 days.

2.4 The account, if you choose to sign in

The account is optional: without it the app works the same way and alerts still arrive.

Data
The identifier Google or Apple gives us for your account, your email (with Apple it can be a private relay address), your name if the provider shares it, the dates of creation and last sign-in, the linked phones and a copy of your trips, favourites and settings (theme, language, alerts). We never receive or keep passwords.
Why
To find your trips, favourites and settings again on another phone.
Legal basis
Performance of the service you request by signing in (Art. 6(1)(b)).
How long
Until you delete the account in the app: deletion from the server is immediate. An account with no sign-in or sync for 24 months is deleted; the phones keep working without it.

2.5 Server technical logs

Data
For each request: the method, the path (which can contain the phone code or a station code), the outcome and the duration. We do not log the IP address: it is used only in memory, for a few minutes, to block excessive requests.
Why
Security, protection against abuse and fixing errors.
Legal basis
Our legitimate interest in keeping the service secure and working (Art. 6(1)(f)).
How long
Logs are overwritten in rotation: at most 100 MB in total, the oldest go first.

2.6 When you browse without following trains

When you search for a station or look at a board or a train, the server receives only the request, for example the station code or the train number, with no data that identifies you.

2.7 What stays only on the phone

2.8 Data about trains, not about you

We store positions and delays of followed trains to build punctuality statistics. This data describes trains and contains no phone code. Raw data is deleted after 90 days; the statistics are kept.

3. What we do not do

4. Who receives data

Providers working for us

Services you use directly, under their own notices

Railway data sources

Our server asks the public sources (ViaggiaTreno and the strike register of the Italian Ministry of Infrastructure and Transport) only for train numbers and station codes, never for data about you.

We disclose data to authorities only when the law requires it.

5. Transfers outside the European Union

Google and Apple may also process data in the United States. Such transfers rely on the European Commission's adequacy decision on the EU-US Data Privacy Framework or on standard contractual clauses. OpenFreeMap is based in the European Union and may serve the map images through Cloudflare's network, which participates in the Data Privacy Framework.

6. Your rights and how to delete your data

You can ask for access to your data, rectification, erasure, restriction of processing and portability, and you can object to processing based on legitimate interest (Arts. 15–22 GDPR).

We answer within one month. You also have the right to lodge a complaint with the Italian data protection authority, the Garante per la protezione dei dati personali (www.garanteprivacy.it), or with the supervisory authority of the country where you live.

7. Security

Traffic between the app and the server is encrypted (HTTPS) and the database cannot be reached from the internet. The server verifies Google's and Apple's answers and signs account sessions. We collect only the data needed to make the app work.

8. Children

The app is not meant for children under 14.

9. Changes

If we change this notice we update the version and date at the top. If the changes are significant, we also point them out in the app.