Documented Incident

Company NewsPolice MisusePrivacyAudits

Flock makes audit tools and search justifications mandatory, cuts default data retention to 7 days

Flock announced on Thursday, August 13, 2026, that it will require all law enforcement customers to enable its "Audit Assistance" tool by the end of the year, which flags unusual search patterns and locks users out pending an administrator review. The company will also mandate that officers enter a case number to justify each search, with exceptions for what it calls genuine emergencies that are automatically flagged. Flock says it is reducing its standard data retention period from 30 days to seven, though agencies can adjust it under state or local policy, and is adding an "evidence mode" for longer preservation tied to a case number. CEO Garrett Langley told CNN the changes were prompted by his conversations about public distrust of police, and said he would like state regulators to require audits and stiffer penalties for abuse across all police technology.

Why this matters

The changes shift several oversight features from optional to mandatory across Flock's customer base, which could set a baseline for how ALPR searches are logged and reviewed nationwide. They also arrive as some cities have cancelled Flock contracts, making the adequacy of vendor-imposed guardrails versus binding local or state rules a live question for communities weighing deployments.

Key facts

Sources

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

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.