Technology

Flock Safety Cuts 18% of Staff as License Plate Network Faces Privacy Backlash

Martin HollowayPublished 16m ago3 min readBased on 8 sources
Reading level
Flock Safety Cuts 18% of Staff as License Plate Network Faces Privacy Backlash
source:flocksafety.com

Flock Safety is cutting about 270 employees, or 18% of its workforce, with departures set for the end of October under a voluntary separation program. TechCrunch

Reuters first reported the planned cut on October 8, 2026, citing sources who described several hundred jobs going away. Reuters TechCrunch confirmed the scope on October 9 as an across-the-board reduction.

The exits follow a voluntary buyout process. Affected employees will leave at the end of October. Wired had reported that Flock was asking some employees to leave to reduce headcount without mandatory layoffs.

Spokesperson Paris Lewbel said Flock offered current employees a Voluntary Separation Program to position the company for its next phase of growth. Lewbel described the program as voluntary, not a layoff, and that difference is central to how the company describes the move. Chief executive Garrett Langley leads the company. Flock declined to comment when TechCrunch asked whether Langley or other executives took a pay cut as part of the program.

In news reports, the workforce action is linked to backlash over Flock's license plate readers and people-tracking technology. The company has installed more than 100,000 license plate-reading cameras across the U.S. Those cameras photograph plates and record time and location, building a searchable record of vehicle movements. It works a bit like a search engine for cars.

That network has drawn scrutiny from privacy advocates and public agencies. Flock has faced criticism for allowing federal authorities access to its nationwide network of readers and databases. TechCrunch The Los Angeles Police Department allowed its contract with Flock to expire, citing privacy and civil liberties concerns.

Flock gives a different account of its performance. At TED2026, Langley, who is also the founder of Flock Safety, said the company's systems had supported more than 1 million investigations and located more than 10,000 missing persons in 2025. Flock Safety

Federal oversight is also in play. Senator Hawley sent a letter dated August 26, 2026 to Langley asking about Flock Safety's collection, retention, and sharing of data from its technology. U.S. Senate

The broader context here is familiar from past infrastructure shifts. License plate recognition, which turns a plate photo into readable text, centralized storage, and cross-agency search are each well understood on their own. Combined at national scale, run by a private company with shared access for many agencies, they raise a different question about who controls location data.

In my view, the cut matters less as a headcount number than as a sign of where that question hits the business. A company selling cameras plus cloud search and storage can grow fast when local departments buy on their own. Growth gets harder when lawyers, policymakers, and residents review those deals together. Calling the exits voluntary keeps options open. Lost contracts and a Senate inquiry narrow them.

Worth flagging for technology leaders is the buying lesson. A non-renewal like the LAPD decision affects how other buyers judge a vendor, from references to procurement risk to legal review of retention and sharing controls. Questions about data minimization, meaning collecting as little as possible, how long records are kept, who can look them up, and whether data can be passed to federal systems are now the central security and compliance review. With 100,000 cameras, risk grows with the size of the database and the breadth of search, not with any single camera.

The optimistic case here is the one Flock makes. These systems can clear cases and find missing people faster than manual work. A claim of 1 million investigations points to real operational use. If independent checks confirm even part of that use, agencies will keep buying some version of this tool. The design task is to agree on guardrails that make it acceptable. Shorter storage by default, clear permission before sharing, full audit logs, and firm limits on tracking people beyond plates would be a start.