Flock cameras and the privacy debate
The short version: A Minnesota journalist misidentified by Flock cameras shows how easily ALPR errors can turn ordinary people into suspects with little recourse.
Our Take
FOX 9 Minneapolis-St. Paul brings a case that should worry anyone who thinks license plate readers are just neutral traffic cameras: a Minnesota journalist got flagged and tracked because Flock's system got it wrong. ACLU Senior Policy Analyst Jay Stanley lays out the basics of how these networks operate and why the errors aren't just theoretical glitches — they're baked into a system built to scan, store, and cross-reference every plate that passes, with minimal human review before action gets taken.
This is the pattern we keep seeing nationwide. Departments install Flock cameras promising narrow use against stolen cars or violent crime, but the database quietly becomes a tool for tracking anyone, anytime, often without a warrant and without anyone checking the match before officers show up. When the target is a journalist instead of a suspect, it's a headline. When it's an ordinary driver, it's just another anonymous entry in a growing surveillance dragnet that nobody outside the department gets to audit.
Accuracy problems aren't a bug to be patched — they're the predictable cost of a system designed to watch everyone by default. Check our camera map to see what's tracking you locally, and hit take action for ways to push back before your city's next Flock contract gets renewed.
This is DeFlock The USA’s original commentary. The video above is the work of FOX 9 Minneapolis-St. Paul, published on YouTube — full credit to the creator.