Being outside isn’t consent.
A public road should not mean a blank check for tracking. Understand license-plate readers by following the records, permissions and people responsible.
What is established.
A camera location is the beginning of the inquiry. To understand a license-plate reader system, examine what it records, how long those records remain, who can search or export them and how misuse is reviewed. This brief examines Flock’s published statements and the ACLU’s advocacy guidance. It does not audit a deployment or establish whether a particular search is lawful.
A plate read contains more than a plate.
Flock’s license-plate reader policy lists plate and vehicle images, vehicle characteristics, plate number and state, date, time and camera location. It describes customer-designated administrators and authorized users, alongside designated vendor personnel with support access.
The policy says queries are logged for auditing and that users should confirm the computer’s plate translation before acting on an alert. Our question: who reviews those logs, and what happens when a search has no legitimate purpose? A log’s existence does not establish effective oversight.
Source 1: Flock: License Plate Reader Policy ↗Seven days is a default—not your community’s answer.
Flock announced a change from a 30-day default to seven days, while saying existing customers would retain their current approved periods. It also announced Evidence Mode to preserve selected records for active investigations. The announcement describes planned rollout; it does not establish which features your agency has enabled.
Ask for the effective retention setting, the agreement governing it and rules for preserved evidence. Also ask what happens to downloaded copies. A headline about deletion does not answer every question about a record’s lifecycle.
Source 2: Flock: privacy, accountability and security updates ↗Customer ownership is not individual control.
Flock’s explanation says customers retain ownership of Customer Data. It also describes a license permitting Flock to provide, support and improve its services, and contract restrictions on sale and sharing. These are the provider’s account of its contractual terms—not our verification of practice.
Our interpretation: the customer operating the cameras and the person whose vehicle was recorded are different parties. Customer ownership does not, by itself, tell that person who searched their movements, where copies went or how to challenge a misuse. Read the executed agreement and applicable local rules.
Source 3: Flock: Data Ownership ↗Community oversight starts with specific questions.
The ACLU opposes networked ALPR surveillance and offers advocacy guidance focused on retention, sharing and permitted uses. It recommends engaging local representatives and public meetings, with model safeguards for communities that continue using the systems.
That is an advocacy position. It is not a court ruling about your city. Use its questions to examine local documents, then distinguish what the policy permits from what the available evidence shows.
Source 4: ACLU: community advocacy on license-plate readers ↗Where we stand.
Our position: being visible in public is not a blank check to build a searchable history of someone’s life. That is a principle we advocate, not a declaration that every public camera violates the law. Public safety claims deserve scrutiny alongside necessity, proportionality and accountability. Privacy professionals can make this debate concrete: ask for the rules, the settings, the exceptions and evidence that someone checks them. Privacy as fuck means doing the homework.
Ask the next question.
- Which executed contracts, amendments and use policies govern this system?
- What retention setting is active, and what exceptions apply to preserved or exported records?
- Which organizations can search the data, and who approves or revokes that access?
- Who reviews search logs, how often, and what public oversight reports are available?
- How are incorrect plate reads, complaints and suspected misuse investigated?
Start with the public record.
Look for procurement records, council agendas, agency policies and a transparency portal. If information is missing, ask the responsible agency for the relevant existing records through its published process. Access, exemptions, costs and deadlines depend on the jurisdiction.
Keep the inquiry focused on governance. Do not publish individual vehicle histories, credentials or personal identifying details. Our Explorer is a starting point for discovery; it is not a complete camera inventory or proof of a deployment’s current settings.
Please point me to the current license-plate reader agreement and use policy, retention rules, authorized sharing partners and any publicly available audit or oversight reports. If these records are not published, which process should I use to request them?
This starts a discussion. It does not establish consent or satisfy every local legal requirement.
Educational commentary. Sources and services can change. This brief does not establish legal compliance, product safety or misconduct. No affiliation or endorsement. Suggest a correction.