Trust
The rules are enforced on us, not just promised
Plate data is location data over time. A program that collects it has to say what it collects, why, who can see it and for how long, and it has to say it in public before it starts.
Commitments
Four that apply on every program
Purpose limitation
Data supports the program it belongs to. It is not repurposed and not sold.
Defined retention
A window set per program and per jurisdiction, stated in the contract.
Limited, logged access
Named roles, and a log entry on every lookup with its purpose.
No facial recognition
Not part of the scope we offer, and not included in the modules described here.
The legal picture
There is no single federal rule, and that is the design problem
State by state
Retention windows, permitted purposes and sharing restrictions for plate data differ by state. Some states set a short window measured in days; others set none at all. A platform that hard-codes one answer cannot be deployed honestly across a country like this.
So retention, purpose and access are configuration in NEXUS, set at the program level for each deployment.
Driver record data
Issuing a notice requires the registered owner, and that information comes from a state motor vehicle record. Federal law limits who may obtain it and for what purposes, and creates liability for misuse.
The platform records the permitted purpose at the moment of the query, along with who made it and when, so that the record exists if it is ever needed.
California
California requires an ALPR operator to publish a usage and privacy policy on its website. Ours is on this site.
Review this with your counsel
We would rather have the conversation before a contract than after a records request.