Privacy policy · effective 14 October 2026

What OnTrack knows, and what it doesn't.

The short version: your trips live on your phone. OnTrack's own server keeps the trips you asked it to watch until the trip is over, and the routes of drives that Train vs car times until 90 days after their last use. If you choose to share trip outcomes or drive times, it keeps those too, with nothing that identifies you. The app uses location in the background only if you turn on Record my drives, and then only to time a drive you saved. There are no accounts, no advertising, no tracking and no sale of data.

Who is responsible. OnTrack is made and operated by Hisham Abboud, Eindhoven, the Netherlands, as a sole developer. Contact details are at the end of this page.

On your phone

Everything you enter stays in the app's own storage on your device: saved trips and routes, your settings, the reliability tables, and a small local log of which features you used. That usage log never leaves the phone; it exists so the app can show you your own weekly review. It is deleted with the app.

A train ticket you give the app, as a photo, a screenshot or the ticket's PDF, is read on your phone. The picture or PDF is not kept and not sent anywhere. What the app reads from it, the stations, the day and the time, goes to the journey planner only to find that train, as with any search you type.

Location

OnTrack asks for location while you use it. The one exception is Record my drives, which is off unless you turn it on: then, and only if you also allow location Always, the app uses location in the background to time the drives you saved, as described under Recorded drives. While you use the app, it uses your position to find the nearest station, to plan a walk to your stop, to show live departures nearby and to fetch the weather for where you are.

To do those things, your coordinates are sent to the services that answer the question: the journey planner receives an origin and a destination, and the weather service (Open-Meteo) receives the coordinates for a forecast. For a journey within the Netherlands the planner is OnTrack's own copy of MOTIS, an open-source router, running on our server; it plans the journey and keeps no record of where from or where to. Any other journey, or a Dutch one our planner cannot answer, goes to Transitous, the public European service built on the same router. None of them receives your name or any identifier of you or your phone. Two features send your position to OnTrack's own server: planning a journey within the Netherlands, as above, and a drive you plan by car from where you are, as described under Train vs car. Nothing else sends your position to us, and nothing stores it on our side.

While a trip is under way and the app is open, it also notes how fast you walk between rides, so walking times match your pace. That stays on your phone.

The watch server

When you save a trip and turn alerts on, the app can ask OnTrack's server to watch that trip while the app is closed, so a warning still reaches you. For that, and only for that, the app sends the server:

  • a push token for your phone, issued by Apple, which lets the server send you a notification and nothing else;
  • the watched trip's origin, destination, planned departure and whether alerts are on;
  • for a watched drive, its route, so the drive can be timed while the app is closed. When the drive starts where you are, so does the route;
  • while a Live Activity is showing, a token for that activity, so its Lock Screen state can be updated.

The server keeps no accounts and no analytics. A trip row expires shortly after its planned departure; the alert history it keeps for your device covers the last 45 days and is used to avoid sending the same warning twice. Turning alerts off or deleting a trip removes it from the watch on the next sync. Deleting the app ends the watch: the push token stops working and the rows expire on their own.

Today this server-side watch is offered for Dutch train trips. Other trips are watched by the app itself when iOS wakes it in the background.

Friends

Friends is optional. You and a friend become friends by swapping a six-character code, which works once and expires after 24 hours. For this the app gives OnTrack's server an install id, made once by the app and kept on your phone, and the name you type. Your friends are shown a stand-in for that id, never the id itself and never your phone's push token.

While you have at least one friend and Share my trips with friends is on, the app sends the server your trips for the next 14 days, in the same form as a share link: where from and where to, the stops, lines, times and platforms. Your friends see them, with the server's live word on them: running late, cancelled, a moved platform, a missed change, when the last ride got in. That live word comes from the operators' public feeds about the train, bus or tram, never from your phone's position. A shared trip is deleted 24 hours after it leaves.

A friend can turn on alerts about your trips, or about one trip when they plan to pick you up. Nobody gets alerts about you unless they turned them on themselves, and your Friends screen shows who has, for example "Mum gets alerts about your trips". The server keeps who turned alerts on for whom until they turn them off or the friendship ends; alerts for a pick-up end 12 hours after that trip leaves. To follow a trip someone has alerts on, the server reads its rides on the operators' live feeds and keeps what it read about the journey's arrival for three days.

Turn off Share my trips with friends and your trips are taken down at once. Removing a friend ends the friendship both ways, with every alert between you. A pick-up you plan stays on your phone: the server learns only that you want alerts about that one trip of your friend's, which your friend can see.

Train vs car

With Train vs car on, the app compares a drive with the train and says how long the drive takes at the hour you leave. To do that, it sends the drive to OnTrack's own server, which times it against public road-sensor history. The server receives:

  • the drive's route: the line your map app drew from its start to its end. When you plan from where you are, that line starts at your current position;
  • the names of the start and the end, which can be a street address, and the minutes your map app planned;
  • for a saved drive, its usual departure time and the minutes you allow for parking; for a comparison, the train's minutes and the time you want to leave.

The server keeps the route under an id the app makes for that drive, so it can answer again without the route being sent again. It is not stored with your name, an account or your phone's push token. A route is deleted 90 days after the app last sent or used it. If you also asked the watch server to watch that drive, both servers know the drive by the same id.

Turn off Train vs car in Settings and the app stops sending drives for it, and shows your map app's own drive times instead. A drive you asked the watch server to watch is still sent for the watch, as described above.

Shared trip outcomes

Share trip outcomes is off unless you turn it on, in Settings or when the app asks you once after your first "How'd it go?" answer. With it on, the app tells OnTrack's own server two things, so that the odds other riders see can learn from what actually happened:

  • when you answer "How'd it go?" for a trip with a change: the station where you changed, whether you made the change, the kind of vehicle on each side, the minutes the plan gave you to change, the app's own estimate of the chance of missing it, and the date. A missed change is shared only for a trip with one change;
  • when you tap "Nothing came?" while waiting at a stop: the stop, the line and the planned departure time.

Nothing else is sent with them: not your position, your name, your phone's push token, an install id or which of your trips it was. The server does not store your network address with them. It keeps the change answers for 400 days and the "nothing came" reports for two days, and it gives them out only as totals: a station's changes once at least five answers stand behind them, and the reports of the last three hours.

Every copy of the app reads those totals, whether or not it shares: once a day for the countries you travel in, and while a trip of yours is about to leave. Turn the switch off and the app stops sending at once. What it already sent carries nothing that leads back to you, so it cannot be picked out for removal either.

Recorded drives

Record my drives is off unless you turn it on in Settings. It times the car trips you saved, door to door, and because a drive starts with the app closed it needs location in the background, so it works only if you allow location Always. With it on, the app asks your phone to tell it when you leave a circle of about 200 metres around the start of a saved drive. Only then does it switch location on, and it uses each position for one thing: to tell whether you are driving and how far you are from the end. It switches location off again when you arrive, or when the drive has run far longer than planned.

What is kept is one line per drive: which saved drive, when you left, when you arrived, the minutes it took and the minutes the app had planned, and whether you stopped for ten minutes or more on the way. The two ends are kept only to the nearest 150 metres. No route is stored and no position along the way. The lines stay on your phone for 90 days. Once five drives of the same saved drive are recorded, the app's chance of arriving on time for that drive leans on them.

Share drive times is a second switch, also off unless you turn it on. With it on, after each recorded drive the app sends OnTrack's own server the id of the saved drive (the same id described under Train vs car), the minute you left, the minutes it took, the minutes the app had planned and whether you stopped on the way. Nothing else goes with them: not a position, your name, your phone's push token or an install id. The server keeps them with the drive's route, so they are deleted with it, 90 days after its last use. They are kept so the server's drive times can be checked against drives that really happened.

Turn off Record my drives and location stops at once. Erase drive memory, in Settings, deletes every recorded drive on your phone and asks the server to delete the drive times you shared for them.

Voice assistant

The Ask tab is optional. If you use it with your voice, the app records audio while you hold the microphone and sends that audio to Deepgram to turn it into text. Your typed or transcribed question, together with the context needed to answer it, is sent to Google's Gemini model: the trips you have saved, with their stations, times, reliability lines and any active delays. Nothing else from your phone is included, and no location is attached.

These two providers process the request to produce the answer. Their own terms govern what they retain; OnTrack does not use assistant conversations for advertising or profiling, and does not store them on its server. The microphone and speech permissions exist solely for this feature, and the app works fully without it.

Services the app talks to

OnTrack has no analytics or advertising SDKs. It calls the following services directly from your phone, for the purpose listed. Each receives only what that purpose needs.

  • NS Reisinformatie (Dutch Railways): live departures, disruptions and journey details for Dutch train trips. Receives station codes and times.
  • OVapi (Dutch public transport open data): live departures and service alerts for bus, tram, metro and ferry.
  • iRail: Belgian rail disturbances.
  • DB timetables via transport.rest: German station boards.
  • SNCF and transport.data.gouv.fr: French rail alerts.
  • Transitous (MOTIS): journey planning outside the Netherlands, and within it whenever OnTrack's own planner cannot answer. Receives origin, destination and time.
  • NDW and the Autobahn API: Dutch and German road incidents and travel times.
  • Open-Meteo and Buienradar: weather and rain radar for your location.
  • Apple Maps, Google Maps, Waze: opened on your request for navigation. What you do there is covered by their policies.
  • Deepgram and Google Gemini: the voice assistant, as described above.
  • OnTrack's own server: the trip watch, Friends, Train vs car and, if you turn them on, Share trip outcomes and Share drive times, as described above.

Notifications and calendar

Notifications are optional and come from the app itself or from the watch server. If you grant calendar access, the app reads event times on the device to suggest arrival times that match your meetings. No calendar data is sent anywhere. The camera permission string exists because the audio capture API requires it; OnTrack never takes photos or video. It reads only the photos, screenshots and PDFs you choose to give it, one at a time, as described under On your phone.

What we never do

  • No accounts, no sign-in, no email collection.
  • No advertising, no ad identifiers, no tracking across apps or sites.
  • No sale, rental or sharing of personal data with anyone.
  • No location in the background, except to time a drive you saved while Record my drives is on. No record of where you drove.
  • No profiling of your travel beyond the trips you save on your own phone.

Your data and your rights

Because your data lives on your phone, you control it directly: delete a trip to remove it, or delete the app to remove everything. Server rows tied to your push token expire on their own after the trip, and a drive's route 90 days after its last use, with any drive times you shared for it. Erase drive memory in Settings deletes your recorded drives from the phone and asks the server to delete the ones you shared. Because a route carries nothing that identifies you, write to us with the drive's start, end and date if you want it removed sooner. Under the GDPR you may ask what we hold about you, ask for it to be corrected or erased, or object to processing; write to the address below and include the approximate date of the trips you asked us to watch, since we have no other way to identify you. You may also complain to the Dutch Data Protection Authority (Autoriteit Persoonsgegevens).

OnTrack is not directed at children under 16 and does not knowingly collect their data.

Changes

If this policy changes, the new version is published here with a new effective date. Material changes are also announced in the app.

Contact

Hisham Abboud · Eindhoven, the Netherlands · [email protected]

To report a security problem, see the security page.