Flock tightens its license-plate surveillance rules — after the cancellations, not before

A surveillance company does not usually rewrite its own rulebook when the technology is working as intended. Flock Safety spent the better part of a year insisting its automatic license-plate readers were a public-safety tool being misused by a handful of bad actors. Now it concedes the machinery itself needs guardrails, and the tell is not what it changed but why it finally did.

The consensus write-up runs as a reform story: a company that heard the criticism and cleaned house. Read the sequence instead. The cameras did not become more dangerous. The business did. Cities canceled. Legislators drafted bills. Auditors published numbers no vendor wants attached to its name. Only then did the settings move.

The headline change is a shorter memory. By default, Flock will now hold a vehicle’s movement data for seven days instead of thirty, keeping records longer only when an officer attaches a case number. It is also making mandatory an audit tool that flags abnormal searches and locks a user out pending review. That tool already existed; it was simply optional. Officers will have to enter a case-number code to run a search, and communities will be able to block outside agencies from querying their cameras by offense type, which is the mechanism a town would use to refuse immigration-related lookups.

The context Flock would rather you skip is the ledger of consequence. More than fifty agencies or jurisdictions have canceled, suspended, rejected, or switched off their Flock contracts since the start of the year. Republican lawmakers filed at least two bills in July to restrict the technology, a rare bipartisan appetite to regulate a policing vendor. In Los Angeles, the police department let its pilot lapse after an inspector general found the system had falsely flagged 161 vehicles as stolen in two months, roughly a third of its hits wrong. Mountain View pulled the plug after learning its data had been shared with hundreds of agencies it never approved. Chief executive Garrett Langley now says the optional guardrails become mandatory by January, and that jurisdictions will run the system “consistent with community values.” Those values were available all along. What changed was the invoice.

The abuses were never abstract. Some fifty documented instances of officers misusing the network for unauthorized tracking. Six Savannah employees fired over searches involving friends and family. A Georgia police chief arrested for allegedly using the cameras to stalk and harass residents. Around two dozen cases nationwide of officers resigning or facing charges for tracking romantic partners. An audit log records all of it, after it happens. A ledger you read only when a public-records request forces you to is not oversight. It is a receipt.

The deepest problem is one no retention setting reaches. Flock is not a camera. It is a searchable national pool of where people drive, and its most consequential use runs through a side door. Immigration agents hold no contract with the company, yet more than four thousand lookups have been run on their behalf by local police, according to reporting the company has not disputed. An analyst at the federal firearms bureau tapped Richmond’s system for an immigration case. Langley has paused federal pilots before. None of that is a fault in a settings menu. It is the design: pool the data widely enough and someone with a badge will always be able to ask a neighbor to look.

Shortening the memory to a week is real, and the audit lockouts will catch the clumsy. But Flock is converting its own optional features into mandatory ones on a timeline it set, for a network it still owns end to end, while the only actor that could truly bind it — a legislature writing an actual statute — is the one it spent the year hoping to avoid. Flock has learned the price of oversight. It has not yet accepted that it is not the one who gets to set it.

Tags: ALPR, Flock Safety, license plate readers, surveillance, Garrett Langley