Axon Is Another License Plate Surveillance Company

Bruce Schneier's July 28 post on the Flock-to-Axon swap. The cameras still read plates, the vendor's wider stack reads a great deal more than plates, and whether the data leaves town turns out to be decided by the contract rather than the logo on the pole.

State of Surveillance Editorial Team

TL;DR: Bruce Schneier posted on July 28, 2026 that cities ditching Flock Safety over its undisclosed ICE and Border Patrol access are landing on Axon, which is itself a license plate reader company wrapped in a much larger surveillance product line. His own verdict was hedged: "Governments are switching, but I'm not sure it makes a difference." Denver is the case in point. The city ended its Flock contract in February 2026, and on March 31 the council approved a $150,000 one-year Axon deal for 50 cameras, about half the 111-camera Flock system it replaced, on a 7-6 vote and over the objection of 14 community organizations. Axon markets plate reading as one feature among many: body cameras, drones, small uncrewed ground vehicles, tasers, the Fusus real-time crime center, and an AI platform the company says can recognize physical altercations and medical emergencies in real time.

What Schneier Actually Said About the Flock-to-Axon Switch

Bruce Schneier posted on July 28, 2026 under the headline "Axon Is Another License Plate Surveillance Company." His own comment on the swap was one hedged sentence: "Governments are switching, but I'm not sure it makes a difference" [1]. The post runs to roughly 200 words, most of which is a block quotation from a Jalopnik explainer published two weeks earlier [1][2].

It is the quoted Jalopnik passage, not Schneier, that names the city: "some municipalities, including Denver, Colorado, are ditching their Flock arrays" [1][2]. The point both writers make is the same one: switching vendors does not switch the underlying business model. The cameras still read plates, and Axon's broader product line means there is a great deal more than plates to read.

The analogy that traveled is Jalopnik's, quoted by Schneier in full: "But keep in mind that if they're only switching from Flock to another brand of license-plate readers, like Axon, it's like a gambling addict trying to kick the habit by switching from FanDuel to DraftKings" [1][2]. The implication is the one that matters for every council weighing an Axon contract: cancelling a vendor is not the same act as exiting surveillance.

What Axon Cameras Actually Collect

Jalopnik's Krome laid out the case on July 14, 2026. His core argument: "The difference is that an Axon network can actually put your privacy at a higher risk than one from Flock" [2].

Axon cameras, Krome wrote, "are pretty effective when it comes to hoovering up personal details that can go far beyond your license plate numbers" [2]. Krome quoted the company describing its Axon Vision technology as capable of recognizing "observable activity such as physical altercations, unauthorized access, medical emergencies, or hazardous conditions" in real time [2]. He also pointed to what the company says about data integration: "All that data can be integrated and viewed onscreen in real time using Axon's Fusus system" [2].

Fusus is the real-time crime center software Axon sells to police agencies. It pulls in video feeds, sensor alerts, and analytics from partner products and stitches them into a single operational picture for dispatchers and officers. Krome's wider point: Axon is "a full-line privacy invader with an entire public safety 'ecosystem'" that already includes body cameras, drones, ground robots, and tasers [2]. Axon, the article notes, was the company that "invented the devices" behind the modern conducted-energy weapon, and those tasers "are incorporated into its web of connected products" [2].

The contrast with Flock matters here. Flock's product surface is narrow: cameras, a national lookup network, and analytics. Axon's product surface is wide enough that the license plate reader is the entry point, not the product. The Denver Justice Project's Casey Childres summed it up in a March 29, 2026 organizing page: "a race to the bottom of more pervasive and more powerful surveillance" with "real-time, AI-powered crime centers" as the destination [6]. The same page notes that Axon's AI Ethics Board resigned after the company ignored its warnings, a fact Childres flagged as relevant to any city signing a long-term contract [6].

The Flock-to-Axon Switch Does Not Stop the Data Sharing

The privacy problem that drove cities to cancel Flock was not the cameras. It was the data leaving the city. ACLU of Colorado documented the issue on March 23, 2026: "Flock's undisclosed partnership with U.S. Border Patrol was exposed through analysis of the company's audit logs," and the audit logs "show Denver's data was searched more than 1,400 times from June 2024 to April 2025 by ICE or by law enforcement on behalf of ICE" [5]. Denver's city auditor declined to sign the city's Flock contract over those terms [5].

Krome made the same point about Axon in the other direction. Flock's defense has been that local law enforcement agencies "control their own data and don't have to share it with anyone," and that the agency-controlled opt-in to a national lookup service is the only path out the door. Krome noted that 75% of Flock agencies opt into the national lookup service [2]. Then came the part that undoes the Flock talking point: "So Denver could have opted out if that was a real issue with Flock" [2]. And, more directly, "there's nothing stopping Denver, or another city, from voluntarily sharing its Axon data either" [2].

The vendor does not decide whether data leaves town. The contract does. The vendor simply controls how easy it is to share, and how cleanly the resulting network stitches together with neighboring jurisdictions. Axon's Fusus platform, by design, integrates data from partner products across a region in real time. The same architecture that makes Fusus attractive to a police chief makes it attractive to any federal agency with an account on the network.

Denver Is the Test Case

Denver announced on February 24, 2026 that it would end its Flock Safety contract, and an Axon proposal followed quickly. ACLU of Colorado's press release describes the timing: the proposal surfaced "just a week after publicly announcing the city had issued a request for proposals" [5]. ACLU and partner organizations had pushed for the cancellation, citing the ICE queries [5]. On the numbers the release is precise: "Axon's $150,000 proposed contract for a 50-camera system is about half of Flock's current 111-camera system" [5].

On March 23, 2026, the morning of the scheduled vote, a coalition of 14 community, advocacy, and civil rights organizations, along with members of Denver's own Surveillance Task Force, sent a letter to city councilors asking them to vote no. ACLU of Colorado's Anaya Robinson, the group's public policy director, framed the issue in plain terms: "The city cannot simply move from one dragnet surveillance company to another and trust that these for-profit companies will put people's civil liberties first" [5]. Robinson's second point is the structural one: "The city must implement critical protections around data retention, information sharing, access limitations, and meaningful community input and legislative approval policies to prevent abuses from government agencies and law enforcement" [5]. Her third was about the off-ramp: "Continuing to operate this risky, unregulated surveillance technology in the city carries far greater risks than pausing the ALPR program" [5].

The Denver Surveillance Task Force members on the coalition letter added their own framing: "Mayor Mike Johnston must not repeat past mistakes. He cannot continue to ignore the concerns of the people of Denver by shutting them out when making decisions that will directly impact their privacy and safety" [5]. They asked the mayor to commit to community oversight and to work with the Surveillance Task Force to draft regulatory guidelines before continuing the program [5]. The council put the vote off that night. The Denver Justice Project's organizing page, published March 29, called on residents to join it at Denver City Council on Monday, March 30 at 5:30 PM [6].

The story Schneier and Krome were telling does not turn on how one council voted. It is that the cancel wave against Flock, documented across more than 30 cities on this site's running list, is producing replacement contracts rather than retirements [3][4]. Camera counts do not all move in one direction either. Denver's replacement is smaller than the system it retired, while Douglas County, Colorado approved a package that doubles its own count [9].

What to Watch

Three things to track.

First, whether Denver's contract terms become the template or the exception. Denver wrote a 21-day retention limit, a bar on federal access, and logged and audited queries into the deal itself [7]. The open question is whether the next Colorado city to sign with Axon copies those clauses or accepts a stock agreement.

Second, watch for Axon contracts that bundle plate readers with Fusus and Axon Vision. Krome's argument is that plate reading is the loss-leader and the integrated real-time crime center is the real product [2]. Douglas County's package, which pairs 100 plate readers with a countywide first-responder drone network, is what that bundle looks like at county scale [9].

Third, watch the audit logs, and watch whether anyone outside a police department ever sees them. The reason Denver canceled Flock was not the cameras. It was the queries from ICE and partner agencies that surfaced only afterwards, through an analysis of Flock's own audit logs [5]. A contractual right to audit is not the same thing as a public record, and the gap between those two is what the ACLU's ask about information sharing was really about.

Update (10 August 2026)

Denver City Council approved the Axon contract on March 31, 2026 on a 7-6 vote, a week after postponing it. The terms are the ones the ACLU letter described: $150,000, one year, 50 cameras. Flock's contract with the city ended the same day [7][8].

The approved contract carries limits at the contract level that the advocacy coverage above was written to demand. Denver's data is held for 21 days rather than Flock's 30. Axon runs no national lookup network, so no outside agency can query Denver's system the way ICE queried Flock's. Access is restricted to Denver safety employees, requires a login, and is audited. Council Member Kevin Flynn put the network point plainly: "Axon does not have a national network. There's no way that we can share it nationally. No law enforcement officer in Texas, Ohio, New York, or California can log into our system." Police Chief Ron Thomas said the city would "bar access from federal agencies, but also from other law enforcement agencies" [7].

That does not settle the objection the coalition raised, which was about the absence of a regulatory framework rather than the wording of a single contract. ACLU of Colorado's Anaya Robinson said after the vote that "these cameras do not belong in the city without crucial regulations in place to protect the privacy and safety of people in Denver," and that the council acted before Denver's own Surveillance Task Force could weigh in [8].

The swap is also not staying small. On July 14, 2026 the Douglas County Board of County Commissioners approved a contract worth about $22.8 million with Axon that replaces the county's 50 Flock cameras with 100 Axon Outpost plate readers and adds a countywide first-responder drone network. It begins January 1, 2027, with a $1.9 million first-year purchase. The reason sheriff's officials gave for leaving Flock was data ownership. Division Chief Taylor Davis told commissioners that "currently right now with Flock, we do not own that data" [9].

Sources

  1. Schneier on Security: "Axon Is Another License Plate Surveillance Company" (July 28, 2026)
  2. Jalopnik: "Some Municipalities Are Replacing Flock Cameras With Axon, But Is There A Difference?" by Charles Krome (July 14, 2026)
  3. State of Surveillance: "30+ Cities Have Canceled Flock Safety Contracts. The List Keeps Growing" (May 19, 2026)
  4. State of Surveillance: "Deflock: The Flock Safety Revolt" (2026)
  5. ACLU of Colorado: "Community Organizations and Denver Surveillance Task Force Members Ask Denver City Councilors to Vote No on Axon ALPR Contract" (March 23, 2026)
  6. Denver Justice Project: "NO FLOCK! NO AXON! Denver Must Reject the Expansion of Mass Surveillance" by Casey Childres (March 29, 2026)
  7. Denver7, Maggie Bryan: "Denver City Council narrowly approves Axon contract to replace Flock cameras" (page carries no visible publication date; reports the March 31, 2026 council vote and the contract terms)
  8. ACLU of Colorado: "Denver City Council Approves New Axon Contract to Replace Flock, Despite Community Concerns and Calls for a No Vote" (April 1, 2026)
  9. Denver Gazette: "Douglas County to replace Flock cameras with $22.8 million Axon system" (July 15, 2026)