Removing Flock Is a Start. Replacing It With Axon Is Not a Victory

September 4, 2026 • 14:45

Surveillance Axon Flock SignalTrace Florida

Recent decisions in Florida show that public scrutiny can change surveillance policy. They also show why the debate cannot stop with one company.

For years, Flock Safety has been the public face of automated license plate reader surveillance. Its solar-powered cameras are easy to recognize, its nationwide data-sharing network has drawn sustained criticism, and public records have documented troubling uses of the system.

That attention is finally producing results.

On September 1, the Lake County Commission voted to revoke permits for automated license plate readers in county rights-of-way. The decision followed a heated public debate over privacy and the scope of vehicle tracking. Mount Dora is also ending its use of six Flock cameras, according to local reporting. At the state level, the Florida Department of Transportation has revoked approvals for license plate readers on state roads and ordered permit holders to remove them within 30 days. The state action applies to license plate reader systems generally, not only Flock cameras.

These are meaningful developments. Residents raised concerns, public officials listened, and surveillance infrastructure is being removed from public roads. That deserves recognition.

But removing a Flock camera does not necessarily mean the surveillance ends. Across the country, some governments have dropped Flock and then hired Axon to provide substantially similar license plate readers. The logo changes. The underlying practice of recording innocent motorists remains.

Why Flock became the target

Flock is not harmless, but it may not be the most secretive company in this market. It is the most visible.

The cameras themselves are conspicuous. Residents can often identify the pole, solar panel, and camera housing from the street. Flock also offers agencies a public Transparency Portal that can disclose policies, data-retention periods, outside sharing relationships, and aggregate usage information. Flock says more than 1,500 agencies have published a portal.

That transparency is optional. Mount Dora maintained a public portal, while the Lake County Sheriff’s Office did not appear to offer an equivalent Flock portal before the county vote. Whether residents can inspect an agency’s use of the system therefore depends largely on choices made by the agency.

Even imperfect visibility has mattered. Audit logs released through transparency portals and public-records requests helped journalists and researchers examine how officers searched the network. They also made projects such as Have I Been Flocked possible. That site aggregates released audit records so the public can study how the system has been queried.

Flock has recently limited some of that visibility. InvestigateTV reported that changes to network audit logs concealed officers’ names and plate details. Flock said the changes were intended to protect undercover officers and active investigations after activists used released data to identify officers. Whatever the reason, redacting those fields makes independent scrutiny harder.

Flock has also announced new safeguards, including a recommended seven-day retention period for new customers, required case codes, expanded misuse detection, and additional controls over interagency sharing. Existing customers can retain previously approved retention periods. Those are improvements worth noting, but they do not change the basic model: cameras still collect records of vehicles that pass them, including vehicles whose occupants are not suspected of a crime.

The camera you notice may not be the only one watching

Flock’s physical visibility can create a distorted picture of the market. People recognize a Flock camera and reasonably focus on it. Competing systems may be mounted in less obvious housings, on ordinary poles, in roadside cabinets, or inside existing streetlights.

Axon’s Lightpost is a clear example. Axon markets it as a system that turns an existing streetlight into a vehicle-intelligence tool with license plate recognition, livestreaming, and vehicle-attribute detection. Axon Outpost is a more recognizable fixed camera with livestreaming, plate reading, and vehicle recognition. Both feed into Axon’s larger software ecosystem.

The public should not confuse unobtrusive hardware with less surveillance. A device that blends into a streetlight may attract less public attention while collecting the same kind of location record.

Nor should anyone assume that every major vendor provides Flock’s limited public-facing tools. Axon, Motorola Solutions, Rekor, Verkada, and Genetec publish product and privacy materials, but we could not identify a vendor-hosted, agency-by-agency public portal comparable to Flock’s Transparency Portal. Local agencies may publish policies or statistics independently, but that is not the same as a standard public window into deployments, retention, sharing, and use.

The Axon alternative deserves more scrutiny, not less

Axon is already deeply embedded in law enforcement. It manufactures TASER energy weapons, supplies body-worn cameras, and operates the Axon Evidence platform used to manage digital evidence. Adding fixed license plate readers does not create an isolated camera network. It adds another stream of information to an existing policing ecosystem.

Several cities have made that switch. Denver declined to renew its Flock contract and selected Axon, which already supplied the police department’s body cameras and data storage. Longmont, Colorado, allowed its Flock contract to lapse and then moved toward Axon license plate readers. Syracuse, New York, also replaced Flock readers with Axon. The Guardian reported in August that Axon had moved to replace Flock in at least seven municipalities across five states.

Some of those cities added meaningful restrictions. Denver, for example, announced limits on retention and federal data sharing. Contract terms and local law matter. An Axon deployment with strict retention, warrant requirements, independent audits, and no external sharing is not identical to an unrestricted nationwide Flock deployment.

Still, the central civil-liberties question remains: should a government routinely record the movements of every passing vehicle in order to investigate the small number associated with a crime?

Axon Fusus makes that question larger. Axon describes Fusus as a real-time platform that places officer locations, dispatch data, alerts, license plate reader results, and video feeds into a single map-based interface. Its Community Connect program can also incorporate cameras shared by residents and businesses. Axon’s documentation says owners control whether and when their cameras are shared, and the company markets the arrangement as permission-based.

The concern is not that every connection is inherently abusive. The concern is aggregation. Body-camera streams, city cameras, participating private cameras, vehicle sightings, alerts, and other operational data become more powerful when viewed and searched together. A system capable of helping officers respond to a serious incident can also become a broad surveillance platform if access rules, retention limits, auditing, and public oversight are weak.

In that respect, Fusus may present a larger long-term risk than a standalone Flock deployment. Flock built a highly visible nationwide vehicle-search network. Axon is positioned to connect vehicle tracking to a much wider collection of cameras, evidence, sensors, and police operations. At present, Axon’s fixed-reader system is not documented as offering the same nationwide, cross-agency search network that made Flock especially controversial. That is a material difference, but not a reason to give Axon a free pass.

Surveillance is already moving beyond license plates

The next generation of roadside surveillance may not need a readable plate at all.

The relevant product here is Leonardo’s ELSAG SignalTrace, sometimes confused with Google’s unrelated Sensorvault location database. Leonardo says SignalTrace passively detects publicly broadcast Bluetooth, Wi-Fi, RFID, and other supported wireless signals. It groups signals that routinely travel together into an electronic fingerprint, stores the resulting data for analysis, and can correlate it with license plate reader records.

The company’s own examples include mobile phones, smartwatches, fitness trackers, RFID tags, and vehicle electronics. Product materials also describe identifying vehicles through an electronic signature even when a plate number is unavailable. Reporting based on Leonardo’s materials has identified wireless headphones, vehicle hotspots, infotainment systems, and tire-pressure sensors among the potential signal sources.

Leonardo says SignalTrace does not decrypt communications, read their contents, or directly identify individuals. That distinction is real. Capturing a broadcast identifier is not the same as reading a text message.

It is also not reassuring enough. A persistent electronic signature can reveal that the same cluster of devices appeared at multiple locations, traveled with another cluster, or moved from one vehicle to another. Even if the system begins with pseudonymous signals, repeated correlation with license plates, places, and other records can make movements and associations revealing. The privacy risk comes from linking observations over time.

SignalTrace also demonstrates why a campaign focused exclusively on visible cameras is too narrow. A sensor can follow a vehicle by its electronics and can potentially follow a device into places where vehicles never go, including malls or transit systems. Public understanding and oversight have not kept pace with that shift.

The standard should apply to the practice, not the brand

Public pressure on Flock has been productive. It exposed weak policies, forced officials to defend their choices in public, contributed to canceled contracts, and pushed Flock to announce stronger safeguards. Lake County, Mount Dora, and Florida’s broader action on state roads show that surveillance policy is not inevitable.

The next step is harder. Communities need to resist treating vendor replacement as reform.

Before any new surveillance contract is approved, officials should publicly answer basic questions: What is collected? How long is it kept? Who can search it? Is a warrant required? Which outside agencies can gain access? Can federal agencies obtain the data directly or indirectly? Are searches independently audited? Will residents receive public reports detailed enough to reveal misuse? Can the system be integrated with private cameras, body cameras, facial recognition, device identifiers, or other databases later without another public vote?

If those questions are not answered before procurement, the public is not being asked to approve a defined tool. It is being asked to trust an expandable surveillance platform.

Flock should face scrutiny. So should Axon, Motorola, Rekor, Verkada, Genetec, Leonardo, and every other company selling systems that record or connect the movements of people who are not suspected of wrongdoing.

Removing six Flock cameras in Mount Dora is a concrete win. Removing readers from state and county rights-of-way is a larger one. But the goal cannot be to replace a camera people recognize with a sensor they do not. The goal should be to reject suspicionless dragnet surveillance, regardless of the hardware enclosure or the vendor name printed on the contract.

Sources

Research note

This article reflects information available through September 4, 2026. Claims about a complete absence of transparency across competing vendors are difficult to prove universally. The article therefore uses the narrower, supportable formulation that no comparable vendor-hosted, agency-by-agency public portal was identified during this review. Local agencies may publish their own policies, contracts, or usage reports.