Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Surveillance Alpr topic
No spam. Unsubscribe anytime.
Council approves short-term Flock contract amendment direction amid heated debate over data access and sanctuary policy
Summary
After hours of public comment and council deliberation, Richmond directed staff to pursue a mixed approach: continue procurement while negotiating contract amendments with Flock Safety that include unauthorized-sharing remedies and stronger data safeguards; motion passed with several dissenting votes.
The council debated and then voted on how to proceed with the city’s Flock Safety CCTV/ALPR system after a disclosure that a Flock feature had made Richmond license-plate data accessible beyond initially intended boundaries.
RPD Chief Simmons said he had turned Richmond’s Flock system off on Nov. 19 after discovering a two-way "national search" function that allowed outside agencies to query full license plates; he said the feature was cut off and later changes have been made (SEG 1920–1928, SEG 1931–1935). Flock public-affairs manager Lily Hoe told council that customers own their data and that Flock stores it on AWS GovCloud; she said Flock would consult with the city and support legal processes if data requests arise (SEG 1841–1850, SEG 1858–1866).
The meeting drew substantial public comment both supporting cameras as a public-safety tool and opposing Flock over data-sharing and sanctuary-policy concerns. Speakers including residents, privacy advocates and labor representatives described experiences ranging from improved evidence gathering to fear of surveillance and potential federal access; some speakers alleged third-party influence and questioned vendor transparency (numerous public-comment blocks across SEG 1776–2623).
Council considered two competing motions: one to move forward with staff’s recommended contract amendment and RFP path (short-term amendment plus RFP), and an alternative motion to decline renewal and require vendors based in California. The council adopted a motion that directed staff to pursue procurement (RFP) while negotiating contract language with Flock that adds unauthorized-sharing remedies, ownership-clarifying language and other safeguards; the motion passed with Council Members Jimenez, Wilson and Mayor Martinez voting no (SEG 2624–2629).
City staff said the city has make-whole remedies in its draft terms (a per-incident remedy was discussed in the meeting), will examine storage and cloud-ownership options, and will continue the RFP process that closed March 27 for vendors; staff cautioned that replacing an installed system will require time, permitting and installation work (SEG 1919–1927, SEG 1858–1866, SEG 2439–2460).
The vote does not eliminate longer-term policy options; council members urged continued oversight, clarity in contract language about data access and ownership, and expedited procurement to test alternatives.
