When Someone Asks for Their Own Data
Location records are among the most requested categories, usually during a dispute. What you will need to produce, and the rehearsal worth doing first.
General orientation, not legal advice.
People can generally ask for a copy of the personal data held about them, and location records are a common subject of such requests — frequently arriving alongside a grievance.
What has to be produced
Their location records, for the retention period.
Derived data: geofence events, distances, scores, dwell figures.
Who accessed it, where you hold that — and if you do not, the absence is itself informative.
The purposes, retention and recipients, which the notice should already state.
Not: other people's data, which in a shared vehicle needs care.
The rehearsal
Do it once, on a volunteer, before it arrives during a dispute.
Produce everything held about one driver for a month.
Time it.
Read it as they would.
Two things usually turn up: data in places nobody remembered — an export on a shared drive, a vendor's copy, a spreadsheet a manager keeps — and a record more detailed than anyone realised.
Where it gets awkward
Shared vehicles. A record for a van covers several drivers, and providing it whole discloses others' movements. Filter by shift, and say what you filtered.
Long retention. A request for six months of continuous position is a large disclosure and a visible demonstration of how much is held. It is also the moment employers discover their retention was not what they thought.
Covert or unnotified collection, which the request will expose and which cannot be explained away at that point.
Free-text notes attached to records. Anything written about the person is disclosable, and "again" or "suspicious" reads exactly as it sounds.
Reducing the difficulty in advance
Collect less, which shrinks every request permanently.
Give routine self-access, which removes most requests: people ask formally because they cannot see it otherwise.
Keep exports under control, because scattered copies are what make a request take a week.
Write records as if they will be read, because eventually one will.
Responding
Within the statutory period for your jurisdiction.
In a readable form — a map export and a table, not a raw data dump.
With an explanation of what the fields mean, including the accuracy caveat.
And with the same care you would want, because how a request is handled is frequently what determines whether a dispute escalates.
After
Note what the request revealed about where data lives.
Fix it: delete the strays, tighten the exports, shorten the retention.
A request is expensive once and cheap thereafter if the first one is used to clean up.
Give routine self-access instead
The change that removes most requests permanently.
People ask formally because they cannot see it otherwise.
Self-service access satisfies the same need in seconds rather than in a statutory response period.
And it improves the data, because people correct their own records and nobody else has the knowledge to.
The cost is a screen. The saving is every formal request you would otherwise process.
Connect policy to configuration
The practical choices behind this note can be compared with inspect this service connection. Keep the written purpose in control of the setup, enable only the data needed and review the result with affected workers.