Flock Safety Reforms: Why Cosmetic Changes Won’t Fix Mass Surveillance

Flock Safety, an automated license plate reader vendor facing nationwide backlash that has driven scores of towns to cancel or suspend contracts, has rolled out a series of product updates and policy reforms aimed at limiting data retention and reining in police misuse of mass surveillance technology.

Under-the-Hood Analysis: Examining Flock’s 7-Day Retention Shift

According to public disclosures and industry reports, Flock’s newly implemented default configuration forces a retention pruning cycle at the 7-day mark unless an administrative override is triggered.

Technical assessments indicate that extending this window beyond the new 7-day default requires police departments to engage “Evidence Mode,” a state designed to tie storage increments directly to active case numbers. However, historical deployment data shows that Flock has previously charged municipal customers financial premiums for extended data retention capabilities. This economic lever means that cash-strapped municipalities might default to the shorter window, while well-funded departments can simply purchase the extended storage tier, rendering the privacy control a pay-to-play feature rather than an architectural safeguard.

Offense Filtering and Audit Trail Vulnerabilities

Alongside the retention adjustments, Flock introduced two secondary configuration controls: granular offense filtering and enhanced automated auditing tools. Offense filtering is designed to let cities restrict database access so that secondary departments—such as code enforcement or regional task forces—cannot query plates unless investigating violent felonies like murder or robbery. Concurrently, the enhanced audit feature is built to proactively lock out officer accounts that generate anomalous or suspicious search frequencies.

Furthermore, CEO Garrett Langley acknowledged the validity of external critiques during a recent shift in corporate posture. As reported by the BBC, Langley remarked: “Historically, my point of view as a chief executive of a private company was, I don’t know if I should be making these decisions. I don’t know if it’s my job to say how long data should be retained.” Langley added that he now agrees with groups like the American Civil Liberties Union and the Electronic Frontier Foundation that police should require an active case number to search stored records, stating, “They’re right. I think it should be required.”

The Structural Flaw of Vendor-Led Privacy Standards

Despite these concessions—which follow intense public pressure, municipal contract cancellations, and legal challenges such as SIREN and CAIR-CA v. San Jose—fundamental architectural questions remain unanswered. Nothing in Flock’s current deployment model prevents the company from rolling back these optional settings if law enforcement agencies begin defecting en masse to rival ALPR vendors.

True systemic reform requires legislative bodies to enact hard statutory limits on police surveillance rather than depending on voluntary, company-imposed software updates.