Documented Incident

Police MisuseCities RejectingData SharingLegislationArizona

Phoenix-area cities reassess ALPR programs after alleged officer misuse in Chandler, Apache Junction and elsewhere

Several Phoenix-area agencies are reviewing or curtailing automated license plate reader programs following allegations that officers misused Flock Safety data. Chandler canceled its Flock contract after an audit and said an officer resigned when confronted about tracking an elderly relative, while an Apache Junction officer resigned after admitting he tracked his wife's movements; Surprise, Goodyear and Apache Junction officers are also under investigation. On Aug. 10, Tempe announced it was halting all data sharing from its 33 Flock cameras, citing community privacy concerns and recent misuse by two local agencies. Phoenix police, by contrast, use Motorola Solutions/Vigilant systems rather than Flock, under contracts approved by the City Council in 2022 and 2025.

Why this matters

The cluster of resignations and investigations across neighboring Arizona jurisdictions shows how ALPR misuse in one agency can trigger contract reviews in others, and raises questions about what audit and access controls exist before deployment. It also illustrates that ending a Flock contract does not necessarily end ALPR use, as cities weigh competing vendors.

Key facts

Sources

This summary was written from the published reporting below and links to it; BlockFlockNow does not reproduce article text.

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 24, 2026. Corrections: blockflock@bytebunny.io. See all documented incidents or search the full article archive.