Flock cut retention to seven days and published the number that made 30 indefensible

On August 13, Flock Safety CEO Garrett Langley said the company would cut its default license-plate-reader retention from 30 days to seven, make misuse detection mandatory for every law-enforcement customer, and require a case code on every search by the end of the year ^[1]. In the same announcement he published the sentence that matters to anyone who stores other people's data: "Our analysis shows that over 90% of searches without a full plate are done within a week" ^[2].

Read that as an operator rather than as a civil-liberties question. Flock set the 30-day default nine years ago and says it believed the number struck a balance ^[3]. The network now spans more than 120,000 cameras ^[4]. If over 90% of partial-plate queries land inside seven days, then roughly 23 of every 30 days of retained vehicle-movement data were serving under 10% of that query volume ^[5]. Nobody decided to keep three extra weeks of national movement data. Somebody typed a defensible number into a config in year one and it was never re-tested against usage ^[6].

The distinction worth holding onto is that access controls are probabilistic and deletion is deterministic ^[7]. Sort the announced package by that test. Six of the seven measures are detection, response, or hardening ^[8]. They work: Savannah PD fired six employees this month after finding unauthorized searches through Flock's own voluntary audit feature ^[9]. But only the retention change alters how much data exists to be subpoenaed, breached, exfiltrated through a compromised account, misused by an insider, inherited by an acquirer, or shared with a partner under a policy nobody has written yet ^[10]. Detection keeps working right up until the audit log is the thing that is compromised.

The announcement followed a Washington Post investigation that documented nearly 50 instances of officers charged with or accused of running unauthorized searches ^[11], and the reaction was not warm. The ACLU called the measures retreads of safeguards that were already inadequate, while allowing that a shorter window may be a step in the right direction ^[12]. Robert Frommer of the Institute for Justice told the AP it was "window dressing that doesn't address the fundamental problem," his objection being that police still decide who gets searched, a decision he argues belongs to judges and warrants ^[13]. The Center for Democracy and Technology described it as the same "Just Trust Us" policy with a fresh coat of paint ^[14]. Andrew Guthrie Ferguson of GWU Law called the shifts better than the opposite while asking for sustained democratic engagement and judicial checks ^[15].

Underneath the disagreement is a structural point: the retention number is still a setting on a vendor's dashboard ^[16]. The nearest comparison, the UK's National ANPR Service, runs roughly 12,700 cameras collecting about 60 million reads a day and retains for 12 months, twelve times Flock's old default ^[17][18]. The UK figure sits under the Protection of Freedoms Act 2012 and published national standards; the American one is a product default announced by a vendor, and can be announced differently later ^[19].

The transferable exercise is small. Log your age-at-access distribution for a month before anyone argues about policy ^[20]. If you cannot name the person who chose your retention window and the reason, it is an inheritance, not a decision ^[21].

Watch whether the case-code requirement actually ships by year end ^[1], and whether Flock publishes the age-at-access distribution rather than the headline percentile.