Data from Kansas City Flock cameras was searched over a million times in 30 days. Who was looking?
The short version: KCUR found Kansas City's Flock cameras got searched over a million times in a month, raising hard questions about who's looking and why.
Our Take
A million searches in 30 days on one city's license plate reader network isn't a glitch, it's a business model. KCUR's reporting shows exactly what we keep hammering on: once a Flock system goes live, the data doesn't stay local. It gets pulled, queried, and shared across a web of agencies that most residents never voted to let in, and most city councils never fully grasp when they sign the contract.
The scary part isn't just the number, it's the opacity behind it. "Mostly by..." is where the sentence trails off, and that trailing off is the whole problem. When a camera system logs a million queries and the public has to FOIA its way toward even a partial answer, that's not accountability, that's a surveillance network running on autopilot with a thin layer of audit logs nobody's required to actually check.
Kansas City isn't unique, it's just the city that got caught looking at its own numbers. Credit to KCUR for doing the digging most local outlets won't bother with. If you want to see whether this is happening in your own backyard, check our camera map and start asking your city council the same questions KCUR just asked Kansas City's.
This is DeFlock The USA’s original commentary. The video above is the work of KCUR: Kansas City public radio, published on YouTube — full credit to the creator.