Palm Bay Unhoods Flock Surveillance Network: Inside the Dragnet, Leaked Code & Dais Records

Our Take

Credit to Thomas Gaume for doing the unglamorous work: pulling council minutes, sworn testimony, and a two-week 'administrative review' apart to show what actually happened in Palm Bay. The pattern is familiar — a network pauses just long enough to generate a good headline, then resumes with the same vendor, the same retention windows, and the same lack of independent audit. One solved car theft and one fast arrest get cited as proof of concept, but nobody in these hearings is weighing that against the retrospective tracking of every plate, every day, for everyone who was never a suspect.

The part that should worry every Palm Bay resident isn't the casework, it's the plumbing underneath it. WIRED's leak of 450+ Flock OS Investigate source files, confirmation of commercial data-broker integration, and the existence of 'zero-crime' search templates are not abstract IT details — they're the mechanism by which a tool sold as 'find the stolen car' becomes a tool for open-ended location history requests with no criminal predicate. When a private company's internal search categories leak and one of them isn't tied to any crime at all, that's not a bug in the system, that's the system.

This is exactly why local dais records matter as much as the tech specs — a council member's on-record vote or a citizen's sworn testimony is often the only public accountability layer standing between 'pilot program' and permanent dragnet. If you want to see whether your own street is already wired into a network like Palm Bay's, check our camera map, and if you want to push back before your city council does its own quiet 'resume operations' vote, our take-action page has the steps.