Privacy Policy
Last updated: 29 October 2026
This policy explains what personal data Trenify P.S.A. processes in connection with the Trainradar24 app, the trainradar24.eu website and related services, why we process it, and what rights you have.
The controller of your data is Trenify P.S.A., ul. Półwiejska 17/26, 61-888 Poznań, Poland, entered in the National Court Register (KRS) under number 0001027160, tax ID (NIP) 7831877152 (“we”, “us”, “Trenify”). This policy covers:
- the Trainradar24 mobile app for Android and iOS,
- the trainradar24.eu website, including departure boards, maps and the blog,
- the mcp.trenify.eu server for AI assistants,
- communication with us, for example by email.
For any matter concerning your personal data, write to support@tr24.eu.
Summary of key points
- You can use the app and the website without an account. An account (sign-in with Google or Apple) is only needed for the kilometre counter, rankings and notifications about a specific train.
- From your account we only know your email address. We do not receive your name or profile photo.
- Your location is sent to our server only when you are signed in and have started a journey, so that we can count the kilometres you travel. Raw GPS points are deleted automatically after 60 days at the latest.
- We do not process special categories of data (such as health data) and we do not sell data.
- We use external service providers, including Google (Firebase, ads, maps), Apple and Microsoft (Clarity), as well as providers of technical infrastructure. Details in section 4.
- Personalised ads and part of our analytics rely on your consent, which you can change at any time.
- You can delete your account in the app at any time; your journey and location history is deleted with it.
Table of contents
- What data do we collect?
- Why do we process your data?
- What legal bases do we rely on?
- Who do we share data with?
- Is data transferred outside the European Economic Area?
- Cookies and similar technologies
- Signing in with Google and Apple
- Location and the kilometre counter
- Notifications
- Advertising
- Server for AI assistants (MCP)
- How long do we keep data?
- How do we protect data?
- What are your rights?
- Children
- Where does the train data come from?
- Changes to this policy
- Contact
1. What data do we collect?
In short: data you give us yourself (your email address when you sign in, the content of your messages) and data collected automatically when you use our services (device information, usage information and — in the app, with your permission — location).
Data you provide
- Email address — we receive it from Google or Apple when you sign in to the app. With Sign in with Apple this may be a relay address that hides your real email.
- Username — we assign a random one when you create an account; you can change it. It is visible in rankings.
- Correspondence — when you email us or report a problem.
Account data
- sign-in method (Google or Apple) and account creation date,
- the train you are currently on (if you select it),
- kilometres travelled (per day, week, month and in total), points, challenges and ranking positions,
- journey history: date, sections between stations, train and distance,
- train notification subscriptions (train, date, stations, language).
Data collected automatically
- Device and app data: device model and manufacturer, operating system and version, app version, language, app and advertising identifiers, connection type.
- Usage data: screens and pages visited, clicks, stations searched, visit duration and referring page. On the website — with your consent — also recordings of how a visit unfolds (mouse movement, scrolling, clicks) in Microsoft Clarity; text you type is masked.
- Technical and diagnostic data: IP address, browser type, date and time of requests, crash and error reports from the app.
- Location — only in the app and only after you grant permission in your phone settings. Details in section 8.
- Notification tokens — identifiers that let us deliver a notification to your device (section 9).
We do not process special categories of personal data, such as data about health, beliefs or ethnic origin. We do not obtain data about you from data brokers or from any sources other than those described in this policy.
2. Why do we process your data?
In short: to make our services work, to improve and secure them, to show the ads that keep the app free, and to meet our legal obligations.
- Providing the services — departure boards, train map, search, delay forecasts, widgets.
- Running your account — sign-in, kilometre counter, challenges and rankings.
- Notifications — about delays, cancellations and the upcoming departure of a train you follow.
- Statistics and development — understanding which features people use, where they struggle and what to improve.
- Stability and security — detecting crashes, protecting against abuse and attacks.
- Advertising — showing ads in the app and on the website (section 10).
- Contacting you — answering messages and reports.
- Legal obligations and legal claims — for example responding to a request from a competent authority.
3. What legal bases do we rely on?
In short: we only process data when the GDPR allows it — most often because it is necessary to provide the service, based on your consent, or based on our legitimate interest.
| Purpose | Legal basis (GDPR) |
|---|---|
| Account, kilometre counter, rankings, train notifications | performance of the contract for our services — Art. 6(1)(b) |
| Location in the app | consent given in your phone settings and performance of the contract — Art. 6(1)(a) and (b) |
| Personalised ads, analytics cookies and Clarity recordings on the website | consent — Art. 6(1)(a) |
| Crash reports, security, abuse prevention, basic statistics | legitimate interest — Art. 6(1)(f) |
| Answering messages | legitimate interest — Art. 6(1)(f) |
| Legal obligations, e.g. tax or towards authorities | legal obligation — Art. 6(1)(c) |
| Establishing, exercising or defending legal claims | legitimate interest — Art. 6(1)(f) |
You can withdraw your consent at any time: on the website through the “Cookie settings” link in the footer, and in the app in your phone settings. Withdrawing consent does not affect the lawfulness of processing carried out before the withdrawal.
4. Who do we share data with?
In short: with the service providers we use to run Trainradar24. They act on our instructions or — for advertising — as independent controllers. We do not sell data.
| Provider | What we use it for |
|---|---|
| Google — Firebase | statistics, crash reports, push notifications, running the app and website |
| Google — AdMob and AdSense | ads in the app and on the website |
| Google — Maps Platform | maps in the app |
| Google and Apple — sign-in | confirming your identity when you sign in |
| Apple — Push Notification service | notifications and Live Activities on iOS |
| Microsoft — Clarity | click maps and visit recordings on the website |
| Hosting and infrastructure providers (data centres in the EU) | servers, database, backups |
| Network and security service providers | delivering and protecting traffic to our services |
| Technical tool providers | error monitoring, 3D map view, sending emails |
We may also share data:
- with competent authorities where the law requires it,
- with a legal successor in the event of a merger, sale or restructuring of our business — subject to this policy.
5. Is data transferred outside the European Economic Area?
In short: some providers (including Google and Microsoft) are based in the United States. Such transfers rely on the safeguards provided for in the GDPR.
Our database is located in the European Union. Providers based in the United States may, however, also process data outside the EEA. Such transfers are based on the European Commission’s adequacy decision under the EU-US Data Privacy Framework (for companies certified under it) or on standard contractual clauses approved by the European Commission. You can request a copy of these safeguards at the address given in section 18.
6. Cookies and similar technologies
In short: the website uses essential, analytics and advertising cookies. In Europe, the last two are used only with the consent you give in the consent window.
Cookies are small files stored in your browser. Identifiers stored in browser storage and advertising identifiers on your phone work in a similar way. On trainradar24.eu we use:
| Type | Tool | Purpose |
|---|---|---|
| Essential | Trainradar24, Google (consent window) | remembering your choices, e.g. consents, a dismissed notice, language |
| Analytics | Google Analytics (Firebase), Microsoft Clarity | visit statistics, click maps, visit recordings |
| Advertising | Google AdSense and Google’s advertising partners | showing and measuring ads, including — with consent — interest-based ads |
The consent window is provided by a Google platform that follows the IAB Transparency & Consent Framework. You can change your choices at any time through the “Cookie settings” link in the website footer. You can also delete or block cookies in your browser settings; some features of the website may then work less well. You can also opt out of Google Analytics with Google’s browser add-on.
7. Signing in with Google and Apple
In short: from Google or Apple we only receive your email address and confirmation that it is you.
When you sign in with Google or Apple, the provider sends us a confirmation of your identity and your email address. We do not receive your password, contacts, name or photo. We then create an account with a random username. How Google and Apple process your data is described in their own privacy policies.
8. Location and the kilometre counter
In short: location shows you on the map. It is sent to our server only when you are signed in and have started a journey — then we count the kilometres you travel.
- Showing your position on the map and finding nearby stations happens on your device.
- Kilometre counter: when you are signed in and start a journey, the app sends your location to our server to add the kilometres you travel to your account.
- Background location: if you allow it, the counter also works with the screen off, but only during an ongoing journey. On Android you then see a persistent “Counting kilometres” notification.
- Raw location points are deleted automatically after 60 days at the latest. A summary of your journeys (sections, distance, date) is kept until you delete your account.
- You can revoke location access at any time in your phone settings. The app will keep working, without the kilometre counter.
9. Notifications
In short: we only send notifications about trains you follow, and only through the channels you choose.
To send a push notification, we store a device token issued by Google (Firebase Cloud Messaging) or Apple, linked to your account and the train you follow. On iOS we also use Live Activities tokens to show your journey on the lock screen. If you choose email notifications, we send them to your account’s email address. You can turn notifications off in the app or in your phone settings; tokens of inactive devices are removed automatically.
10. Advertising
In short: ads keep Trainradar24 free. They are delivered by Google; in Europe, interest-based ads are shown only with your consent.
Ads in the app are served by Google AdMob and on the website by Google AdSense. Google and its partners may use your device’s advertising identifier or cookies to show ads, measure their performance and prevent fraud. If you do not consent to personalised ads, you may still see ads, but they will not be based on your interests. You can reset or limit your advertising identifier in your phone settings. More on how Google uses data: policies.google.com/technologies/partner-sites.
11. Server for AI assistants (MCP)
In short: AI assistants fetch train data from us. We do not receive your conversation with the assistant.
At mcp.trenify.eu we provide a free server from which AI assistants (e.g. Claude, ChatGPT) retrieve data about trains in Poland.
- We only receive the query sent by the assistant, such as a station name, a date or a carrier name. We do not receive your conversation, name, email address or location.
- The IP address is used only to protect against abuse. It is processed briefly and we do not store it.
- We log the name of the tool used, the response time and error information — without query content and without IP addresses — for up to 7 days.
- Your conversation with the assistant is processed by its provider (e.g. Anthropic, OpenAI) under its own terms, which we do not control.
12. How long do we keep data?
In short: for as long as needed for the purpose we collected it for; after that we delete or anonymise it.
| Data | Retention period |
|---|---|
| Account, kilometre statistics, journey history, subscriptions | until you delete your account |
| Raw location points | up to 60 days |
| Notification tokens | until you sign out, delete your account or the inactive device is removed automatically |
| Encrypted database backups | up to 30 days |
| Server logs (including IP addresses) | for a short period needed for diagnostics and security |
| Server error reports | up to 90 days |
| Google Analytics statistics | detailed event data up to 2 months; aggregated reports without identifying data — no time limit |
| Microsoft Clarity recordings and click maps | recordings up to 30 days, aggregated click maps up to 13 months |
| MCP server logs | up to 7 days |
| Correspondence | until the matter is closed, then for the limitation period of any claims |
When you delete your account, we delete it from our database immediately, together with your location and journey history. Positions in archived rankings remain without any link to you. Backups are overwritten within the period stated above.
13. How do we protect data?
In short: we use technical and organisational measures, but no system is completely immune to attacks.
Connections to the app, the website and our servers are encrypted, and so are our backups. Only authorised people have access to the data. Despite these measures we cannot guarantee that transmitting data over the internet is completely secure. If a personal data breach occurs that may put you at risk, we will inform you and report it to the Polish supervisory authority (UODO).
14. What are your rights?
In short: you have the right to access, rectify and erase your data, to restrict processing, to data portability and to object, as well as the right to lodge a complaint with a supervisory authority.
Under the GDPR you have the right to:
- find out whether we process your data and obtain a copy of it,
- have inaccurate data corrected,
- have your data erased — the easiest way is to delete your account in the app settings,
- restrict processing,
- receive the data you provided to us and transfer it to another controller,
- object to processing based on our legitimate interest,
- withdraw your consent at any time.
To exercise these rights, write to support@tr24.eu. We will respond without undue delay and within one month at the latest. We may ask for information confirming that the request comes from the person the data relates to. You also have the right to lodge a complaint with the President of the Personal Data Protection Office in Poland (UODO, ul. Stawki 2, 00-193 Warszawa, uodo.gov.pl) or with the supervisory authority in your country of residence.
We do not make decisions about you based solely on automated processing that produce legal effects or similarly significantly affect you. Delay forecasts concern trains, not people.
15. Children
In short: accounts are for people aged 16 and over; younger users need the consent of a parent or guardian.
Anyone can use the train information without an account. Accounts may be created by people aged 16 or over. A younger person may create an account only with the consent of a parent or legal guardian. If we learn that an account belongs to a child under 16 without such consent, we will delete it. Parents or guardians can contact us about this at support@tr24.eu.
16. Where does the train data come from?
In short: from official open data published by infrastructure managers and railway operators. It contains no personal data.
Timetables, delays, disruptions and train positions come from open data published by infrastructure managers and railway operators — in Poland, among others, the open API of PKP Polskie Linie Kolejowe S.A. Our algorithms use it to calculate, for example, delay forecasts and punctuality statistics. This data is indicative only — the rules for using it are set out in our Terms of Use.
17. Changes to this policy
In short: we update this policy when our services or the law change.
The current version is always available on this page, and the date of the last change is shown at the top. We will also announce significant changes in the app or on the home page.
18. Contact
Questions about this policy and your data can be sent to support@tr24.eu or by post:
Trenify P.S.A.ul. Półwiejska 17/26
61-888 Poznań
Poland