On August 7, 2026, the City of Chandler announced it would discontinue its 40 automated license plate readers and decline to renew its agreement with Flock Safety. It is the largest Arizona city to end a Flock partnership.
The headline is straightforward. The details are more useful, and three of them deserve to be raised at every council meeting in the region.
1. The audit worked — after three years
Chandler did not act because a resident complained or because a lawsuit forced it. Its own routine audit process flagged something. Per the city’s statement, for the first time in three years of audits, the review “identified an anomaly in the use of the Flock system that could not be explained through standard police action.” Police Chief Bryan Chapman described it as “a potential misuse of the system by somebody in our organization.”
Access was cut for the entire department immediately — roughly 200 of about 560 personnel had it — and an internal investigation opened.
Both readings of this are fair, and honest advocacy should state both. The audit is evidence that oversight can work. It is also evidence that a system can run for three years before routine oversight surfaces anything, which leaves an obvious question about the preceding period that nobody can now answer.
The city said its initial review made clear no resident’s privacy was compromised. That is the city’s characterisation of an investigation it had not finished, and we report it as the city’s position rather than as established fact.
2. The 88-to-1 ratio is the real finding
This is the number that should travel, and it has received far less attention than the shutdown itself.
An ABC15 investigation reported that in January 2026, Chandler PD ran roughly 454 searches of its own system across about 70 investigations. In that same month, outside agencies ran nearly 40,000 searches of Chandler’s data.
That is roughly 88 external searches for every internal one.
Think about what that means for local control. Chandler’s council approved a system, set a retention period, and adopted a policy governing how Chandler officers use it. Those rules covered barely more than one percent of the actual searching. The overwhelming majority of use was by officers in agencies the council does not oversee, cannot audit, and cannot discipline.
This is the concrete answer to the most common reassurance offered in these debates — that a city’s policy protects its residents. A policy governs your own officers. It does not govern the network.
3. No council vote ever happened
Worth understanding for anyone planning a campaign elsewhere.
A renewal vote was scheduled for May 21, 2026. Facing organised opposition, the council postponed it to July 16, then to August 13. On August 7 — six days before that third date — the city announced the program was ending.
Declining to renew an expiring agreement was an administrative act. It did not need a vote, and the scheduled vote became moot.
Two lessons follow. First, a postponed vote is not a defeat; sustained pressure across three postponements is what created the conditions here. Second, campaigns built entirely around winning a council vote can miss where the decision actually gets made. Contract expiry dates deserve as much attention as agendas.
What the department said, fairly stated
Chandler PD defended the system throughout and continued to after the shutdown. Chief Chapman told the council in May 2026: “I can point conservatively to over 2,000 positive applications of ALPR technology here in Chandler,” citing fleeing home-invasion suspects, a wanted robbery suspect, and missing dementia patients. Reported department figures included about 7,600 alerts in the last fiscal year and, for July 2025 through April 2026, 16 stolen vehicles recovered, 9 missing persons located, and 39 arrests.
On announcing the shutdown he said the decision “slows down our investigative capacities.”
These figures come from department presentations reported in local media. They have not been independently audited and we have not obtained the underlying case data. We repeat them because they are the department’s honest position, and because an argument that only works when you hide the other side’s best evidence is not an argument worth making.
The question was never whether these systems are ever useful. It is whether that usefulness justifies recording everyone, and whether the same results could be obtained with narrower tools and lawful process.
Chandler was not alone that week
Days earlier, the Pinal County Sheriff announced he would not renew his office’s Flock contract when it expires at the end of September 2026, citing Fourth Amendment concerns. Roughly 22 of those 45 cameras sit inside San Tan Valley — a town that only incorporated on July 1, 2026 and is now setting its surveillance policy from scratch.
And on August 10, Apache Junction disclosed that one of its officers had used reader technology to locate a family member, telling dispatchers it was a welfare check. He resigned. That case was caught by two dispatchers’ judgment, not by any audit.
Three East Valley agencies, one week. That is a pattern, not an anecdote.
Five questions for your own council
- How many searches of our data were run by outside agencies last month, and how many by our own officers? Ask for the number, not a reassurance.
- Which agencies can search our data, and who approved that list?
- When does our contract expire, and what happens if we do nothing?
- How many audits have we run, what did they look at, and what did they find?
- If misuse were occurring right now, what specifically would detect it?
The Chandler and Apache Junction cases answer question five uncomfortably. One took three years of audits to surface. The other was caught because two dispatchers thought a request felt wrong.
Sources
Every factual claim above traces to the entries in our Decision Record and Documented Harms collections, where each source is listed individually with its sourcing tier. The primary document is the City of Chandler’s own news release.
The search-volume figures come from ABC15’s investigation into ALPR data access in Arizona.
If we have any of this wrong, tell us — corrections are dated and left visible on the page.
Correction log
No corrections to date. If something here is wrong, tell us — per our standards, we correct mistakes publicly and log the correction on this page.