TrackMile
← Back to the app page
Privacy policy

What TrackMile collects, and where it goes

Last updated: 22 August 2026

TrackMile is built to keep your data on your phone. This page explains exactly what's collected, why, and the small number of cases where something does leave your device — because "we don't collect your data" is only trustworthy if it's specific about the exceptions too.

The short version
No account, no sign-up, no user ID of any kind
No analytics, no ad SDKs, no tracking of any kind
Journeys, receipts and vehicles stay in a local database
Route map thumbnails call Google's Maps service — see below
Backup, email and calendar sync only run when you trigger them
Uninstalling the app deletes everything TrackMile stored

Who this policy covers

TrackMile is developed by Fieldworks, an independent app studio. This policy covers the TrackMile Android app only. If you have questions, contact trackmile@fieldworks.work.

What's stored on your device

Everything below is written to a local database on your phone and is never transmitted to Fieldworks or any server we operate — there isn't one. This includes:

  • Journey data — start/end times, GPS coordinates, distance, classification (business/private), category, purpose, and place names derived from reverse-geocoding.
  • Vehicle records — name, type, odometer readings.
  • Receipt photos and amounts — images are stored in the app's private storage on your device.
  • Favourite routes, work-hours rules, and every setting described in the app's Settings screen.

None of this requires an account, and TrackMile has no way to identify you beyond what's on your own device.

Location and motion data, specifically

TrackMile requests ACCESS_FINE_LOCATION, ACCESS_BACKGROUND_LOCATION, and Android's Activity Recognition permission to detect when you're driving and to measure distance accurately. This data is:

  • Used only to detect trips and calculate mileage
  • Stored only in the local journey database on your device
  • Never uploaded to Fieldworks, sold, or shared with data brokers or advertisers

You can decline background location entirely and use manual trip entry instead — see the Permissions walkthrough on the main app page for what each option does.

Where data does leave your device

TrackMile's core promise is local-only storage, and that holds for everything above. A few features are genuine exceptions, each of which only activates when you use that specific feature:

  • Route map thumbnails — if a Google Maps Static API key is configured, the start/end coordinates (and, with detailed route recording on, the recorded path) of a journey are sent to Google's Maps Static API to render the thumbnail image on that journey's detail screen. If no Maps key is configured, this is skipped entirely and a plain "View route on Google Maps" link is shown instead, which only sends coordinates to Google if you tap it.
  • "Get directions in Google Maps" — tapping this link opens Google Maps (app or website) with your journey's start and end coordinates, subject to Google's own privacy policy from that point on.
  • Calendar sync — if you enable it, journey details (place names, times, and whether a trip is business or private, depending on your filter setting) are written to a calendar already configured on your device. If that calendar account itself syncs to a cloud service — a Google or Outlook account, for example — this data will sync there too, governed by that provider's own policy, not TrackMile's.
  • Manual backup and automatic backup folder — when you tap "Export full backup" or set up a weekly automatic backup folder, a file containing your journeys, vehicles, and receipt photos is written to a location you choose (for example, a folder in your Google Drive). This only happens because you explicitly picked that destination — TrackMile has no default cloud location and cannot see or access this file once it's written.
  • Email export — tapping any "Email" export option opens your device's own email app with a report attached. From that point, the report is handled by your email provider, not TrackMile.
None of these run in the background or without your direct action — TrackMile does not silently sync, upload, or phone home. Each of the above only happens because you tapped something specific.

Third-party services

TrackMile does not use any analytics, crash-reporting, or advertising SDKs. The only third party involved in any capacity is Google, and only through the two Maps-related features described above, plus the underlying Android platform and Google Play services required to run any Android app (motion sensor access, notification delivery, and app distribution/updates).

Data retention and deletion

Data stays on your device for as long as the app is installed. You can:

  • Delete individual journeys, receipts, or vehicles at any time from within the app
  • Clear all app data via Android Settings → Apps → TrackMile → Storage → Clear data
  • Uninstall the app, which removes everything TrackMile stored, including its local database and any receipt photos — unless you've separately backed that data up somewhere yourself

Children's privacy

TrackMile is not directed at children and is not knowingly used to collect information from children.

Changes to this policy

If this policy changes in a way that affects what's collected or how it's used, the "Last updated" date at the top of this page will change accordingly. Material changes will also be reflected in the app's Play Store listing.

Contact

Questions about this policy or your data can be sent to trackmile@fieldworks.work.