Public sector
Law enforcement
Plate data is location data over time, and that is exactly why it is useful and why it is regulated. We build the controls first and the search second.
The context
The controls are the product, not a compliance layer bolted on top
Several states now require a written usage and privacy policy, an access log, periodic audits and a defined retention window. Some restrict sharing outside the state entirely. A platform that treats those as configuration is one that can be deployed; one that treats them as customization is one that cannot.
- Retention windows differ for hits and non-hits, and by state.
- Permitted purposes are defined by the agency and recorded per query.
- Sharing follows the published policy, and the policy is public.
Named roles
Who may query, export and administer, defined by job title.
Audit exports
Access logs in the form a periodic audit requires.
Retention control
Scheduled destruction, with the destruction itself recorded.
Training record
Who was trained, on what, and when.
Before deployment
Three documents, then the system
Usage and privacy policy
Drafted with your counsel and published on your site.
Data agreement
Roles, purposes and responsibilities stated in writing.
Audit plan
Who reviews the logs, how often, and what they report.
Review the controls with your counsel
We will walk through the policy template and the audit exports before anything is installed.