Documented Incident

LegislationCities RejectingPrivacyArizona

Tempe council member proposes city ordinance to permanently bar ALPR use after Flock contract ended

Tempe Councilmember Bobby Nichols says he will introduce an ordinance to write the city's decision to stop using automated license plate readers into city code, after Tempe ended its contract with Flock Safety in August 2026 over concerns about potential misuse. As drafted, the measure would bar the city from using ALPRs for law enforcement, require destruction of existing ALPR data, and make violations a firing offense for employees, with carve-outs for missing-person cases, warrant-authorized searches, and non-law-enforcement uses such as parking management. Nichols plans to introduce the ordinance at the September 24 council meeting, with a possible vote as early as October. Retired detective and Tempe resident Bill Richardson opposes an outright ban, saying the technology is a useful investigative tool and that safeguards could be strengthened instead.

Why this matters

If adopted, the ordinance would move Tempe from an administrative contract decision to a binding local law, a step no other Arizona city has taken. It tests whether communities can lock in surveillance limits beyond the term of a single vendor agreement or council majority.

Key facts

Timeline

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