[ PRIVACY AT EMPIRIC EARTH ]
A company whose input is video from public roads has to answer this before it says anything else about itself. So this is not a policy page filed behind a footer link. It is one of the five things in our navigation, and it is longer than our product pages on purpose.
[ WHY THIS PAGE IS THIS BIG ]
The industry has earned
the suspicion.
Cameras on public roads have been used to follow people who were not suspected of anything. Location data collected for one purpose has been resold for another. Systems sold as safety tools have been repurposed as surveillance tools, sometimes by their operators and sometimes by whoever asked nicely. None of that is hypothetical, and none of it is a reason to pretend the risk does not exist. It is the reason to say precisely what we do, what we refuse, and how you can check.
Φ
The stated purpose drifts
A capability built for one use gets pointed at another. The defence is not a promise. It is not building the capability.
Δ
Retention outlives the reason
Data kept indefinitely will eventually be used for something nobody consented to. Deletion schedules are a safety feature.
Σ
The driver is never asked
In most in-vehicle systems the person most exposed has the least say. We think that is the wrong way round, and we have written it differently.
[ THE LONG ANSWERS ]
Read further
Φ
The ten commitments
Ten binding commitments on road data privacy, what each one costs us, and the three questions applied before any new capability ships.
Δ
How de-identification works
Where in the pipeline it happens, what it removes, what it measurably misses, and what we do about the gap.
Σ
Law enforcement requests
The standard we hold, what we refuse, when we notify, and how we narrow an over-broad order.
Ψ
If you drive one of these vehicles
What is recorded, who can see it, what your employer can and cannot do with it, and how to raise a dispute.
Λ
Capability disclosure
A dated, versioned specification of what the platform is incapable of doing — written to be tested by somebody who does not work here.
Ω
Who decides, and how
Retention schedule, subprocessor list, security posture, review cadence and the named accountable owner.