Last materially updated: August 21, 2026
Information you submit
The plate lookup accepts one state and one exact plate value in a POST request. PlateReaderMap does not place that value in a URL, save it to browser storage, publish a plate page, expose recent searches, or intentionally write request bodies to application logs. Results use a no-store cache policy.
The plate value is processed only to perform the current exact lookup against the available released public audit-record index. Refreshing or leaving the page clears the result from the interface.
Routine infrastructure data
Hosting and network providers may process ordinary request metadata needed to deliver and protect the site, such as IP address, user agent, route, timing, and security signals. PlateReaderMap does not intentionally add a submitted plate to that metadata or to analytics events.
The lookup uses Cloudflare Turnstile to deter automated bulk searching. The browser receives a short-lived, single-use verification token, and the server validates that token with Cloudflare before reading the private index. The plate value is not sent to Turnstile.
Analytics and advertising
No session replay, heatmap, advertising, or cross-site tracking scripts are included in the initial release. If lightweight analytics are added later, plate input and plate results will remain excluded.
Public source records
Camera data and any future audit-search index come from public, lawfully obtained sources. The public website does not offer a browsable plate directory or a bulk download of PlateReaderMap’s assembled records. Source files are reduced to fields needed for the product and provenance rather than retained merely because they were included in a release.
Questions
A public contact channel will be posted here before production launch. No contact form is used, so the site does not collect message data.