Mileage Tracker Unlimited

Privacy policy

Updated 25 October 2026

The short version: your trips are on your phone, with a backup in your own iCloud or Google Account. There is no account, no server of ours, and we cannot reach your data, not even that backup. This applies to the app on iPhone and on Android.

Who is responsible

Rittenregistratie is made and published by Socialista (Marvin Visser), Amsterdam, the Netherlands, registered with the Dutch Chamber of Commerce under number 61396478. Questions about this policy or about your data go to [email protected].

What the app records

The app records what a correct mileage log needs:

  • Location data: the points of your route, with time, speed and accuracy.
  • Trip data: start and end time, distance, category, the purpose you type, odometer readings and notes.
  • Vehicles and places: the cars you add and the places you set a rule for, such as home or the office.
  • Settings: your country, your working hours and which ways of starting you have switched on, and which beacon, car radio or NFC sticker belongs to which car.

All of it sits in a database in your own device's storage. It is not sent to us and we have no access to it. If you back up your iPhone, that database travels inside your own backup, under your control. On top of that the app makes a backup of its own; how that works is described below.

Backup

So that you do not lose your trips when your phone breaks or you switch phones, the app makes a backup by itself. It is on by default and you can switch it off under Settings in the app.

  • iPhone: after a change, the app puts a copy of your trips and settings in your own iCloud, in the app's private database (CloudKit). That copy belongs to your Apple Account.
  • Android: the app keeps a compact backup file, and Android includes it in your phone's Google backup, if that is switched on. Google makes that backup roughly once a day, while your phone is charging. The database itself is not included, only that file.

Switch the backup off and the app deletes that copy: on an iPhone from iCloud, on Android the backup file, which then also disappears from the Google backup.

You can also make a backup yourself. The app writes a single file that you keep wherever you like: in Files, iCloud Drive, Google Drive or in an email to yourself. Restoring reads that file back in. A file from an iPhone works on Android, and the other way round. After a fresh install the app offers to restore the automatic backup. Restoring merges: trips that are already on your phone stay there.

A backup contains your trips with their routes, your vehicles, odometer readings, places, labels, the change log and your preferences, such as country, rate, working hours, ways of starting and notifications. Not included: anything that belongs to this one device, your permissions, and the ad-free purchase. That last one comes back through the App Store or Google Play.

We have no server for any of this and cannot reach your backup. The copy sits in your iCloud or your Google Account, under Apple's or Google's terms and privacy policy. A backup file you keep yourself stays wherever you put it.

What the app uses your location for

Only to measure your trips. The app asks for the Always location permission, because otherwise a trip stops the moment you close the app or pocket your phone. You can also choose While Using; the app then works, but only with the app open.

To show the start and end address of a trip, just that one location is turned into an address. On an iPhone Apple's mapping service does that, on Android the Google address service built into your phone, each under its own privacy policy. Only that one point is sent, not the trip and not the route. If the app only notices a trip a little after you set off, it fills in the missed stretch from where you parked along the road. On an iPhone it asks the same Apple mapping service for that route; only two points are sent for it: where the car was parked and a point just after you set off. We see none of it. The map in the app comes from Apple on an iPhone and from Google Maps on Android. They see which part of the map you are looking at, plus technical data such as your IP address and phone model, each under its own privacy policy. The app draws your route on top itself; the route is not sent.

If you allow Motion & Fitness (iPhone) or Physical activity (Android), the app reads on your device whether you're in a car, walking or cycling. That way a trip starts on time and stops when you get out. That activity goes nowhere. On Android the app keeps the transitions on your device for a week, so that even after a restart it knows since when you have been driving.

If you set up a beacon, your car radio or your car's screen (CarPlay or Android Auto) as a way of starting, the app checks on your device whether the beacon, radio or car is nearby or connected. On Android that needs the Nearby devices permission. That goes nowhere either.

Advertising

The app is free and shows a banner at the bottom, delivered by Google AdMob. For advertising, data about your device may be processed, such as an advertising identifier, your coarse location at country or city level, and device information. Google does that as an independent controller, under the Google privacy policy.

Before any ad loads, you get a consent dialog in Europe where you can choose per purpose. You can change that choice later under Settings in the app. On an iPhone, iOS also asks by itself whether the app may track your activity; saying no costs you no features. On Android you can delete your phone's advertising ID yourself in Android's settings.

Your trips never go into this. The advertising module gets no locations, no routes, no trips and no vehicle data. If you want no ads at all, you can turn them off with a purchase in the app.

Purchases

Turning ads off runs through Apple's App Store or through Google Play, as a subscription or as a one-time purchase. We see no payment details; through Apple or Google we only see whether a purchase was made. Apple's or Google's privacy policy applies to the payment itself.

What we collect

Nothing. There is no analytics package in the app, no crash reporting to us, no server of ours and no account. We do not know how many trips you make, whether you still use the app, or where you drive.

How long data is kept

As long as you keep it. Delete a trip and it becomes invisible in the app and counts nowhere; an empty trace stays in the database so the change log keeps its continuity, which tax rules require. Delete the app and the whole database goes with it. The automatic backup then stays in your iCloud or Google Account, so you can restore it on a new phone; if you want that gone too, switch the backup off before you delete the app. We cannot restore anything, because we hold nothing.

Your rights

Because we keep nothing about you, there is nothing at our end to request, correct or erase. Access to your own data is immediate: export a report as JSON and you have it all, route points and change log included. To erase, delete the trip or the app, and switch the backup off. If you have a complaint about processing by Google or Apple, you can go to your national data protection authority.

Children

The app is meant for adults who drive for work and is not aimed at children.

Changes

If something material changes we update this policy and put a new date on it. Big changes are announced in the app as well.

Ordering an iBeacon

If you order an iBeacon, we and our payment provider Stripe receive your name, address and email, only to process and ship the order. This is the only thing on a server of ours, and it is separate from your trips. We erase your address 90 days after delivery. Only Stripe keeps payment details.