Flock Makes Its Audit Feature Mandatory After 50 Officers Were Charged With Misusing It

Flock Safety said Thursday that every customer will be required to adopt its "Audit Assistance" feature by the end of the year, and that officers will have to enter a case code tied to an investigation when they run a search ^[1][2][3]. Both controls already existed; the case code requirement has been optional since it shipped in July 2025 ^[3]. The change is a concession that voluntary accountability settings do not get switched on.

The trigger is not subtle. A Washington Post investigation earlier this month found at least 50 law enforcement officers have been charged with misusing Flock's tools ^[6]. This week alone, a police officer in New Bedford, Massachusetts was accused in court of using the technology to stalk an ex-girlfriend, and three sheriff's deputies in Georgia were arrested on similar allegations ^[4][5].

Audit Assistance works by tracking abnormal activity inside a department and flagging it for review, and under the new policy an account will be automatically suspended while that review runs ^[1][2]. That is a real consequence, and it is the most interesting line in the announcement, because suspension does not require a supervisor to care. It also arrives after the fact. Flagging anomalies is detection, not prevention, and the stalking cases that prompted this were discovered by courts and prosecutors rather than by dashboards.

The case code mandate has a stated exception: it can be bypassed in emergencies ^[3]. Flock also says customers can now scope how their cameras are shared with other agencies, for example permitting a search for a missing person while excluding immigration enforcement ^[8]. The announcement did not explain how an officer would be stopped from lying about the reason for a search ^[9]. Chad Marlow, senior policy counsel at the American Civil Liberties Union, called the package largely a public relations stunt and said several of the measures are "merely retreads of previous inadequate safety measures," writing in a blog post that the search purpose requirement had already failed because users could easily circumvent it ^[10][11]. Marlow did credit one item: a proposal to cut retention of license plate search data from 30 days to seven, except where it is held as evidence ^[12]. Flock, for its part, described the measures as a "continuation of our commitment to both safety and privacy" ^[7].

Scale is the reason any of this matters. Flock was founded in Atlanta a decade ago and now holds contracts with more than 7,000 organizations running roughly 120,000 license plate readers ^[13][14], an average of about 17 cameras per customer ^[15]. Contracts have been cancelled in Los Angeles, Cambridge, Massachusetts, and Eugene, Oregon ^[16].

Watch whether the case code field is validated against an actual case management system or accepted as free text, how often the emergency bypass is invoked, whether the seven-day retention proposal becomes policy, and whether the year-end deadline slips for large accounts.