One officer ran the same plate through Flock 382 times
The short version: Two officers, two coasts, one week: Flock data got weaponized for stalking and leaked to a domestic-violence suspect, proving the network has no idea who's asking or why.
Our Take
Flock U (credit where due) just laid out the plainest case yet for why 'the data is only used for serious crimes' is a marketing line, not a safeguard. A Fort Pierce, Florida officer allegedly ran one plate 382 times, cross-referencing it against FCIC/NCIC, DAVID, and TLO — that's not a traffic stop, that's a surveillance campaign built on taxpayer-funded infrastructure. Four felony counts later, the damage to whoever that plate belonged to is already done.
Three days later and a continent away, a San Jose officer allegedly pulled Flock data on a personal phone and handed it to a suspect in a domestic-violence case, reportedly helping that person locate the victim. This is the nightmare scenario advocates have been warning about since these cameras started going up: once the data exists, it leaks, gets abused, or gets weaponized against the exact people the system claims to protect. The network itself has no idea if the query is a stalker, an abuser, or a cop clearing a warrant. It just answers.
Two incidents in one week isn't a coincidence, it's a pattern baked into the design — thousands of readers, minimal audit friction, and trust-based access controls that only get checked after someone's already been harmed. If there's a camera reading plates in your town, you deserve to know it's there. Check our map and see what you can do about it on our take-action page.
This is DeFlock The USA’s original commentary. The video above is the work of Flock U, published on YouTube — full credit to the creator.