Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Surveillance Policy topic
No spam. Unsubscribe anytime.
Heated public debate on Flock surveillance contract leaves council without a final vote
Summary
After the police chief detailed fixes and a contract amendment that would impose penalties for unauthorized data sharing, dozens of residents, business leaders and advocates testified for and against reinstating Flock ALPR, CCTV and drone programs; the council did not take a final vote and will revisit the issue in follow-up agenda items.
The city’s months-long dispute over Flock Safety technologies — automated license-plate readers (ALPR), closed-circuit cameras (CCTV) and a drone-as-first-responder program (DFR) — returned to the Richmond City Council on March 3 for a long, sharply divided hearing that ended without a final council vote.
Police Chief Timothy Simmons opened the presentation by recounting why he disabled the ALPR system in November 2025 after discovering a reciprocal national-lookup feature that made Richmond’s data temporarily accessible beyond its intended closed network. "The moment I found out that was the case, I took immediate action that very day to decide to turn the cameras off," Simmons said, adding that he informed the city manager and council at once.
Chief Simmons described changes Flock made in January 2025 to limit cross-jurisdictional lookups, new guardrails (a documented right-to-know/need-to-know requirement for searches), and an unusual contract amendment negotiated with the company that would allow Richmond to seek penalties of up to $290,000 per unauthorized-access incident. He recommended a short-term transitional contract amendment — through the end of the year — to restore the tools while the city audits use, sends monthly audit reports to the Community Police Review Commission (CPRC), and completes an RFP for future solutions.
Public comment was extensive and sharply divided. Business and merchant groups, the Richmond Police Officers Association and many local residents described crime-fighting benefits that they say Flock provided before November, citing dozens of felony arrests, multiple recovered vehicles and a reported local surge in vehicle thefts since the system was paused. "These cameras are not a luxury. They are a lifeline for an understaffed department," a police sergeant told the council.
Opponents — including immigrant-rights groups, Reimagine Richmond, privacy advocates and many residents — said Flock has a documented national history of data-sharing incidents, hacker exposures, and use by federal agencies in ways that undermine local sanctuary protections and personal privacy. Speakers cited litigation and contract terminations in other jurisdictions and urged the council to terminate or deny renewal of the Flock contract rather than rely on company promises and monetary penalties.
Chief Simmons proposed several accountability steps if the council restored the contract: keep ALPR searches logged and audited monthly by the CPRC, require annual third-party audits delivered to the council, and keep ALPR sharing features disabled unless explicitly authorized and documented. He also noted the city has an active RFP to evaluate alternatives should the council choose to end the Flock relationship.
Council members debated whether to continue deliberations in a special session; a motion to continue the meeting failed and the council ultimately adjourned without taking a final vote on W1. Several council members signaled they want more time to review audit language, contractual penalties and the results of the city RFP process before authorizing any reactivation of ALPR, CCTV, or drone assets.
The chief recommended bringing the item back for reevaluation at a later date; staff also proposed returning with an analysis and the RFP results and to report monthly audits to oversight bodies if the council opts to reinstate systems.
