Documented Incident
Chandler Residents Weigh In as City Council Prepares Vote on Flock Contract Renewal
First reported: August 7, 2026 · 2 sources
ABC15 canvassed people in downtown Chandler, Arizona, about the city's use of Flock Safety automated license plate reader cameras ahead of a City Council decision on renewing the contract. The council had tabled a renewal vote in May and scheduled a study session with public comment before a vote at its regular meeting. Residents interviewed expressed a mix of support and opposition, according to the report.
Chandler's renewal debate shows how contract expirations create recurring decision points where councils must publicly revisit ALPR surveillance, giving residents a formal opening to weigh in.
Key facts
- Chandler City Council tabled a vote on renewing its Flock contract in May.
- A study session on the cameras was set for Monday at 4 p.m. with 15 minutes of public comment.
- Additional public input and the vote were expected at the regular meeting on Thursday, August 13, at 6 p.m.
- ABC15 reported a range of resident views, both supportive and opposed; the report did not quantify overall public sentiment.
Sources
This summary was written from the published reporting below and links to it; BlockFlockNow does not reproduce article text.
- For it or against it: What Chandler residents think about Flock license plate reader cameras (ABC15 Arizona, August 7, 2026)
- Chandler Council hears it from Flock technology opponents (yourvalley.net, August 14, 2026)
More from Arizona
Everything we have documented in Arizona, or search every Arizona article in the archive.
About this record
BlockFlockNow documents reported incidents involving Flock Safety cameras and automated license plate readers: council votes, contract decisions, misuse by authorized users, lawsuits, audits, and community response. Every record is reviewed by a person before publication. New to the topic? Start with What is Flock?, find meetings near you, or learn how to request your town's camera records.
Updated August 15, 2026. Corrections: blockflock@bytebunny.io. See all documented incidents or search the full article archive.