License Plate Reader Warrant: EFF's Line on Flock

License plate reader warrant: what EFF is asking for

EFF, the Electronic Frontier Foundation, wrote about Flock Safety in August 2026. EFF's stated target is the search of stored license plate reader data for a specific vehicle. The table sets out the ask and the one related claim EFF reports about Flock's CEO.

A judge-signed warrant for historic ALPR data

ALPR is short for automated license plate reader. The data in question is the record of plates those cameras have already read.

EFF says police, at a minimum, need a warrant signed by a judge to search that historic data about specific vehicles. EFF calls this common sense. It likens such a search to police going back in time to retroactively follow someone's comings and goings.

Flock's CEO and the active case number

EFF reports that Flock's CEO has come to agree with groups such as the American Civil Liberties Union and EFF that police should need an active case number to search Flock's data. A case number is not a warrant. EFF's account of the CEO's position does not mention a judge.

What Flock changed: retention, filtering and audits

EFF describes Flock Safety as the embattled vendor of mass surveillance technology. It says Flock rolled out a handful of reforms after nationwide anger that has seen scores of towns cancel or suspend their ALPR contracts with the company.

EFF names three of the reforms: retention, offense filtering and audit lockouts. None of the three is a warrant requirement.

Flock data retention drops from 30 days to 7

Retention is the period for which Flock's system keeps plate reads. EFF calls the change to retention the most consequential of the reforms.

Flock's default setting is an optional 7-day retention period for ALPR data, down from an original default of an optional 30-day period. To keep data past the retention setting, police must use Evidence Mode. In EFF's description, that means the data is tied to an active investigation rather than a fishing expedition.

Offense filtering and audit lockouts for officers

Offense filtering lets a city give other departments access to its ALPR data only when they are investigating certain crimes. EFF's example is murder or robbery, but not immigration-related investigations.

The other reform, EFF says, is supposedly a stronger audit feature that proactively locks out officers who file suspicious requests for data. EFF's objection is that these audit and transparency tools address a problem Flock created: an abusable mass surveillance system that tracks all cars all the time.

Why EFF says a vendor cannot settle the question

EFF's fundamental objection is about who sets the rules, not about any one setting. EFF's post is titled "Too Little, Too Late: Flock Admits Their Technology Needs Reforms." The two points that follow are EFF's reasoning.

EFF asks what stops Flock from reversing course

EFF poses the question directly: what stops Flock from reversing these reforms if its law enforcement customers defect to another ALPR vendor? Its answer is one word: nothing.

EFF adds a principle. In its view, the decision on how long police can collect and retain data on millions, if not hundreds of millions, of innocent people should not rest with Flock or any other ALPR vendor.

EFF's call for laws that restrict police use

EFF's remedy is legislative: lawmakers need to pass laws that restrict police use of surveillance technology. In EFF's words, the surveillance business model is the problem, and the company-imposed reforms are slapdash.

Two other laws have their own write-ups: Colorado AI Act: Repealed Before It Took Effect and EU AI Act 2026: What Applies in August, What Waits. The quotes above come from EFF's post.