Haines City Police Revise Use of Flock Cameras
The short version: Haines City PD only tightened Flock camera rules after an officer allegedly used the network to stalk his estranged wife, proving internal 'safeguards' often arrive after the damage is done.
Our Take
This is the pattern we keep seeing nationwide: a department insists its ALPR system has robust audit controls, and then it turns out an officer quietly ran personal plate searches for months before anyone noticed. Tampa Bay 28's reporting on Haines City PD is a useful case study because it shows the gap between what Flock Safety markets to city councils and what actually happens once a badge and a login are all it takes to pull someone's movement history. "Policy revisions" after the fact don't undo the surveillance that already happened to that woman.
Flock's own sales pitch leans on the idea that every search is logged and reviewable, but logs only matter if someone is actually auditing them in real time, not after a victim files a complaint. An officer with access to thousands of cameras can track an ex-partner's daily routine, home, workplace, and routine stops just as easily as he can look up a stolen car — and in this case, allegedly did. That's not a hypothetical privacy harm civil liberties groups warn about; it's exactly what happened here.
Departments love to frame these incidents as isolated misuse rather than evidence of a system with far too few guardrails baked in from the start. If you want to know whether your own city has quietly wired itself into this network, check our camera map, and if you'd rather your local council ask harder questions before approving more cameras, our take-action page has the tools to push back.
This is DeFlock The USA’s original commentary. The video above is the work of Tampa Bay 28, published on YouTube — full credit to the creator.