Odotur: Mileage Log · com.benbasha.odotur
Privacy policy
In short. Odotur has no account and no server that holds your trips. Your trips, places, purposes, odometer readings and history are stored only on your phone and in backups you make. Maps and address lookups use Apple or Google services. To fix crashes and see which features are used, the app sends pseudonymous usage events (a random install ID, not linked to your name, account or trips) and crash reports that never contain trips, places, km, amounts or text you typed. They are sent only if you agree, and you can turn this off in Settings at any time. No ads, no tracking, nothing sold.
Who is responsible
Odotur (bundle id com.benbasha.odotur) is published by Ben Basha, an independent developer. Contact for anything in this policy: odotur@benbasha.com.
What stays on your phone
Everything you log is stored in a database inside the app on your phone:
- trips: start and end time, start and end point, the route points (thinned to about one per 50 m), measured and estimated km, how the trip was started and ended;
- what you add: category, purpose, business partner, addresses, stops, passengers and their names (Norwegian profile), tolls and parking, notes;
- odometer readings, reconciliations, vehicles (label, plate, kind, fuel, ownership), employers, saved places and routes;
- your profile (country, what you log for, and the name and address you choose to enter for the report), opening balances and settings;
- the change history of all of the above;
- possible drives found from motion data (kept 30 days, then removed if you didn't log them);
- on Android, if you turn on car-Bluetooth prompts, which paired device is your car;
- your Pro purchase status, as last confirmed by the store.
We never receive any of it. Odotur never asks for or stores national ID numbers (CPR, personnummer, fødselsnummer).
Location
- Odotur uses your precise location while a trip is recording, from Start until the trip ends, to measure the distance. iOS shows the location indicator and Android shows the ongoing recording notification for that whole time.
- It also reads your position once when you tap "Use current location" while saving a place (Pro).
- Odotur only asks for "While Using" location on iPhone and foreground location on Android. It does not ask for, and cannot use, background ("Always") location.
- Without location you can still log trips by hand.
Motion and activity, Bluetooth, notifications
- Motion & Fitness (iPhone) / Physical activity (Android): used on the phone to notice that you have parked, so the trip ends by itself, and (Pro) to find possible drives you forgot to record. iPhone looks back at most 7 days. This data is never sent anywhere and is never used for analytics or ads.
- Nearby devices (Android, optional, Pro): asked only if you turn on car-Bluetooth prompts, to notice when your car connects. Stays on the phone.
- Notifications ("Trip saved", trips to classify, odometer due, the recording notification) are created on the phone. There is no push server.
What leaves your phone, and to whom
| What | Data sent | Recipient | When |
|---|---|---|---|
| Map tiles | The coordinates of the map area you view | Apple (MapKit), on iPhone only. On Android the trip shows as a route sketch drawn on the phone, without map tiles. | When a map is on screen |
| Address lookups | The start and end coordinates of a trip, to show its address; the address you type, to find a saved place (Pro) | Apple (iOS geocoder) or Google (Google Play services geocoder) | While the app is open and a trip without an address is shown, or when you look up a place |
| Suggested distance (iPhone) | The from and to text you typed for a manual trip, and the two points found for it | Apple (Apple Maps search and directions) | Only when you tap Suggest |
| Usage events | Fixed event names with fixed values (see below), a random install id, device and app metadata | Mixpanel, as our processor | As you use the app, only with your consent |
| Crash reports | Crash traces, device model, OS and app version, memory and disk state, a Firebase installation id | Google Firebase Crashlytics, as our processor | When the app crashes, only with your consent |
| Purchases | The store transaction | Apple (App Store) or Google (Google Play) | When you buy or restore Pro |
| Store notifications | Refund and purchase status messages, sent by the store, not by the app; no data from the app | Our purchase-status endpoint | When the store reports a change, for example a refund |
| Exports and backups | The PDF, CSV or backup file you create | Only where you send or save it | When you choose to share or save it |
Apple and Google handle map, address and directions requests under their own privacy policies (Apple, Google). We never receive those coordinates or addresses.
Usage events and crash reports
We use Mixpanel to count which features are used and Firebase Crashlytics to fix crashes. We do this only with your consent. The app asks once, and nothing is sent to Mixpanel or Crashlytics before you say Yes. You can withdraw your consent at any time in Settings; from then on, no more usage events or crash reports are sent. Your trips, places and km are processed on your phone, never by us.
- Events have fixed names and fixed values only, for example
trip_endedwithended_by: auto_stillnessandduration_bucket: 5_30,trip_classifiedwithcategory: business,export_donewithformat: csv, the country profile you picked, onboarding steps, permission results, and paywall and purchase steps. Screen views send the screen name only. - An allowlist in the app drops anything else, so events never contain coordinates, addresses, km, amounts, times, trip ids, purposes, names, plates or any text you typed.
- Mixpanel's automatic events are off, and its IP-based location lookup is off, so no location is derived from your connection.
- The install id is a random id created by the analytics library. It is not your advertising id, and it is not linked to your name, email or store account.
- Google Analytics is not part of the app, and on Android the advertising-id permission is blocked.
- Crash reports contain no trip content: no custom fields and no logs with your data.
- Data is sent over encrypted connections (HTTPS). Mixpanel and Google may process it in the United States.
- Retention: usage events are kept according to our Mixpanel project's retention settings; crash reports are kept by Firebase for 90 days.
What Odotur doesn't do
- No account, no sign-up, no email or phone number asked.
- No ads and no advertising SDK.
- No tracking across apps or websites, so no tracking prompt.
- No server of ours that stores your trips. We never see them.
- No selling or sharing of data. Mixpanel and Firebase process data for us only.
- No AI features and no tax advice.
Backups
- Your Odotur backup: Settings > Backup & restore creates one .odotur file with every trip, change, reading and route point. It goes only where you save or send it, and it is yours to keep and delete.
- iPhone: if you use iCloud Backup or back up to a computer, iOS includes Odotur's data in that device backup, as for most apps. That backup is under your Apple account; we can't read it.
- Android: Odotur opts out of Google's automatic app backup and of device-to-device transfer, so your log is not copied to Google Drive. Use the Odotur backup to move it to a new phone.
Keeping and deleting your data
- Your log stays on your phone until you delete it. Delete everything in Settings (confirmed by typing DELETE) removes all trips, history, readings and settings from the phone. Uninstalling the app also removes them. Backups and exports you saved elsewhere are not touched.
- Possible drives you didn't log are removed after 30 days.
- Because usage events are not linked to you, we usually can't find which ones are yours. You can still email odotur@benbasha.com and we will delete what we can match (for example by app version and time). Crash reports are deleted after 90 days. Turning off usage statistics and crash reports in Settings stops all further sending.
Your rights
Under the GDPR and the laws of Norway and other EEA countries, you can ask us for access to, correction of or deletion of personal data we hold about you, object to its use, and complain to your data protection authority (for example Datatilsynet in Denmark or Norway, IMY in Sweden, Autoriteit Persoonsgegevens in the Netherlands, the Datenschutzbehörde in Austria, or your German state authority). Write to odotur@benbasha.com.
What the store privacy labels say
- App Store: Identifiers (device id), Usage Data (product interaction), Purchases (purchase history) and Diagnostics (crash data, other diagnostic data). Not linked to you, not used for tracking. Location: not collected by Odotur; map and address lookups go to Apple.
- Google Play: App activity (app interactions), App info and performance (crash logs, diagnostics), Device or other IDs, Financial info (purchase history), and Location (precise location, processed ephemerally, for app functionality), because address lookups on Android go through Google Play services. Not shared with third parties; encrypted in transit; you can delete your data in the app.
Children
Odotur is a tool for adults who drive for work (on Google Play the target audience is 18 and over). It is not directed at children.
Not tax advice
Odotur helps you keep a driving log. It does not give tax advice and is not affiliated with any tax authority. See the terms of use.
Changes to this policy
If the app starts collecting or sending anything new, this page and the store labels change first, with a new date at the top.