Still Flockin': When Does FLOCK Misuse Become More Than a Policy Violation.

Our Take

Copville's latest 'Lock'd Up' installment zeroes in on a question we've been hammering on for a while: at what point does an officer punching a plate into Flock's network for personal reasons — an ex, a neighbor, a rival — stop being a 'training issue' and start being an actual violation of law? It's a good sign when independent creators start pulling that thread, because police departments and Flock Safety itself have spent years treating every documented abuse case as an isolated, correctable mistake rather than evidence of a system that was never built with enforceable guardrails.

That framing matters because 'policy violation' is doing a lot of quiet work. Policies are internal, revisable, and almost never prosecuted. When access logs show someone searched a plate with zero case number attached, that's not a paperwork slip — it's unauthorized surveillance of a private citizen using a government-funded camera network, and it should carry consequences that look like it. The fact that these incidents keep surfacing city after city, department after department, isn't a string of bad apples; it's what happens when you hand thousands of officers nationwide a searchable database of everyone's movements and tell them to self-police.

Credit to Copville for keeping this conversation public instead of letting it die in an internal affairs file. If you want to see whether these cameras have already shown up on your street, check our map, and if your city is debating a Flock contract, our take-action page has what you need to push back before the cameras go up, not after the misuse reports start.