GreenDriver Mileage Tracker

Privacy Policy

The short version

GreenDriver is built to keep your data on your own phone. There is no user account, no company server and no cloud database. Almost everything this policy has to say follows from that one design choice.

What the app records, and where it stays

Location

While a trip is running, the app uses your phone's GPS to record mileage. This is stored only in a local database on your device. It is never transmitted to us or to any server we operate — because we do not operate one.

Background location is required because tracking must continue with the screen off and while you are away from the vehicle delivering on foot. Without it, every trip would stop recording the moment your screen turned off.

Trip and financial records

Pay, expenses, receipt photos, vehicle information and mileage logs you enter are stored locally on your device in the same local database.

Addresses

To fill in a trip's start and destination automatically, the app asks Android's own operating-system service to convert GPS coordinates into a street address. On most phones that system service may contact Google's geocoding servers, using only the coordinates. That request is made by Android, not by this app. You can also type an address by hand instead.

Maps

Viewing a trip on a map requires map images from a map provider, and the request reveals the area of the map you are looking at — as it does for any online map. By default those images come from OpenStreetMap; if you switch to a Google map or satellite layer in Settings, they come from Google's Maps service instead. No map is loaded unless you open one.

"Snap route to roads" — off by default

GPS wanders slightly, so a recorded line does not sit exactly on the road. If you turn this setting on, opening a trip's map sends up to about 100 of that trip's own GPS coordinates to router.project-osrm.org, a public routing service run by the OSRM project, which returns the line aligned to the road network.

This is the only feature in the app that sends your trip data to anyone else. It is cosmetic, it never changes the mileage that was recorded, and it is off unless you switch it on. With it off, your coordinates are never assembled into a request at all.

Receipt and document scanning

Gas receipts and schedule screenshots are read using on-device text recognition (Google's ML Kit, running entirely on your phone). No image or extracted text is uploaded as part of this feature. The camera used for scanning belongs to Google Play Services, which runs that screen itself — GreenDriver does not hold camera permission at all.

Backup, if you turn it on

If you enable backup and choose a folder, including a cloud folder, the app writes a backup file to that location using Android's standard file picker. That upload, if any, goes wherever you chose. We have no backup server, and this only happens if you set it up.

Crash reports, if you turn them on

The app includes an optional, off by default crash-reporting switch. If enabled, basic technical information about crashes and errors — not your trip data, not your location — is sent to Firebase Crashlytics, a Google service, to help find and fix bugs. You can turn it off in the same place you turned it on. The switch is hidden entirely in builds where crash reporting is not configured.

Feedback you send

The in-app feedback button opens your own email app with a message addressed to the developer, pre-filled with your app version and device model. Nothing is sent until you review and choose to send that email yourself.

What we do not do

• No user accounts, so no names, passwords or sign-in information.
• We never receive your data ourselves. We do not sell it, and we do not share it with anyone for advertising, marketing or profiling. The only time any of your trip data reaches a third party is the optional road-snapping setting described above, and the map-image requests needed to draw a map you have opened.
• No tracking across other apps or websites.
• No ads and no advertising ID.

Permissions the app requests, and why

• Location (precise, approximate and background) — to log mileage while a trip is running, including when the app is not in the foreground and while you are away from the vehicle on foot.
• Bluetooth (connect) — to talk to your car's Bluetooth and to an OBD-II adapter if you use one. The app reads only devices you have already paired yourself; it never scans for nearby devices and does not request a scanning permission.
• Notifications — the ongoing-trip notification that background tracking requires, and the scheduled block alarm.
• Alarms and full-screen alerts — so a scheduled block alarm can wake the screen at the right minute, like a clock app.
• Ignore battery optimisation (optional prompt) — the app can offer you the system screen that exempts it from battery restrictions, because those restrictions silently stop mileage recording. The app only ever opens the prompt; your answer is yours.
• Internet and network state — to fetch map images when you open a map, and to tell you the map is offline rather than showing an empty square.

The app does not request camera permission, Bluetooth scanning, activity recognition, or any sensor permission. Drive detection uses the accelerometer, which requires none.

Data deletion

All data lives on your device, so uninstalling the app deletes it. There is no account to close and no server-side copy to request deletion of — except any crash reports already sent to Firebase if you had crash reporting switched on, which Google's own Firebase privacy documentation explains how to request deletion of.

Children

GreenDriver is a tool for working drivers. It is not directed at children and we do not knowingly collect information from anyone under 13.

Changes to this policy

If any data practice described here changes, this page is updated before that version of the app ships, and the date at the top changes with it.

Contact

Questions about this policy can be sent through the developer contact link on the app's Google Play listing.