Flock CEO Calls for 'Compromise' as Surveillance Company Faces Growing Backlash

Flock Safety CEO Garrett Langley stepped into the public eye this week to call for a national "compromise" on surveillance regulation — a move that arrives as more than 120,000 of the company's cameras now monitor roads across 7,000 cities, and as documented cases of police misuse continue to mount. The Washington Post counted at least 46 instances of officers using the company's license plate reader network to track ex-partners, estranged spouses, or former girlfriends. The backlash has turned bipartisan, and it is not slowing down.

The Claim

Flock Safety's pitch is that it did not invent police misconduct; it merely made existing behavior more visible and therefore more accountable. Langley, appearing on NBC's TODAY program in a segment broadcast August 14, framed the company's surveillance infrastructure as a transparency tool rather than a liability, arguing that the pattern of abuse exposed in press coverage would have happened regardless — Flock just left a paper trail.

To back that framing with action, the company announced a set of protocol changes. The default data retention window was cut from 30 days to 7 days. Officers are now required to enter a case code before accessing footage, creating at least a nominal audit layer. Langley called these changes a meaningful overhaul and used them as evidence that Flock is capable of self-regulating. He also called on state legislatures to pass laws that would criminalize unauthorized officer access — an explicit acknowledgment that the company's own controls are not sufficient.

The broader ask from Langley is a federal framework: clear national rules on who can access automated license plate reader data, under what circumstances, and with what oversight. In his telling, a patchwork of inconsistent state laws is more dangerous than a unified standard, and Flock is willing to operate under that standard if legislators can agree on one.

What We See

The ACLU's public response — that the changes "may be a step in the right direction" — is about as qualified as a positive statement can be, and that hedging is warranted. The 7-day default is meaningfully shorter than 30 days, but both the retention window and the case-code requirement can be overridden through what Flock calls "Evidence Mode." That single escape hatch substantially weakens the headline changes. A configurable safety default that operators can silently bypass does not provide real privacy protection; it provides the appearance of one while leaving the liability question open.

Our read is that the "Evidence Mode" override is the most important detail in this story, and it is the one most likely to get buried under the CEO's more quotable calls for compromise. The design pattern here — a restrictive default that can be unlocked without meaningful friction — is familiar from the broader history of platform safety features. When the unlock mechanism is easy and audits are retroactive, the default setting becomes a policy statement rather than an operational constraint. Multiple reports on the announcement focused on the 7-day retention number without examining whether that number actually governs anything when a department opts into Evidence Mode.

The scale of the Flock network makes this more urgent than a niche privacy debate. The Today.com report on Langley's appearance noted that more than 120,000 cameras are already deployed. A company operating at that footprint, woven into the infrastructure of 7,000 cities, is not a startup making early mistakes — it is critical infrastructure, and the governance model needs to match that reality. Calling for a federal "compromise" sounds reasonable in the abstract, but what Flock is actually asking for is a legislative process that takes time, while the existing network keeps running under today's rules.

Where It Falls Short

The bipartisan coalition forming against Flock is worth watching carefully, because it does not fit a simple political narrative. Senator Bernie Sanders and Michigan Democratic Senate candidate Abdul El-Sayed are on one side; three House Republicans co-sponsoring a bill that would ban federal purchase of automated surveillance systems using facial recognition, biometrics, or license plate readers — naming Flock cameras specifically — are on the other. When the opposition spans that range, it signals that the objections are not primarily ideological. They are procedural and structural: who controls the data, who audits access, and what happens when an officer goes rogue.

The ACLU's stated preference is a 48-hour maximum retention window, not the 7-day default Flock announced. That gap — 48 hours versus 7 days versus the pre-change 30 days — illustrates how far apart the company and its critics remain on the core question of what "protective" retention actually looks like. Fox News reported on the CEO's public appearances and the sabotage incidents directed at Flock cameras, framing the controversy partly around the "public revolt" angle. That framing, accurate as a description of the temperature of the debate, risks obscuring the more specific issue: the 46 documented misuse cases represent individual officers weaponizing institutional access for personal ends, which is exactly the category of harm that Flock's new audit controls were supposed to prevent — and which Evidence Mode can still make possible.

What remains unanswered is the enforcement mechanism. Langley wants states to criminalize unauthorized access. That is a reasonable legislative goal, but it is reactive — it punishes misuse after it occurs rather than preventing it at the system level. The gap between what Flock's new defaults promise and what the Evidence Mode override permits is the gap between accountability theater and accountability infrastructure. Developers and city procurement officers considering contracts with any surveillance vendor should take note: the default setting that appears in the press release is not necessarily the setting their deployment will run on.

Sources