Documented Incident

LegislationCities RejectingPrivacyVandalismArkansas

Lowell, Arkansas council to weigh ordinance banning ALPRs, facial recognition and audio sensors

A proposed ordinance introduced by Lowell City Councilman Adrian Flores would bar the city from using Flock Safety automated license plate readers, acoustic listening devices and facial recognition technology. The measure, called the Citizens' Liberty and Information Privacy (C.L.I.P.) Ordinance, would require existing systems to be disabled within 30 days, hardware removed within 60, and historical data deleted within 30 days after that, except records tied to active criminal cases. Flores said he learned of the city's four cameras roughly a year after installation and alleges Flock structures contracts to stay just below thresholds that would trigger council approval; Flock did not respond to the station's request for comment. Lowell Police Chief Tim Kuth said the cameras have aided investigations and raised concerns the audio provision could affect other department equipment.

Why this matters

The proposal tests whether a small city can retroactively unwind an ALPR deployment that was approved administratively rather than by elected officials, and its data-ownership and private-right-of-action provisions could serve as a template for other municipalities.

Key facts

Sources

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

More from Arkansas

Everything we have documented in Arkansas, or search every Arkansas 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 21, 2026. Corrections: blockflock@bytebunny.io. See all documented incidents or search the full article archive.