The moment Oshkosh, Wisconsin’s city council chamber on April 21, 2026. Council member Brad Spanbauer asks Flock Safety’s Chief Information Security Officer Chris Castaldo a direct question: can the system generate a heat map of a specific vehicle’s movements over time? Castaldo answers: “No, that is not available.” The council votes 5–2 to renew the contract. Less than 24 hours later, Police Chief Dean Smith has personally confirmed the feature exists — and the deal is already dead. This isn’t just a Wisconsin story. It’s an $8.4 billion surveillance app company, backed by Andreessen Horowitz and Tiger Global, getting caught misrepresenting its own product to the government writing the checks.
What Flock’s System Actually Does
The heat map isn’t a camera — it’s a behavioral profile built from your daily routine.
Flock’s own documentation states it plainly: “FlockOS allows you to see the historical locations of a specific vehicle, including a map-based view and heat map as part of license plate search.” Over configurable windows of 14 to 30 days, the system aggregates every automated license plate reader capture of a specific plate and brightens the map where that vehicle appears most frequently. Think less Ring doorbell, more Google Maps Timeline — except built for law enforcement and pointed at your car. Where you live, work, worship, seek medical care, or show up to protest: the heat map can surface all of it, based on secretly tracking repeated camera reads alone.
The 24-Hour Collapse
From a 5–2 approval to a 7–0 cancellation in a single day.
OPD officers flagged the discrepancy to Smith the morning after the vote. Smith verified the heat map feature himself. That evening, at a special meeting, he told the council: “Because of this misrepresentation, specifically to a question asked by a council member, I can no longer recommend Flock,” according to the Oshkosh Northwestern.
Every council member who had approved the contract the night before voted to kill it.
Flock’s Explanation – and Why It Doesn’t Land
“One small misunderstanding” is doing a lot of heavy lifting for a categorical denial.
Flock spokesperson Josh Thomas called it “one small misunderstanding,” arguing Castaldo thought Spanbauer was asking about tracking people rather than vehicles, and that the heat map merely visualizes “point-in-time images” within a limited retention window. The company called the outcome “disappointing” given “one small misconception stated during a two-hour meeting.” Smith’s position was unambiguous: whether intentional or a mistake, inaccuracy at a public procurement meeting destroys trust. Flock’s own documentation directly contradicts the categorical “No” Castaldo gave the council, and independent reporting corroborated by Footnote4a.org confirms the feature’s existence and scope.
The Bigger Picture
Oshkosh won’t be the last city asking these questions — and that’s exactly the point.
Oshkosh reportedly isn’t the first jurisdiction where Flock Problem representations about data capabilities have faced scrutiny, with civil-liberties reporting describing a broader pattern of similar disputes across multiple cities. The company carries $500 million in annual recurring revenue and a valuation north of $8 billion — the momentum is undeniable. The Oshkosh case has already surfaced as a model for procurement accountability advocates, who point to the following as the minimum standard for any surveillance contract:
- Live feature demonstrations
- Written vendor responses
- Pre-vote independent verification
A “No” that becomes a “Yes, actually” by the next morning isn’t a minor nuance. It’s the whole problem.
