Skip to content

Legal

Driver app privacy policy

For the Odobase Driver app for Android and iPhone.

Last updated

Android package app.odogrid.driver

1. Who we are

Odobase is a fleet management platform operated by EqualPixels, F-16 Ali View Garden, Phase 3, Lahore Cantt, Lahore 58200, Pakistan.

Odobase Driver is used by professional drivers who work for a company that runs its fleet on Odobase. That company — your employer or the operator who assigned your trips, referred to below as the fleet operator — decides what data is collected about you and why. EqualPixels stores and processes that data on their behalf.

This means that for most requests about your data, the fleet operator is the right first point of contact. We will always help if you come to us instead — see requesting deletion.

This policy covers the driver app. For the Odobase website, dashboard accounts and subscription billing, see the website privacy policy.

2. How you get an account

You cannot sign yourself up. Your fleet operator creates your driver record on their Odobase dashboard and enters your phone number. You then sign in to the app with that number and a 4-digit PIN. The app has no registration screen.

3. What the app collects

Your phone number

Used to sign you in and to identify which driver record you are. It is the number your fleet operator already holds for you.

Your location, while a trip is running

When you start a trip in the app, it records your position roughly every 30 seconds and sends those positions to the server about once a minute. Each record holds latitude and longitude, your speed, how accurate the reading was, and the time it was taken. This is what produces the distance and route for the trip.

Recording begins when you start a trip and stops when you complete it. It does not run between trips, and it does not run when you are off shift. Recording continues while the app is in the background during an active trip, and for the whole of that time your phone shows that it is happening: Android shows a notification, and iPhone shows the location indicator. The app cannot begin recording on its own — a trip has to be started by you, in the app.

Photos you attach

If you photograph a receipt for an expense, or an invoice when completing a maintenance job, that image is uploaded and attached to the record. The app only ever reads the image you choose or capture for that purpose; it does not scan your photo library.

What you type into a trip

Odometer readings at the start and end of a trip, and the expenses you log along the way — the type, the amount, and any note. These are work records that belong to the fleet operator.

4. What the app does not collect

To be explicit, the app contains none of the following:

  • No advertising, no advertising ID, and no advertising or marketing SDKs.
  • No third-party analytics or crash-reporting SDK.
  • No background location. The app does not ask for it and cannot use it.
  • No access to your contacts, calendar, messages, microphone or call history.
  • No browsing history, and no tracking of you across other apps or websites.
  • No device identifier or push token is sent to our servers.

5. Why we collect it

Every item above exists to make the app work for the job it does: signing you in, showing you the trips assigned to you, recording the distance you drove so it can be billed and so you can be paid, and keeping a record of expenses you are owed back. Nothing is collected for advertising, profiling, or any purpose unrelated to running the fleet.

6. Who can see it

Your trips, distances, expenses and receipts are visible to your fleet operator on their Odobase dashboard. That is the point of the app.

Beyond that, we do not sell your data, we do not share it with advertisers or data brokers, and we do not give it to other fleet operators. We disclose it outside Odobase only where the law requires it, or to the service providers who host the platform for us and are bound to use it for nothing else.

7. How it is protected

All traffic between the app and our servers is encrypted in transit over HTTPS. The release build of the app trusts only the operating system’s own certificate authorities, and your sign-in token is held in the app’s private storage, which other apps on the device cannot read.

8. How long it is kept

Trip records, expenses and receipts belong to the fleet operator and are kept for as long as they keep their Odobase account, since these are the records they bill and account from. Your phone number is kept for as long as you are an active driver on their fleet.

When a fleet operator closes their Odobase account, the data belonging to it is removed from our active systems.

9. Getting a copy of your data, or having it deleted

You can ask for a copy of the personal data we hold about you, ask us to correct it, or ask for it to be deleted. Two ways to do that:

  1. Ask your fleet operator. They control your driver record and can remove it directly from their Odobase dashboard.
  2. Email us at info@odobase.com with the phone number you sign in with and what you would like done. We will confirm your request and act on it within 30 days.

A deletion request removes your driver profile, your phone number and your recorded trip locations. Where the fleet operator must keep a trip or an expense as a business or tax record, that record is retained but stripped of the details that identify you personally.

Deleting the app from your phone does not by itself delete data already held on the server — use one of the two routes above.

10. Children

Odobase Driver is a tool for employed professional drivers. It is not directed at children, and we do not knowingly collect data from anyone under 18.

11. Changes to this policy

If we change what the app collects or how it is used, we will update this page and move the “last updated” date at the top. Material changes will also be reflected in the app’s Data safety information on Google Play and its App Privacy details on the App Store.

12. Contact

Questions about this policy, or about the data we hold, can go to info@odobase.com.

This document is published in English. If it is made available in another language, the English version governs.