Privacy Policy
The short version
Everything you log stays on your phone. Your vehicles, fill-ups, charges, expenses, reminders and settings are written to a database inside the app's own storage and are never sent anywhere. There is no account to create, no OdoTick server to sync to, and no way for us to see what you drive, what you pay for it, or how far you go.
OdoTick has no ads and no ad SDK, free or Plus. Nothing in the app profiles you, and there is no advertising identifier anywhere in it.
Two services do receive something, and neither of them receives your data: Firebase Crashlytics gets an anonymous report when the app crashes, so defects get fixed, and RevenueCat and Google Play get your purchase receipt if you buy OdoTick Plus, so it can be validated and restored on a new phone. Each has a section below saying exactly what it holds.
The rest of this page explains that in full, because "it stays on your phone" deserves to be backed up with specifics.
1. Who we are
OdoTick ("OdoTick", "we", "us") is an independently developed vehicle running-cost tracker for
Android, published on Google Play as com.jaironlanda.odotick by Jairon Landa. This
policy explains how the app and the website at
odotick.com handle information.
If you have any question about this policy, you can reach a human at jaironlanda@gmail.com.
2. What we collect
Nothing about your driving. To be specific, OdoTick does not:
- ask you to create an account, sign in, or give us an email address;
- send your vehicles, odometer readings, fill-ups, charges, expenses, notes, reminders or settings to us or to anyone else;
- include any analytics or usage-measurement software;
- include any advertising SDK, ad network, ad-consent flow, or advertising identifier — OdoTick has no ads at all, in the free app or with Plus;
- include any social media SDK or third-party tracker;
- build a profile about you, or share, sell or rent information about you;
- request or use your location, contacts, photos, camera or microphone; or
- look up fuel prices, nearby stations, or anything else over the network as you use it.
We operate no servers. There is no OdoTick backend for your information to be sent to, which is the simplest guarantee we can offer: we cannot lose, leak, subpoena or sell data we never receive.
Two third-party SDKs inside the app do talk to their own providers — crash reporting and purchases. They are covered in section 6 and section 7, and neither receives anything you have logged.
3. What the app stores on your device
OdoTick is useless without remembering what you spent, so it stores that locally, in a private SQLite database inside the app's own storage area, which other apps cannot read. This information never leaves your phone unless you deliberately export it (see Exports and backups).
| What | Examples |
|---|---|
| Your vehicles | The name and colour you gave each one, its energy type, currency and units, its starting odometer, and optionally the make, model, year, tank or battery capacity and purchase price. |
| Your entries | Fill-ups, charges and other costs: the date, the odometer reading, the quantity in litres or kWh, the unit price and total, the category, whether it was a full tank, the charge source (home, work or public), and any note you typed. |
| Your reminders | What each one is for (roadtax, insurance, service and so on), its due date, how far ahead it should nudge you, whether it repeats, and whether you have marked it done. |
| Your settings | Theme, language, distance and volume units, reminder time of day, whether the active car's colour tints the app, and which vehicle is active. |
| App state | Small flags that make the app behave properly — whether you have finished onboarding, and whether OdoTick Plus is currently unlocked on this device. |
Odometer readings and fuel stops can say something about where and how much you drive. We treat them accordingly: they are kept on your device, they are not transmitted, and they are not used for any purpose other than showing you your own figures inside the app.
4. Permissions the app asks for
Notifications (optional)
If you save a reminder, Android asks your permission to post notifications — at that moment, not at launch, so you are asked only once the permission has a purpose. You can decline, or turn notifications off later in Android's settings, and the rest of the app works normally; the reminder list still shows what is due and overdue.
Run at startup
OdoTick declares RECEIVE_BOOT_COMPLETED. Android clears every scheduled alarm on a
reboot and on an app update, so without this the reminders you had set would silently stop
arriving. It is granted at install, needs no prompt, and is used for nothing else: on boot the
app re-arms the reminders that are already in your own database.
Files (only when you use them)
Exporting a CSV or a backup writes a file and hands it to Android's share sheet, where you choose what happens to it. Restoring asks you to pick a file. The app only ever touches the file you select for that action; it cannot browse your storage.
What OdoTick never asks for
No location, no contacts, no calendar, no camera, no photos, no microphone, no phone state and no advertising identifier. The app does not request exact-alarm permission either — its reminders use inexact alarms, which is why they arrive around the time you chose rather than to the second.
5. Reminders and notifications
Reminder notifications are scheduled and posted entirely by your own phone, at the dates and lead times you set. They are not push notifications: there is no server sending them, no device token, and no record anywhere of whether one was delivered, seen or tapped. The Log cost and Mark done buttons on a notification act on the database on your phone and nothing else.
A notification's text is drawn from the reminder you wrote, so it can appear on your lock screen. That is your device's notification setting to control, per reminder type, in Android's own settings.
6. Crash reporting (Firebase Crashlytics)
OdoTick includes Firebase Crashlytics, from Google, so that when the app crashes we find out and can fix it. This is the one piece of the app that reports back without you asking it to, and it is worth being precise about what it sends.
| A crash report contains | It does not contain |
|---|---|
| The stack trace — the list of functions the app was inside when it failed, plus the line numbers. | Any vehicle, entry, reminder, note, odometer reading or amount you have logged. |
| Device model, manufacturer, Android version, orientation, available memory and storage, and whether the app was in the foreground. | Your name, email, Google account, phone number or contacts. |
| The app version and build, the time of the crash, and a randomly generated installation identifier so repeated crashes on one device can be counted as one problem rather than many. | Your location, and any advertising identifier. |
We see these reports grouped by defect, not by person. Crashlytics is configured with its default retention, and Google processes the reports on our behalf as our service provider. See Firebase Privacy and Security and the Crashlytics data description.
7. Purchases and OdoTick Plus
OdoTick Plus is sold through Google Play Billing and managed with RevenueCat, which validates the purchase and lets you restore it on a new phone. If you never buy Plus, the app still contacts RevenueCat to ask which plans and prices to show on the Plus screen; that request carries no personal information about you.
What Google gets
Your payment method and billing details are handled entirely by Google. We never see or receive your payment information. Google is the seller of record, and what it holds is covered by the Google Privacy Policy.
What RevenueCat gets
A pseudonymous app user ID generated on your device (not your name, not your email, not your Google account), your purchase receipt from Google Play, and basic device and store metadata such as country, platform and app version. For a subscription it also holds the renewal and expiry dates, the trial state, and whether the subscription is active — the app has to know whether Plus is still running. It receives none of your vehicles, entries or reminders. See the RevenueCat Privacy Policy.
What that means in the app
Plus unlocks against the Google account on the device, not against an OdoTick account, because there is no such thing. Cancelling a subscription in Google Play ends the Plus features at the end of the period you paid for and never deletes anything you logged — your history stays, and the app keeps tracking. See the Terms of Service for billing, the free trial and cancellation.
8. Exports and backups
OdoTick Plus can export your entries as a CSV file and write a full backup file of your ledger. Both are manual actions you trigger. There is no automatic export and no cloud backup.
Once that file exists, it is yours and it is your responsibility. If you save it to a cloud drive, email it to yourself, or send it to your accountant, it has left your phone and is covered by whatever policy that service or person has, not by this one. We never receive it, and we cannot recall it.
Restoring a backup replaces what is currently on the device. The app warns you before it does that.
Separately, Android's own system backup may include app data, depending on your device and your Google account settings. That mechanism belongs to Google and Android and is controlled from your device's backup settings, not from OdoTick.
9. The full list of third parties
Four, and you can check each one against the sections above. Nothing else in the app talks to anything.
| Who | Why | What they get |
|---|---|---|
| Google Play | Distribution — you installed the app from there | That you installed it. We can see anonymous, aggregated Play Console figures such as installs per country, never who you are. |
| Google Play Billing | Selling OdoTick Plus | Your purchase and payment details. We never receive them. |
| RevenueCat | Validating and restoring the Plus entitlement | A pseudonymous ID, the purchase receipt, device and store metadata, and subscription dates. No vehicle data. |
| Firebase Crashlytics (Google) | Fixing crashes | Anonymous crash reports and device metadata. No vehicle data. |
That is the whole list. There is no fifth party. If we ever add a service that changes this, we will update this policy and say so in the app's release notes before it ships.
10. This website
This site is a set of static pages hosted on Cloudflare. It sets no cookies, runs no analytics and no JavaScript, embeds no third-party fonts, scripts, pixels or share buttons, and asks you for nothing.
Like any website, requests reach it over the internet, so Cloudflare, as the hosting and network provider, processes standard technical information such as your IP address in order to serve the page and protect against abuse. That processing is Cloudflare's, described in the Cloudflare Privacy Policy. We do not add tracking on top of it and we build no profile from it.
11. Your rights and choices
Privacy laws such as the GDPR, the UK GDPR, the CCPA and Malaysia's PDPA give you rights over personal data a company holds about you: to access it, correct it, export it, or have it deleted.
These rights are largely self-service here, because we hold no personal data about you. There is no account to look up and no record with your name on it. In practice:
- Access: your data is already in your hands, in the app.
- Portability: export it yourself as CSV or a backup file at any time with OdoTick Plus — it is plain, readable data, not a locked format.
- Correction: edit or delete any entry, vehicle or reminder in the app.
- Erasure: see Deleting your data.
- Objection and opt-out: there is no profiling, no targeted advertising and no sale of personal information to object to. We do not sell or share personal information, and never have.
For the crash reports and purchase records described above, write to jaironlanda@gmail.com and we will do what we can — though a crash report is not linked to your identity, so in most cases there is nothing to look up. For data Google holds because of your install or purchase, those rights are exercised with Google.
12. Deleting your data
Because everything is local, you are always one step away from deleting all of it, with no request to file and no waiting period.
- Delete one entry, vehicle or reminder: remove it in the app.
- Delete everything: uninstall OdoTick, or go to Android Settings → Apps → OdoTick → Storage → Clear storage. That permanently erases the database, the settings, and every reminder that was scheduled.
- Delete an export you made: that file is wherever you sent it, so delete it there.
This is irreversible. Your history exists only on your device, so we cannot restore it for you — we do not have it. Export a backup first if you want to keep it.
Uninstalling does not cancel a subscription. Cancel that in Google Play (see the Terms of Service).
OdoTick has no user accounts, so there is no account to delete and no account-deletion request to make.
13. Children
OdoTick is a general-audience app aimed at people who run a vehicle, and it is not directed at children. We do not knowingly collect personal information from anyone, children included, because there is nothing to collect. The app contains no ads, no chat, no social features and no user-generated content from anyone but you.
14. Security
Your data lives in your device's app-private storage, protected by Android's application sandbox and by your device's own lock screen and encryption. Because your ledger is never transmitted to us, there is no server-side breach that could expose it.
The practical risks are local ones, and they are in your control: someone with an unlocked phone can open the app, and an export you have made is only as safe as wherever you put it.
15. Changes to this policy
If this policy changes, we will update the "last updated" date at the top of this page. If a change ever materially affects your privacy — if the app started collecting something, say — we will make that clear in the app before it takes effect, rather than quietly editing this page.
16. Contact
Questions, concerns, or a privacy request? Email jaironlanda@gmail.com and you will get a reply from the person who makes the app.