Documented Incident

PrivacyData SharingNew DeploymentsPolice MisuseAlabama

Birmingham declines to release ALPR contracts as city's surveillance camera network reaches $9.7 million

AL.com reported that Birmingham has roughly 200 mapped automated license plate readers within city limits, most made by Flock Safety, purchased through Alabama Power as an intermediary rather than directly from the vendor. The Birmingham Police Department declined to answer questions about how the data is collected, stored or shared, and the city denied multiple records requests for its camera contracts, saying they did not meet unspecified city and state criteria. The city eventually provided its ALPR policy, which states data is used only for law enforcement purposes and shared with other agencies only with the police chief's approval, though the underlying records retention schedule is not public. City Councilman Darrell O'Quinn said the lack of a direct agreement with the vendor raises questions about protecting residents' data, and DeFlock Birmingham founder Darrell Nance is calling for release of the contracts and public hearings.

Why this matters

Birmingham illustrates how purchasing surveillance equipment through a third-party utility can leave a city without a direct vendor contract, complicating public records access and oversight of a nearly $10 million system.

Key facts

Sources

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

More from Alabama

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