📹 Cities Are Dropping Flock — and Quietly Switching to Axon

The claim, and what the record actually shows

It is tempting to read the cancellation wave as a clean victory, and tempting in the other direction to read it as theater — councils staging regret while quietly keeping the cameras. The documented reality is a third thing, and it is more useful than either. The cancellations are real and hard-won: they follow audits, records requests, and reporting that surfaced genuine abuse. But in case after case the same capability reappears under a different logo, because the replacement vendor was already embedded. The honest framing is not “cities are pretending.” It is: dropping a brand is not the same as ending the surveillance, and the swap is happening faster than the oversight.

The scale of the exit is not in dispute. As of late July 2026, more than 50 municipalities had canceled or rejected Flock camera contracts, part of a wave that included 39 terminations in the first five months of 2026 alone. The anti-surveillance group DeFlock, which crowdsources camera locations, counts more than 122,000 license-plate-reader cameras mapped nationwide and roughly 95 cities that have rejected ALPR systems. Those are the wins. The question this piece is about is what fills the vacuum.

Why cities are leaving Flock — the abuses were real

The cancellations cluster around a small set of documented failures, and they matter because they are the legitimate grievance that makes the whole story credible. Recurring findings across the audits that triggered exits:

• Illegal federal and immigration data-sharing. Mountain View’s audit found the ATF, Air Force, and a GSA Inspector General in its Flock data; Oxnard found a “nationwide query” setting sharing data with federal agencies against California law.
• Exposure to thousands of outside agencies. Syracuse acted after reporting revealed its police department had exposed drivers’ data to thousands of outside law-enforcement agencies nationwide, including federal immigration authorities, through Flock’s national network.
• Targeting protected activity. The EFF documented that the risks had materialized around using ALPR data against immigrants and people seeking reproductive or trans healthcare, with Texas authorities implicated in using cameras to target abortion seekers.

These are not abstract privacy worries; they are the specific, on-the-record reasons councils voted to cancel. Keep them in view, because they are exactly the capabilities that a vendor swap can quietly carry forward. Max Intel maintains a running accountability file of documented ALPR and Flock misuse for the full catalog.

The pivot: Flock off, Axon on

Here is the pattern the headlines mostly miss. When a city removes Flock, the plate-reading capability frequently continues through Axon — the Taser and body-camera giant that is now the largest policing-technology company in the United States. Blaze Media, surveying the wave, put it bluntly: cities are switching to a public-safety tech company already inside these departments in smaller roles — Axon.

The tell is that phrase “already inside.” In the largest documented cases, the Axon relationship predated Flock’s exit and was never touched by the cancellation:

• Austin. When the city canceled Flock in 2025, EFF’s own victory writeup noted that Austin still makes use of ALPRs via its contract with Axon. The Flock win was genuine; it simply never reached the parallel Axon system.
• Los Angeles. LAPD let its Flock contract expire in July 2026 while its patrol cars already ran Axon body cameras and tasers, with Axon supplying basic plate-recognition for in-car cameras well before Flock’s exit.

Denver: the cleanest documented case

Denver is where the swap is easiest to see in the numbers, and it doubles as the honest counter-argument — because Denver’s replacement genuinely tightened some controls. The city removed all 110 Flock cameras when its contract expired March 31, 2026, and replaced them with 50 Axon cameras. On paper the deal looks like a rollback: half the cameras, 21-day retention instead of 30, no access to a vendor-run national database, and mandatory audit trails for every query.

That is a real improvement, and it deserves to be said plainly rather than flattened into a conspiracy. But two facts sit next to it. First, the camera count fell and the surveillance continued — a smaller dragnet is still a dragnet. Second, the city’s contract only ever covered police-operated cameras: privately owned Flock cameras installed by HOAs and businesses across Denver remain operational, untouched by the cancellation. The public network shrank; the private one Flock aggressively markets to neighborhoods kept running.

Why the swap can be worse, not neutral

Switching vendors is not a lateral move, and the direction it moves is toward more aggregation. Flock is, at its core, a plate-reader company. Axon sells an entire ecosystem — and its ALPR is a feeding tube into Fusus, its real-time crime center platform, which by design pulls officer location, alerts, dispatch data, ALPR overlays, and video feeds onto a single live map. Axon has been explicit that plate reads flow into that unified environment: its new fixed ALPR cameras deliver shared visibility across jurisdictions, and Axon Fleet in-car cameras alone read 8.1 billion plates in a single year. It is also integrating private cameras — through Fusus “Community Connect” and a Ring partnership — so the same platform that ingests police plate reads can pull in residential and business video.

Privacy technologists flagged exactly this. In Syracuse, a member of the city’s own Surveillance Technology Working Group argued that Axon’s reach may raise the stakes, because it facilitates so much of law-enforcement technology — body cameras, drones, and the Fusus crime center — and its reliance on AI makes accountability and oversight further removed. Independent coverage reached the same conclusion: switching vendors may actually increase privacy risk through deeper system-wide data aggregation.

The accountability gap after cancellation

The other recurring problem is that the oversight built around Flock does not automatically transfer to its replacement — and sometimes the replacement contract is harder to see. Nearly a year after Syracuse voted to drop Flock, a privacy strategist who sat on the panel that first reviewed the Flock technology said he requested the city’s new Axon contract and its ALPR policy more than six months ago and never received either. The city had signed a five-year, $422,636 contract with Axon in February 2026 after the Flock data-sharing scandal — but the oversight body created for Flock was, by its own member’s account, shut out of the successor.

That is the mechanism to watch. The public attention, the working group, the retention rules, the audit obligations — all of it accretes around the vendor that got caught. When the capability moves to the vendor that was already there, the scrutiny does not always move with it. The surveillance can end up less visible after the “win.”

What actually stops the swap: state law, not contract language

The lesson every serious analysis of this wave lands on is the same: contract terms are a temporary patch that a vendor cycle erases; only statute survives. As one review put it, contract tweaks are a temporary patch — state law is the only protection that survives a vendor swap. A retention limit Denver negotiated with Axon protects Denver residents until the next procurement; a state deletion mandate protects everyone regardless of who wins the bid.

A few states show what durable looks like. New Hampshire mandates a three-minute data-deletion rule, and Vermont’s approval process has functionally blocked ALPR deployment statewide — but most states have neither protection. The courts are converging on the same variables. Two January 2026 rulings — Schmidt v. City of Norfolk and State v. Simonson — upheld limited ALPR use but identified scale, retention period, and sharing scope as the decisive constitutional factors. Those are precisely the things a vendor swap can reset and that only law can lock across cycles.

How to tell a real win from a rebrand (a checklist)

If your city is “dropping Flock,” these are the questions that separate an actual reduction in surveillance from a logo change. Ask them at the council meeting and in a records request:

• Is there a successor vendor? Ask specifically whether Axon (or any ALPR-capable system) is already under contract for in-car cameras, body cameras, or a real-time crime center. The Austin and LAPD cases show the parallel contract is often already there.
• Does the new contract get the same oversight? Confirm the surveillance working group, retention rules, and audit obligations explicitly attach to the replacement — Syracuse shows they may not.
• What happens to the private-camera network? Police-contract cancellation usually leaves HOA and business Flock cameras — and Axon’s Community Connect / Ring integrations — running.
• Is anything locked in state law? A retention or sharing limit that lives only in a contract dies at the next procurement. Ask what survives a vendor swap.
• Where does the data flow? The Flock scandals were about sharing scope — federal and cross-jurisdiction access. Ask whether the replacement shares into a national or regional network, and under what warrant standard.

To see what is actually deployed around you before you ask, Max Intel maintains a state-by-state ALPR camera dataset and a walkthrough of mapping a local surveillance network with free tools.

Bottom line

The cancellation wave is real, and the people who forced it — auditors, journalists, council members, residents filing records requests — earned genuine wins against a company caught sharing driver data with federal agencies. The correction to the “quiet regret” framing is not that the cities are insincere; it’s that ending a contract with Flock and ending the surveillance are two different things. When the same capability continues under Axon’s Fusus — often a vendor that was already in the building — the dragnet persists with less public scrutiny and deeper aggregation. The durable fix isn’t a better contract clause; it’s state law that binds whatever logo comes next.

Primary reporting: Blaze Media (“Flock off, Axon on”); Gadget Review / Yahoo News (Denver contract terms, state-law analysis); CNY Central (Syracuse Axon contract & oversight gap); State of Surveillance (cancellation tracker, Mountain View & Oxnard audits, Denver private-camera note); EFF Deeplinks (Austin cancellation, Axon parallel contract); Newsweek / DeFlock (nationwide camera map); Axon.com and Axon press materials (Fusus capabilities, 8.1B plate reads). Contract figures and dates reflect each outlet’s reporting as of July 2026; this piece characterizes a documented pattern, not the motives of any individual official.