Berkeley limits Flock expansion

Police surveillance was the whole fight in Berkeley this week — not whether the city uses cameras at all, but how far it lets one vendor spread. On Thursday, May 7, the City Council kept Berkeley’s existing Flock Safety license-plate-reader system alive and rejected, or at least stopped, the bigger expansion tied to the same company. That split decision matters because it preserves a tool police already use while drawing a hard line against turning one contract into a much broader surveillance stack. (dailycal.org) ### What did Berkeley actually approve? The council renewed Berkeley Police Department’s Flock contract for automated license plate readers — the cameras that log passing plates, vehicle details, time, and location. Berkeley’s existing network has 52 of those camera(dailycal.org) is the part the council did not move forward. (dailycal.org) ### Why was the expansion the real flashpoint? Because the debate was never just about plate readers. The proposed package had grown into a roughly $2 million surveillance buildout, with Flock software sitting in the middle of multiple tools. For critics, that chang(dailycal.org)cal and legal ask. (berkeleyside.org) ### What was the legal problem? City attorneys warned that Flock might not be able to comply with Berkeley’s own rules on data security and unauthorized sharing. The leaked memo described exposure to potential liability — including the risk of expensive lawsuits — if the city renewed without resolving those issues. In a sanctuary-city-minded place like Ber(berkeleyside.org)city says it opposes. (dailycal.org) ### Why does Flock’s structure make people nervous? Flock sells itself as a crime-solving platform, not just a camera company. That is useful for police — basically one dashboard that can connect plate readers, fixed cameras, alerts, and outside feeds. But the catch is tha(dailycal.org)rust in how all of that behaves under pressure. (berkeleyside.org) ### Why did outside cities come up in Berkeley? Because Flock’s problems are no longer hypothetical. Appleton, Wisconsin, said this week that it is ending its use of Flock cameras, with Mayor Jake Woodford saying concerns about the integrity of Flock’s underlying system had eroded trust. And in Ohio, fallout from a Dayton-area breach has turned into a broader war(berkeleyside.org)romised benefits and more about whether the vendor can actually honor the limits cities think they bought. (wtmj.com) ### Why keep the plate readers at all? Because police and some city officials argued the existing ALPR network helps solve crimes and find suspects with less labor. Berkeley officials defending renewal framed it as a narrower, already-operating tool rather than a fresh expansion. That narrower framing seems to have carried more weight than the larger package did. The council’s message was basically: continuity, maybe; expansion, not now. (dailycal.org) ### So what changed in one night? Berkeley moved from debating whether to widen Flock’s footprint to drawing a boundary around it. The city did not become anti-camera overnight. It became more skeptical of platform sprawl — especially when legal compliance and vendor trust look shaky. (dailycal.org) ### Bottom line This was a limit-setting vote. Berkeley kept the surveillance tool it already had, but refused to hand Flock a bigger role while basic questions about compliance, control, and trust are still hanging in the air. (dailycal.org)