Documented Incident

Company NewsCities RejectingData SharingAuditsCalifornia

Flock announces privacy changes as Bay Area cities diverge on license plate readers

Flock Safety said Thursday it would let individual police departments limit which outside agencies can view their data and would shorten the default data retention period from 30 days to one week, though agencies can adjust those settings. CEO Garrett Langley said the changes had been in development for months and that the company had "a responsibility to do more." The announcement came as Bay Area jurisdictions took sharply different paths: San Jose still runs nearly 500 cameras with tightened rules, while Mountain View, Los Altos Hills, Santa Clara County and El Cerrito have ended or barred Flock use. ACLU senior policy counsel Chad Marlow called shorter retention a positive step but said the local-control features are "good in theory" and unproven, arguing Flock is treating privacy as a public relations problem.

Why this matters

Flock's changes shift key privacy decisions to individual agencies, meaning protections may vary widely from city to city and rest on local policy rather than binding law. The Bay Area's split outcomes show how audits revealing unauthorized federal access have driven some councils to cancel contracts while neighbors expand them.

Key facts

Timeline

Sources

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

More from California

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