Privacy Policy
Odo keeps a service history for your car. That means it holds real details about you and a vehicle you own, so this page says plainly what those details are, where they sit, and how to get rid of them.
The short version
- Your phone number is the only thing Odo requires. Everything else is optional.
- Photos of bills and documents are read on your phone. The text is extracted there, not on a server.
- If you turn on trip tracking, the GPS coordinates never leave your phone. Only the distance and the times are synced.
- If you turn on automatic fuel logging, Odo reads the merchant name and the amount from payment notifications sent by the payment apps you pick — nothing else, and only on your phone. It is off until you switch it on.
- We do not sell your data, and we do not share it with advertisers or insurers.
- You can delete your account and everything in it yourself, from this website, without installing the app.
Who this is from
Odo operates the Odo mobile app and this website, and decides how the data described below is handled. Under India's Digital Personal Data Protection Act, 2023, that makes us the Data Fiduciary and you the Data Principal.
What we collect
Almost all of it is something you typed or photographed. Nothing here is bought from a third party or inferred from your behaviour on other apps.
| What | Why | Where it lives |
|---|---|---|
| Phone number | It is your account. We verify it by SMS so nobody else can open your service history. | Your phone and our servers |
| Name, email, home city, profile photo | Optional. The city is used to price-check a bill against local rates. | Your phone and our servers |
| Car details — registration number, make, model, variant, fuel type, model year, odometer readings | The record the whole app is built around, and what makes reminders and cost-per-km possible. | Your phone and our servers |
| Service records — dates, workshop name, amounts, categories, your notes | Your service history, and the input to the health score. | Your phone and our servers |
| Bill photos and the line items read from them | So a bill can be checked line by line against typical rates instead of retyped. | Your phone and our servers |
| Vehicle documents — registration certificate, insurance, PUC, driving licence: the file and its expiry date | So the app can warn you before one expires and you can produce it when asked. | Your phone and our servers |
| Reminders, health scores, cost-per-km history | Calculated from the records above and kept so trends survive a reinstall. | Your phone and our servers |
| Fuel fills — date, amount paid, quantity, rate, the fuel station's name, and the odometer reading if you give one | What fuel actually costs you, and the two readings that turn into a measured mileage. | Your phone and our servers |
| Detected payments awaiting your confirmation — the merchant name and the amount, only from payment apps you enabled | So a fill you were shown but have not answered yet is not lost when the notification is dismissed. Deleted once you confirm or reject it. | Your phone only — never sent anywhere |
| Trips — start and end time, distance covered | Only if you switch trip tracking on. Used to keep the odometer current without you typing it. | Your phone and our servers |
| GPS coordinates | Used on the device to measure how far a trip went. | Your phone only — never uploaded |
| Notification token | Lets us push a reminder to your phone. It identifies the installation, not you. | Your phone and our servers |
| Diagnostic logs | Written on your device as the app runs. Uploaded only when you choose to send a problem report. Phone numbers, emails and similar identifiers are masked before the file is written. | Your phone; our servers only if you send a report |
| Crash reports and usage events — screens opened, features used, app version, device model, OS version, and an app-instance identifier Firebase generates for this installation | To find crashes and see which parts of the app are worth improving. Not tied to your name or number, and the identifier is replaced if you reinstall the app or clear its data. Firebase also sees the IP address a report arrives from, which places you in roughly the right city; Odo does not store or use that. | Google Firebase |
What we deliberately do not collect
- Your contacts, call logs, SMS messages or photo library.
- Your chassis or engine number.
- Any advertising identifier. Odo carries no ad SDK and no tracking pixel. The app removes the Android Advertising ID permission that its analytics library would otherwise declare, and switches that library's ad-ID collection off.
Permissions the app asks for
Android asks you before granting any of these, and the app asks at the moment the feature needs it rather than at launch. Declining any of them leaves the rest of Odo working.
- Camera — to scan a bill, a document or a fuel pump's display. Frames are read on the device; nothing is uploaded unless you save the photo to a record.
- Location, including in the background — only for trip tracking, and only after you switch it on. Background access is what lets a trip keep measuring while your phone is in your pocket. The coordinates stay on the device.
- Physical activity — to notice that you have started driving, so a trip can begin without you tapping anything.
- Nearby devices (Bluetooth) — to notice your car's stereo connecting or disconnecting, which is the cheapest signal that a drive has started or ended. We read the connection event, not the device's contents.
- Notifications — to show reminders about an expiring document or a due service, and to show you a fill Odo has detected so you can confirm it in one tap.
- Notification access — optional, off by default, and the one permission worth explaining at length. See below.
Reading payment notifications
Automatic fuel logging works by reading the notification your payment app posts when you pay at a fuel station, so a fill is recorded without you opening Odo. Android has a single switch for this, and its own consent screen warns that an app holding it could read every notification on the phone — some manufacturers add a red warning and a risk checkbox. That warning describes what the permission allows, not what Odo does, so here is what Odo actually does.
- It is off until you turn it on, and turning it off again in Android's settings stops it immediately. Nothing else in the app depends on it.
- Only apps you choose are read. Odo checks the sending app against a list you control before it looks at any text. A notification from any other app — messages, email, banking, anything — is discarded without being read.
- Only two things are taken from it: the merchant's name and the amount. Not the full text, not your balance, not an account or card number, not the sender.
- It is read on your phone. The text is never uploaded, and Odo is never inside the payment itself — it sees the same notification you see, after the payment has happened.
- A payment that does not look like fuel is dropped and nothing is stored. If Odo asks about a merchant that was not a fuel station, telling it so stops it asking again.
- Nothing is saved until you confirm it. A detected fill is held on your phone as an unanswered question until you accept or reject it. Only what you confirm becomes a record, and only confirmed records sync.
- Odo does not have the SMS permission at all, so it cannot read your messages. You can check that yourself in Android's app permissions.
Who else can see it
Only the companies that run the infrastructure underneath Odo. Each of them processes data on our instructions and for no purpose of their own.
- Supabase — the database and file storage holding your records. Hosted in the Asia-Pacific region.
- Google Firebase — sends the SMS that verifies your number, delivers reminder notifications, and collects crash reports and usage events.
- Google Play — distributes the app and handles any purchase you make through it.
We will also disclose data where the law genuinely requires it — a court order or a valid demand from an authority. We do not hand over service histories on informal request, and we will tell you if we are permitted to.
Some of these providers operate outside India. Where your data is processed abroad, it is under contractual terms that keep the protections described here in force.
How long we keep it
- Your records — for as long as your account exists. Nothing expires on its own, because a five-year-old service entry is the point of a service history.
- Deleted records — when you delete a car or a document in the app, it is hidden immediately and cleared from our servers within 30 days.
- Diagnostic logs you sent us — 90 days.
- Your whole account — erased when you ask, see below.
Deleting your data
There are two things you might want to delete, and they are separate.
The copy on your phone
Open Profile → Delete my data in the app, or uninstall Odo. Either clears the local database and the files it saved.
Your account and everything on our servers
Go to Odo · Delete account, verify your phone number by SMS, and confirm. Your profile, cars, service records, bills, documents, reminders, scores and uploaded files are erased immediately and permanently. You do not need the app installed to do this.
One thing survives, and it is not linked to you: the anonymous price points that make bill checking work. When a bill is checked, the amount, the service category and the city are added to a pool that carries no account, car or bill reference and cannot be traced back to anyone. That pool is what lets the next owner know an air-filter change should not cost ₹2,000, and it remains after deletion.
Keeping it safe
- Everything travels over HTTPS, and the database and file storage are encrypted at rest.
- Access rules are enforced by the database itself, per row, keyed to your account — not by the app asking politely.
- Your bills and documents sit in private buckets. Nothing is served by a public link; a file is reached through a signed URL that expires.
- Sign-in is by SMS code. There is no password to leak or reuse.
No system is perfect. If we ever discover a breach affecting your data, we will notify you and the Data Protection Board of India as the DPDP Act requires.
Your rights
Under the DPDP Act, 2023 you can:
- Ask what we hold — a summary of your data and who we have shared it with.
- Correct it — most fields are editable in the app; email us for anything that is not.
- Erase it — the deletion page above does this immediately, no request needed.
- Nominate someone — to exercise these rights on your behalf if you die or are incapacitated.
- Complain — to us first, at the address below, and to the Data Protection Board of India if we do not resolve it.
Children
Odo is for vehicle owners and is not directed at anyone under 18. We do not knowingly collect data from children. If you believe a child has created an account, email us and we will remove it.
Changes to this policy
If we change what we collect or who we share it with, we will update this page and change the date in the footer. For a change that materially affects you, we will also tell you in the app before it takes effect.
Contact and grievances
Write to support.odo.in@gmail.com for anything on this page — a question, a correction, a copy of your data, or a complaint. We answer within 30 days, and usually the same week.