Lawmakers Approve Surveillance Tech They Admit They Don't Understand

Our Take

This clip names a problem we see constantly in Flock Safety rollouts: the people writing the fiscal notes, drafting the bill language, and briefing the committee are not engineers, they're generalist staffers on a deadline. When nobody in the room understands hash-matching, retention windows, or how a "public safety" camera network quietly becomes a de facto tracking grid, the only expert in the building is the sales rep who flew in to demo the product. That's not a conspiracy, it's just how understaffed statehouses work — but it means the technical framing of a surveillance bill is written by the company that profits from it passing.

Once that framing is baked into the staff brief, it survives all the way to the floor vote. Lawmakers then defend a technology they've openly admitted they don't fully understand, because the alternative — pushing back on a vendor-supplied narrative with no counter-expertise in the room — takes political will most offices don't have. That's how ALPR networks expand district by district with almost no adversarial scrutiny of retention periods, data sharing agreements, or who else gets to query the system.

Credit to Verified Privacy VPN's Hide & Speak for tracing this from the research desk up to the vote instead of just yelling about the outcome. If you want to see what that legislative failure looks like on the ground, check our camera map for the cameras near you, and if you'd rather not wait for Sacramento or your state capitol to get technically literate, our take-action page has concrete steps for pushing back locally.