Why These Police Officers RESIGNED! 🚨 #FLOCKCameras #Shorts

Our Take

Credit to ClassE and Erik Harmon for flagging this one. Whenever officers walk away from a job rather than face scrutiny over how they used a license plate reader system, it's worth paying attention. Flock and its law enforcement partners love to point to "audit logs" and "reason for search" fields as proof the system polices itself. Cases like this are a reminder that a log only matters if someone actually reviews it, and usually that review only happens after a complaint, a nosy reporter, or a jilted ex forces the issue.

This is the quiet failure mode of mass ALPR surveillance: it's not just the hypothetical federal dragnet people worry about, it's the everyday temptation for an officer, dispatcher, or admin with access to run a plate for personal reasons — an ex-partner, a neighbor, a rival. Flock's marketing sells blanket camera coverage as a crime-fighting tool, but every network node is also a liability sitting on a server, waiting for someone with a login to misuse it. Resignations are a consequence after the fact; they don't undo the searches that already happened or tell the public who else got looked up.

If your town is debating a Flock contract, this is exactly the kind of incident to bring to the city council meeting — not as a hypothetical, but as documented behavior from inside a department. Check our camera map to see what's already watching your streets, and head to take-action for tools to push back before your local department has its own version of this story.