Privacy Concerns Flock Cameras and Police Surveillance
The short version: A new video revisits the 50+ officer misuse cases that pushed Flock to add audits and shorter retention — reforms that don't fix the core surveillance problem.
Our Take
TheEricTConversation lays out something we've been saying for a while: Flock Safety's own numbers on officer misuse — personal tracking, stalking allegations, dozens of documented cases — aren't hypothetical privacy fears. They're a track record. The company's response, tightening audits, requiring case codes, shortening default retention, reads less like a fix and more like damage control aimed at keeping cities from canceling contracts.
Here's the problem with "trust us, we added an audit log": audits catch misuse after the fact, if anyone bothers to look. They don't stop a network of thousands of always-on cameras from building a permanent movement record of every driver, whether or not that driver is ever suspected of a crime. Case codes are a paperwork requirement, not a technical barrier. A cop determined to look up an ex or a rival can still type in a code and get access. The infrastructure for abuse doesn't disappear because the company promises better bookkeeping.
This is exactly why we track where these systems are deployed — check our map to see if Flock or other ALPR networks are running in your area. If you'd rather your city not be the next misuse headline, our take-action page has concrete steps for pushing back at the local level. Credit to TheEricTConversation for putting the officer misuse numbers front and center — that's the part of this story that keeps getting buried under "safety" talking points.
This is DeFlock The USA’s original commentary. The video above is the work of TheEricTConversation, published on YouTube — full credit to the creator.