/privacy

Privacy policy

Last reviewed 29 August 2026 · owner: engineering · applies to milestracking.com and the Miles Tracking service

The short version: we track vehicles, not people, and this website watches nobody. The rest of this page is the detail behind that sentence.

1. This website

• No cookies. No advertising pixels. No fingerprinting. No third-party analytics of any kind — nothing on this site talks to Google Analytics, a tag manager, or anyone else.
• We do count our own pages, on our own database, so we can tell which ones are useful. What that means exactly: a random number is generated for your browser tab, kept only until you close it, and used to group the pages seen in one sitting. We record which of our own pages you opened, whether you clicked through to the pilot form, and whether you started and sent it. We also record the website you arrived from — "google.com", not which page of it and not what you searched.
• What we deliberately do not have, and could not produce if asked: any way to recognise you on a later visit, any cookie, any stored identifier, your IP address in that data, your browser or device details, any full web address, or anything you typed into a form. Because nothing survives the tab, we cannot count people at all — only sittings — and our own reports say so.
• If your browser sends Do Not Track or Global Privacy Control, we count nothing. You can also switch it off here, on this page, right now:

• Cloudflare serves the site and, like any host, sees your IP address in operational logs, kept for about 30 days. We do not tie those logs to you.
• The demo map on the home page draws its base map from OpenFreeMap. Loading those tiles shows OpenFreeMap your IP address and the map area on your screen, nothing else.
• The pilot form asks for an agency name, fleet size, state, email, and an optional phone number. We use them to reply and to size your shipment, and for nothing else: no newsletter, no list, no third party. While the form is switched off, it collects nothing at all.
• A pilot request is stored with one line about how you arrived — for example "search · google.com · landed on the NTD page" — so we know which of our own pages does any good. That line is the same information described above, copied onto your enquiry; there is no link back from it to the page counts, and it is deleted when your enquiry is. If you have Do Not Track on, or the switch above turned off, the line is simply not there.
• Retention: the page counts are deleted after 400 days. A pilot request is kept while we are talking to you, and deleted outright the moment you ask — name, email, phone and everything you answered, with no archived copy.

2. Riders and passengers who open a map

• No accounts, no sign-in, and no rider location. Opening a vehicle map never asks where you are.
• The map and the embed set no cookies, use no local storage, and carry no analytics identifiers. We count aggregate requests to size capacity: counts, not people.
• Your IP address reaches Cloudflare, which serves the map, and OpenFreeMap, which serves the base map tiles, as ordinary web traffic.

3. Vehicle data, for the fleets we track

A tracker sends us a vehicle ID, latitude, longitude, heading, speed, a timestamp, and the device's own health. That is a position of a vehicle, and a position never carries a person: no operator identifier is stored on it, in the map, in the API or in the feeds. Where a customer uses driver sign-in in our phone app, that sign-in is a separate record kept beside the tracking, never inside it — it names the vehicle only while the shift is open and is deleted the moment the shift ends, so no position history can be attributed to a person afterwards. We collect no driver behaviour events of any kind, and no in-vehicle audio, video, or cabin sensors.

The fleet's data belongs to the customer whose fleet it is. We process it to run the service and for nothing else: we do not sell it, share it with data brokers, or use it for advertising. The only people who can see a fleet's history are the customer's own staff accounts.

Some fleets use a phone as the tracker, running our Miles Tracker app. While tracking is on, the app reads the phone's location in the background and sends the same record listed above: position, battery, and the fleet device ID it was set up with. That ID names a fleet asset, not a person. Tracking starts and stops with the shift, the app shows the person whether it is on, and while it is off the app collects nothing. A personal phone goes home untracked. The app carries no advertising identifiers, infers nothing about motion or fitness, and its location data is never sold or shared.

If you drive a tracked vehicle: whether and when it is tracked is your operator's decision, not ours. What we can say about our part is that the position belongs to the vehicle, we offer no driver scoring, and some states require written notice of monitoring, and we tell every customer which ones.

4. How long we keep it

• Live positions: minutes, in memory, for the current service day.
• Position history: 90 days by default. Each customer elects its own period, 30 days to 3 years, to match its own records schedule.
• Driver sign-in records: only while the shift is open. Ending the shift deletes the record.
• Staff account records: the life of the account. Billing records: as long as tax and audit rules require, then deleted.
• On cancellation: the customer's data is exported to them and hard-deleted within 30 days of confirmed receipt. Backups expire at most 30 days after that, and then it is fully gone.

5. Who else touches data

We keep one complete list of the companies that process data for us, and exactly what reaches each one. It is published, in full, on the security page — one maintained list, so no two answers can drift apart. Customers are notified of changes 30 days before they take effect.

6. Your rights and requests

• Export, correction, and deletion of fleet or account data go through the customer that holds the account: the data is theirs, so we act on their instruction.
• A public agency's vehicle data may be subject to public-records law. The agency answers those requests; we assist, including honouring legal holds that suspend a scheduled deletion.
• Questions about this page go to contact@milestracking.com and are answered by the person who wrote the system. When something you ask isn't answered here, we add it here rather than answer it privately.

7. Changes

Changes appear on this page with a new "last reviewed" date at the top. Anything that changes what we collect or how long we keep it is also told to customers directly, before it takes effect.