Flock camera policy changes after suspected misuse
The short version: Texas City disciplined two employees after an audit caught them misusing Flock license plate reader data, proving these systems get abused even with 'safeguards' in place.
Our Take
Credit to KPRC 2's Click2Houston for actually digging into what happens when a Flock Safety audit finds a problem instead of just taking a police department's word that everything's fine. Texas City didn't catch this misuse because the system is self-correcting — someone had to go looking, and two employees ended up disciplined. That's the quiet part of the ALPR sales pitch nobody likes to say out loud: the audit trail only matters if somebody actually reads it.
This is the pattern we keep seeing around the country. Departments roll out Flock cameras promising narrow use cases — stolen cars, Amber Alerts — and then the access logs reveal employees running plates for personal reasons that have nothing to do with public safety. A 'policy change' after the fact is not a deterrent, it's damage control. The real question is how many searches like this never get audited at all, in Texas City or anywhere else running a Flock network.
If you want to see how many of these cameras are watching your own commute, check our camera map, and if you think your city council should be asking harder questions about audit transparency before approving another Flock contract, our take-action page has tools to help you show up and ask them.
This is DeFlock The USA’s original commentary. The video above is the work of KPRC 2 Click2Houston, published on YouTube — full credit to the creator.