📹 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, counted more than 122,000 license-plate-reader cameras mapped nationwide and 95 cities that had rejected ALPR systems (Newsweek, 28 July 2026). By 4 October its map showed 143,356 US plate readers and its “Recent Victories” table listed 153 cities. Jalopnik (4 Oct 2026) By 15 October the Institute for Justice counted 277 local governments that had ended or not renewed ALPR contracts since 2025. IJ (as of 15 Oct 2026) 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:

• Federal access that California law bars. Mountain View said an internal audit found that federal users had searched data from one of its cameras in 2024. They included ATF offices, two Air Force bases, the GSA Office of Inspector General and a national recreation area. It said Flock had turned on a “nationwide” search setting without the department’s permission or knowledge. City of Mountain View (30 Jan 2026) Oxnard found that a vendor-enabled “nationwide query” let agencies outside California search its data, including a federal VA police department. California law bars sharing plate data outside the state, federal agencies included. Oxnard PD (27 Feb 2026)
• 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 warned of “the potential of using the data against immigrants and people seeking trans or reproductive healthcare.” It noted a 404 Media report implicating Texas authorities in using the cameras to target abortion seekers. EFF (6 Jun 2025)

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 maker. 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. Denver’s Flock contract expired on 31 March 2026 with its “100-plus public cameras” already gone. The same day the council approved a one-year, $150,000 Axon contract for 50 cameras by 7–6. Denverite (31 Mar 2026) On paper the deal looks like a rollback: half the cameras, data kept 21 days instead of 30, no national database that other agencies can search, and audited access. Denverite (18 Mar 2026)

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: “Private Flock cameras remain in operation throughout Denver.” Denverite (31 Mar 2026) 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 April 2025 release promised “shared visibility across jurisdictions” and said Axon Fleet 3 in-car cameras “have read a total of 8.1 billion license plates” (vendor claims). Axon (22 Apr 2025) 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. Jalopnik reached the same conclusion: an Axon network “can actually put your privacy at a higher risk than one from Flock.” Jalopnik (14 Jul 2026)

The ACLU calls this the "operating system" problem. Its June 2026 report, Surveillance, Profits, and the Police, names Axon, Flock and Motorola. It warns that some vendors want to run "operating systems" for police that, "like operating systems on computers and phones, can see and control all the data in the system". Police cloud services pool data from thousands of departments on company servers and let vendors control deployed devices remotely. The ACLU says insiders could misuse that data against critics, journalists or competitors. It recommends contract limits on vendor access to police data, local rather than cloud hosting, and community-control (CCOPS) ordinances ACLU (24 Jun 2026).

Which other plate-reader vendors might a city switch to?

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 Common Council had voted in February 2026 to sign a five-year, $422,636.28 contract with Axon 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

Every state ALPR law passed in 2025–26, and the federal bills introduced since July, are tabulated in License-Plate Readers and the 2026 Midterms.

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, a limit that binds every vendor. Courts have so far upheld plate readers, but one ruling left the door open on scale. On 27 January 2026 a federal judge in Virginia found Norfolk’s Flock cameras did not violate privacy rights: “not today.” The cameras did not gather enough to rebuild whole routines, he found. He warned that “the constitutional balancing could conceivably tip the other way” as the network grows (Schmidt v. City of Norfolk, now on appeal). WHRO (11 Feb 2026) Two days later, in State v. Simonson, a Washington appeals court held there is no reasonable expectation of privacy in a plate shown on a public road. That account comes from Flock’s summary of the ruling (vendor source). Flock Safety blog How many cameras, how long data is kept and who can search it: these are exactly what a vendor swap can reset. Only law can lock them 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.

August 2026 update: Flock blinks, and the numbers keep climbing

Two things moved after this piece first published, and both sharpen its argument rather than soften it.

Flock changed its own rules — which is exactly the point about vendor controls. On August 13, 2026, under sustained pressure, Flock announced it would cut its recommended default data-retention period from 30 days to seven, require officers to attach a case code to every search, and make its “Audit Assistance” misuse-detection tool mandatory for all law-enforcement customers by the end of 2026, with case codes mandatory on the same timetable and multi-factor authentication already required since early August. It also added “offense filtering,” letting a city allow another agency to search its cameras only for, say, a stolen vehicle while blocking immigration queries. These are real improvements. But notice the mechanism: a private company voluntarily adjusting a default it can adjust back, with existing contracts keeping their old retention periods unless a city opts in. Civil-liberties groups said as much. The ACLU called the shorter retention “a step in the right direction” while describing the other safeguards as “retreads.” Institute for Justice attorney Robert Frommer called the package “window dressing” from a company in “panic mode,” arguing searches should be approved “by judges with real warrants.” Associated Press, as excerpted by Slashdot (14 Aug 2026) That is the whole thesis of this page in miniature: a control that lives in a vendor’s settings panel, not a statute, is a control that survives only as long as the vendor and the contract do.

And the exodus accelerated. By mid-August, DeFlock’s tally of agencies or communities that had canceled, suspended, rejected, or deactivated Flock since the start of 2026 still stood above 50 and kept growing, with fresh actions that month in Rhode Island and Nebraska, five Arizona cities dropping contracts, and Burnet County, Texas removing all its fixed cameras after repeated vandalism. By 3 September the Institute for Justice’s new cancellation database — which excludes mere pauses and vendor swaps — listed 163 local governments in 31 states and DC. Newsweek, mapping DeFlock data on 28 July, counted 95 cities that had rejected ALPR systems and more than 122,000 cameras mapped nationwide. The through-line holds: the cancellations are real, the pushback is bipartisan, and the durable question is still whether what replaces Flock — Axon, or Flock’s own reformed defaults — is bound by law or only by a promise.

September 2026 update: the streetlight camera, and the pressure spreads to Axon

Three developments in the two weeks after the August update go to the heart of this piece: the swap is now visible in council minutes, the vendor being swapped to is now under the same congressional scrutiny, and the hardware that makes the swap easy has been sitting in Axon’s catalogue since 2025.

Axon Lightpost turns any streetlight into a plate reader. Announced alongside Outpost on April 22, 2025 and built with the streetlight-electronics firm Ubicquia, Lightpost mounts on an existing streetlight and draws regulated AC power from it, “without new poles, trenching, or delays,” in Axon’s words. It reads plates on the device itself, uploads the LPR metadata to Axon Fusus over an integrated LTE modem, and lets an authorised Fusus operator open a live video stream from it. That is the same capability set as a Flock Falcon with one difference that matters for this article: the mounting point. A city that cancels Flock and later approves a “streetlight modernisation” or Fusus expansion can end up with plate readers on every lit block without a single new pole to notice or a single line item that says license plate reader. The product is not new; what is new is that residents have started asking about it.

The swap, in the record. Abington Township, Pennsylvania commissioners were set to vote on 27 August on replacing Flock with Axon — two cameras at $6,576.50 a year for five years. A second Flock contract runs to 2028 and cannot be ended early; “We can’t get out of it,” a police lieutenant said. On August 28 the Boston Globe reported that Boston police had been running Motorola and Axon ALPR pilots since January and June respectively. The pilots came to light through city records. That followed a 2025 Flock pilot the city did not extend; two councillors said they had been unaware of the pilots. Not every city followed the script. Tempe, having shut Flock off, pulled a nearly $7 million Axon item carrying 11 ALPR cameras from its August 31 agenda as a “clerical error.” The mayor said “we are not seeking another provider.” In Santa Barbara, whose Flock contract ended on 23 August, city staff recommended Verkada over Axon and Motorola, whose systems had “higher costs or limited privacy controls.”

The scrutiny follows the logo. Senator Josh Hawley opened a Senate Judiciary subcommittee investigation into Flock on August 26, then on September 3 sent the same letters to Axon, Motorola Solutions and Verkada, responses due September 16 — the clearest institutional statement yet that the problem is the capability, not the vendor. A bipartisan “Flock-Off Act” introduced the same week would bar federal funding for plate readers outside borders and tolling, vendor-neutral by design. And on the night of August 27 Texas Governor Greg Abbott directed all state agencies to pause funding for Flock cameras — a Flock-specific order covering state money, which is exactly the kind of lever this article warns can be routed around with a different purchase order. Watch what Texas agencies buy next.

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”); Denverite (Denver contract terms and vote); Gadget Review (state-law analysis); CNY Central (Syracuse Axon contract & oversight gap); City of Mountain View and Oxnard Police Department statements (audit findings); EFF Deeplinks (Austin cancellation, Axon parallel contract); WHRO (Norfolk ruling); Newsweek / DeFlock (nationwide camera map); Axon.com and Axon press materials (Fusus capabilities, 8.1B plate reads, a vendor claim). 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.