Flock Camera Controversies
Flock Camera Controversies by State
Flock camera controversies are no longer one national argument. They are local fights shaped by state law, city contracts, immigration enforcement fears, audit logs, public-record access, and whether residents believe their council approved surveillance before asking hard questions.
The short version
The Flock camera fight looks different by state. In California, the central issue is whether ALPR data sharing follows SB 34 and the state attorney general's guidance. In Texas, the live examples are San Marcos removing city-contracted cameras and El Paso debating a large police camera contract. In Iowa, Coralville ended its Flock contract after public backlash and pressure over immigration-enforcement limits. In Minnesota, Columbia Heights terminated service after residents and officials questioned privacy, sharing, and local control.
That pattern matters more than any single headline. Cities are not only asking whether automated license plate readers help police. They are asking who can search the data, which agencies can receive access, whether local restrictions survive state or federal pressure, how long records are kept, and whether the contract gives the city a clean exit.
This tracker is not a claim that every Flock camera program is unlawful or failing. It is a map of the public controversies that keep repeating across states.
California: sharing rules drive the fight
California is the clearest legal-risk state because it has a specific ALPR framework. SB 34 requires public agencies using ALPR systems to provide an opportunity for public comment before implementation, maintain a usage and privacy policy, use reasonable security safeguards, keep access records, and limit use to authorized purposes.
The California Department of Justice reminded law enforcement agencies in October 2023 that ALPR collection, storage, sharing, and use must comply with state law. EFF summarized the guidance as confirming that California agencies may not share license plate reader data with out-of-state or federal agencies.
That is why California Flock fights often focus on sharing settings, not just camera locations. Residents want proof that local data is not available to federal, out-of-state, or indirect partner searches in ways that violate California rules or local promises.
California cities to watch
South Pasadena became a useful example because local coverage tied Flock pushback to broader concern over California ALPR data sharing and federal immigration access. LAist reported in March 2026 that some South Pasadena residents wanted the city's Flock readers gone after reports about Southern California agencies sharing license plate reader data.
San Francisco is another pressure point. EFF and the ACLU of Northern California said in 2025 that San Francisco police had shared ALPR data with out-of-state and federal agencies and called for that sharing to stop. The issue is not only whether a city owns cameras. It is whether outside searches can reach local plate data.
For California city councils, the practical rule is simple: no public meeting, no written ALPR policy, no verified sharing controls, no audit trail, no clean approval.
Texas: local control is the open question
Texas does not have the same single ALPR framework as California, so the fights are more local. San Marcos is the strongest current example. The city's ALPR page says the city council voted on December 2, 2025 to discontinue its Flock Safety contract and that, as of February 1, 2026, all city-contracted Flock cameras had been deactivated and removed.
The same San Marcos page says the police department stopped automatic sharing of license plate reader data with other law enforcement agencies effective June 9, 2025 and moved to a request-based process tied to a specific criminal investigation or prosecution. It also describes 30-day access and regular audits.
El Paso shows the other side of the Texas debate. El Paso Matters reported in March 2026 that the city was weighing a Flock Safety camera contract for police. That story put contract scale, retention, public-safety claims, and civil-liberties concerns in front of the council instead of treating the purchase as routine equipment.
Iowa: immigration limits became the flashpoint
Coralville is one of the cleanest cancellation examples. The Daily Iowan reported that the Coralville City Council voted in February 2026 to terminate a two-year Flock Safety contract, initiating removal of surveillance cameras. Little Village reported that the council ended the contract after backlash and that residents told the city 'never again.'
The public fight grew beyond whether the cameras could help investigations. Coralville residents raised privacy and process objections, and the debate sharpened after the Iowa Attorney General's Office pushed the city over policy language limiting immigration-related use.
The lesson for other Iowa cities is not that every camera vote will end the same way. It is that a local ALPR policy can become unstable if the city cannot explain how state pressure, federal requests, and vendor-network access interact with local limits.
Minnesota: Columbia Heights became a trust test
Columbia Heights terminated Flock service in June 2026 after months of concern over privacy, data sharing, immigration enforcement, and local control. MPR News reported that the city council voted to end the Flock Safety camera contract.
The city's own Flock page later said service had been terminated, five city-installed cameras had been removed, seven Flock-installed cameras remained covered with black plastic until removal, police database access had ended, and data sharing with all agencies had been shut off.
That sequence made Columbia Heights a trust case. Police and public-safety officials argued the cameras had value, but the council still moved to termination once residents and officials were no longer comfortable with the system's controls.
Ohio and Michigan: contract oversight is the recurring issue
Cleveland and Troy show a quieter but important version of the controversy: contract oversight. The questions are camera count, renewal terms, data access, audit logs, retention, and what residents can see before the system expands.
Cleveland's public council file and local reporting made the city's proposed Flock expansion visible as a public contract issue. Troy's city council materials and order form showed how a local Flock purchase can hinge on ordinary-looking procurement documents that still carry surveillance-policy consequences.
For cities in states without a strong ALPR statute, these local documents matter even more. If the contract is vague on sharing, audits, cancellation, data deletion, and camera removal, the city may not have enough control when public concern rises.
The pattern across states
The same questions keep showing up: Who approved the cameras? Was there a public meeting? How long is plate data retained? Which outside agencies can search it? Are searches tied to case numbers? Are audit logs reviewed? Can the city stop sharing immediately? What happens if the contract ends?
Controversies often start when residents discover the system after approval. They grow when officials cannot produce the policy, the sharing list, the audit trail, or the contract terms quickly. They peak when immigration enforcement, out-of-state access, or vendor network features make local control feel uncertain.
That is why Flock camera debates are becoming governance fights. A camera can be useful and still create public backlash if the city cannot prove the system is narrow, auditable, and locally controlled.
What residents should ask in any state
Residents should request the Flock contract, order form, renewal terms, camera list, retention rule, sharing settings, agency-sharing list, audit logs, search policy, case-number requirements, public meeting record, and any immigration-enforcement policy.
They should also ask whether data is available to federal agencies, out-of-state agencies, fusion centers, task forces, private entities, or other departments through request-based access, automatic sharing, mutual aid, or vendor network features.
If officials say the answer is no, ask for the current settings and logs that prove it. ALPR oversight should be evidence, not reassurance.
The bottom line
The state-by-state controversy map is still early, but the direction is clear. California is about statutory compliance and sharing limits. Texas is about local control and public process. Iowa and Minnesota show how immigration-enforcement fears and trust breakdowns can end contracts. Ohio and Michigan show why procurement documents deserve surveillance-level review.
For any city considering Flock, the safest path is public approval, published policy, narrow sharing, documented audit logs, clear retention, and exit terms that give the city real control.
The controversy is not only about cameras. It is about who controls the plate data after the cameras start working.
Sources used
California Legislature, SB 34 bill text, Automated license plate recognition systems: use of data: https://leginfo.legislature.ca.gov/faces/billNavClient.xhtml?bill_id=201520160SB34
California Department of Justice, Attorney General Bonta Advises California Law Enforcement on Legal Uses and Management of Automated License Plate Recognition Data, October 30, 2023: https://oag.ca.gov/news/press-releases/attorney-general-bonta-advises-california-law-enforcement-legal-uses-and
Electronic Frontier Foundation, California Department of Justice Declares Out-of-State Sharing of License Plate Data Unlawful, October 31, 2023: https://www.eff.org/deeplinks/2023/10/victory-california-department-justice-declares-out-state-sharing-license-plate
LAist, Some South Pasadena residents want the city's Flock license plate readers gone - they're not alone, March 5, 2026: https://laist.com/news/some-south-pasadena-residents-want-the-citys-flock-license-plate-readers-gone-theyre-not-alone
City of San Marcos, Automated License Plate Readers (ALPR): https://www.sanmarcostx.gov/4530/Automated-License-Plate-Readers-ALPR
El Paso Matters, City weighs Flock Safety camera contract for El Paso police, March 2, 2026: https://elpasomatters.org/2026/03/02/flock-safety-license-plate-reader-cameras-contract-el-paso-texas-city-council/
The Daily Iowan, Coralville city councilors end Flock camera contract, February 25, 2026: https://dailyiowan.com/2026/02/25/coralville-city-councilors-end-flock-camera-contract/
Little Village, Coralville City Council ends Flock contract signed by police chief after backlash, February 2026: https://littlevillagemag.com/flock-alpr-cameras-removed-coralville/
City of Columbia Heights, Flock page: https://www.columbiaheightsmn.gov/police/flock.php
MPR News, Columbia Heights City Council votes to end Flock Safety camera contract, June 9, 2026: https://www.mprnews.org/story/2026/06/09/columbia-heights-city-council-votes-end-flock-safety-camera-contract