A City Just Ripped Out Its Flock Cameras - The Audit Is Why | Jim asks Claude | Rewired #Shorts

Our Take

Credit to Jim at Rewired with Jim for digging into this one, because it's exactly the kind of story we keep warning about. Mountain View, California didn't pull its Flock Safety cameras over price tags or policy debates — they pulled them because an audit turned up a "Statewide Lookup" setting that had been live for roughly a year and a half, unbeknownst to the city's own staff. Nobody could explain how it got switched on. There were no logs. That's not a minor glitch, that's a surveillance system operating outside the control of the people who supposedly run it.

The part that should worry every city council considering Flock is the second half of the story: when Mountain View asked whether federal agencies had queried their camera data, Flock reportedly couldn't answer — because the auditing function to even check that question doesn't exist. Flock's public line is that agencies aren't auto-enrolled into data-sharing networks. Fine, but if there's no logging infrastructure to verify who accessed what and when, that promise is just a press release, not a safeguard. A system with no audit trail is a system nobody can be held accountable for, and that's the whole ballgame when you're talking about license plate data that maps where every driver in town goes.

This is why we keep saying "trust us" isn't a privacy policy. If your city has Flock cameras — or is being pitched on them — demand the audit logs up front, not after a year and a half of silent statewide access. Check our camera map to see what's already watching your streets, and head to take-action for tools to push your local government toward real transparency instead of default trust.