The city of Chandler, Arizona is shutting off all 40 of its Flock automated license plate readers and will not renew its agreement with the company, after a routine internal audit flagged use of the system that the police department could not explain.
The city announced the decision on August 7, 2026, and said it had immediately restricted all Chandler police personnel from accessing the system. Chandler is the largest city in Arizona to end its partnership with Flock Safety.
What the audit found
The finding came out of the department’s own review process, not from an outside complaint. In the city’s words:
“For the first time in three years, our routine audit process identified an anomaly in the use of the Flock system that could not be explained through standard police action.”
The city has said an investigation is under way into whether the system was used inappropriately and what discipline may be required. No employee has been publicly named, and the specific nature of the anomaly has not been detailed.
Chandler has been explicit on one point: its initial review found that no Chandler resident, and no member of the public, had their privacy compromised. That statement is doing real work here — it distinguishes a query that should not have been run from a query whose results were acted on or shared.
How the deployment grew
Chandler’s relationship with Flock began as a pilot. Fourteen license plate readers went in during March 2024. In May 2025 the deployment was expanded to 40 fixed cameras.
Police Chief Bryan Chapman has been candid about what losing the system costs his department, saying investigators would be “significantly behind the curve” without the technology. On the mechanics of the shutdown he said Flock is aware of the city’s plans, and that winding down “could look like taking them down, placing hoods over them.”
The hardware itself is not the city’s to remove. The 40 cameras and their poles remain the property of Flock Group, Inc., and the vendor is responsible for taking them out.
Why the audit is the story
Most Flock disputes reaching the news have been about consent and control — a town that voted the cameras down, a vendor that turned them back on, an installation nobody approved. Chandler is a different case, and in some ways a more instructive one.
Here the cameras were properly authorised, publicly expanded, and running for nearly three years. The problem surfaced from inside: someone at the department appears to have queried the system in a way that police work could not account for.
That is the failure mode privacy researchers have consistently warned is the most likely one. The realistic risk in a plate reader network is rarely a dramatic institutional abuse. It is an individual with legitimate credentials looking up a person for a personal reason — an ex-partner, a neighbour, someone in a custody dispute. Law enforcement database misuse of that kind is well documented across other systems, and it is difficult to prevent through policy alone because the person doing it already has authorised access.
The uncomfortable corollary: Chandler found this because it ran a routine audit and because Flock’s Auto Assist function surfaced the anomaly. Agencies that do not audit would not have found it. The single flag in three years could mean the system was used cleanly for three years, or that the audit process only recently became capable of catching this pattern. There is no way to tell from outside.
Arizona keeps walking away
Chandler is not an outlier in its own state. Flagstaff and Sedona ended their Flock contracts last year, and Pinal County decided this week not to renew, with the sheriff saying he would let the agreement lapse when it expires in under 60 days.
Nationally, more than 20 local jurisdictions have moved toward cancelling Flock contracts, and the opposition has been unusually bipartisan. In Littleton, Massachusetts, the town moved to cancel after discovering the company had reactivated cameras the Select Board voted to switch off. Cambridge terminated its contract after cameras were installed without notification; Evanston, Illinois issued a cease-and-desist over a similar incident. Reporting has also revealed a Flock proposal to add roughly 350,000 Uber, Lyft and delivery vehicles to its network via dashcams — a partnership the company says was never executed.
The company has attracted stranger attention too, including a wave of scams after Google’s AI falsely claimed Flock cameras contain pure gold, prompting thefts of the units themselves.
What Chandler does next
The city has not framed this as an exit from license plate reading altogether. It plans to strengthen safeguards through revised policy, additional audit procedures and new reporting requirements — and, if the City Council approves, may issue a request for proposals from other vendors.
That is the pragmatic position, and it points at the real question. Swapping vendors does not address an insider misuse problem; the controls do. The provisions that matter are query-level justification recorded at the time of search, automated anomaly detection that the agency itself can run rather than relying on the vendor’s tooling, independent review of audit results outside the chain of command, defined retention limits, and explicit consent requirements before data leaves the jurisdiction.
A City Council discussion of the technology is expected later this month. Whether Chandler emerges with a different vendor and the same controls, or the same capability under materially stronger oversight, is the part of this story still unwritten.
