LA Just Walked Away From The Surveillance Network Tracking 80,000 License Plates Here's Why That Matters

The Los Angeles Police Department, the third-largest police force in the United States, just let its contract expire with a company most Americans have never heard of, but whose cameras have probably photographed their license plate anyway.

The company is Flock Safety. It operates a network of at least 80,000 license plate reading cameras across the country, feeding real-time vehicle tracking data to police departments and federal agencies. On Saturday, LAPD's three-year relationship with Flock officially ended.

The reason, according to LAPD's own chief information officer: "serious concerns around civil liberties and civil rights issues, particularly around privacy and the data that is being collected from these cameras."

That's not a budget dispute. That's not a technical hiccup. That's one of the largest police departments in America saying, in plain language, that a private surveillance company's practices had become too risky to keep using.

Here's what actually led to this moment and why it matters far beyond Los Angeles.

What Flock Actually Does

Flock Safety is an Atlanta-based company that sells automated license plate reader (ALPR) cameras to police departments, homeowners' associations, and businesses. The cameras scan every passing vehicle, log the license plate, timestamp, and location, and feed that data into a searchable network.

Individually, none of that sounds particularly alarming. Cameras photographing public roads are nothing new. What makes Flock different is scale and connectivity. With over 80,000 cameras deployed nationwide, and departments able to share access across jurisdictions, Flock has effectively built a national vehicle-tracking infrastructure that no single government agency has built or directly controls.

A police department in one city can potentially search vehicle movement data captured by cameras in a completely different city or state, depending on data-sharing agreements. That's the feature that made Flock attractive to law enforcement and the same feature that's now triggering a serious alarm.

Why LAPD Actually Pulled The Plug

Dean Gialamas, LAPD's chief information officer, was direct about the department's reasoning: "This contract is not being renewed because of serious concerns around civil liberties and civil rights issues, particularly around privacy and the data that is being collected from these cameras."

He added that LAPD is now seeking new contract language specifically addressing "data, privacy, security, and sharing concerns" before any future relationship with Flock resumes.

That's a notable framing. LAPD isn't saying license plate readers are inherently bad technology. It's saying Flock's specific practices around how data gets collected, stored, and shared no longer meet the department's standards and that the previous three-year contract didn't adequately protect against those risks.

What's still unclear is what happens to the cameras themselves. Flock, not LAPD, owns and operates the physical hardware. A spokesperson didn't respond to requests for comment about whether the cameras will keep recording in Los Angeles despite the expired contract an ambiguity that itself says something about how much control local governments actually have over infrastructure that private surveillance companies install on their behalf.

LA Isn't Alone, And The Pattern Is Growing

LAPD is a significant loss for Flock given its size, but it's not an isolated incident. Mountain View, California, and South Portland, Maine, have both cut ties with the company recently, citing privacy concerns.

South Portland's case is particularly pointed: local officials raised concerns that federal immigration authorities used Flock's cameras to track individuals in ways that potentially violated the city's sanctuary city policies policies specifically designed to limit local cooperation with federal immigration enforcement.

That's the crux of the broader anxiety building around Flock's network: even when a city or police department has its own rules about what surveillance it will conduct and share, Flock's interconnected system creates pathways for other agencies, including federal ones, to access that data anyway.

Flock's Response: "Misconceptions"

Flock spokesperson Holly Beilin told TechCrunch the company was caught by "surprise" by LAPD's decision and expressed confidence that Flock could "clear up the current misconceptions" that led to the contract ending.

Notably, Flock did not specify which misconceptions it meant.

That's a curious non-answer given the sheer volume of documented, specific incidents connected to the company's cameras over the past year, incidents that go well beyond abstract privacy theory into concrete cases of people getting hurt.

The Part That Should Actually Worry You

Here's where this story moves from policy debate into something more visceral: real people have been detained at gunpoint, jailed, and tracked for days because of Flock camera errors.

Researchers tracking these incidents have documented a rising number of cases where motorists were pulled over, detained, or arrested due to false positives generated by license plate readers. Just last week, a journalist from The Drive detailed his own experience being tracked for days and eventually boxed in by police, all because a Flock camera incorrectly flagged the license plate of a review vehicle he was driving as stolen.

Think about what that actually means. A system built to help police find genuinely stolen vehicles or wanted suspects instead generated a false alert, and the response wasn't a follow-up phone call or a quick verification; it was armed police officers physically surrounding a private citizen's car based on an algorithm's mistake.

That's not a hypothetical privacy concern. That's an actual person, driving a car that wasn't stolen, getting treated like a dangerous suspect because software made an error.

The Security Failures Make It Worse

Beyond tracking errors, Flock has faced repeated security lapses that call into question how well the company protects the enormous amount of surveillance data it collects.

In one striking case, independent outlet 404 Media discovered they could access publicly exposed Flock cameras online and used that access to watch themselves, live, through a security camera they had no idea was broadcasting to anyone who found the right URL.

Lawmakers have separately pushed federal consumer protection authorities to investigate Flock for failing to implement basic security measures, warning that many police login credentials used to access the system aren't protected by multi-factor authentication, a baseline security practice that most consumer email accounts now require by default.

That gap became more than theoretical when 404 Media reported that the U.S. Drug Enforcement Administration used a local police officer's login credentials without that officer's knowledge to conduct immigration-related surveillance through Flock's system. A federal agency used someone else's identity to search a surveillance network that the officer may not have even known was accessible in that way.

Communities Are Fighting Back Physically

The backlash to Flock hasn't stayed confined to city council meetings and contract negotiations. Some residents, frustrated after watching their communities approve and then quietly walk back Flock deployments, have started dismantling cameras themselves, including covering them with trash bags to block their view.

In at least one documented case in Evanston, Illinois, Flock reportedly reinstalled cameras without permission from local authorities after they'd been removed, raising uncomfortable questions about who actually controls surveillance infrastructure once it's been installed in a community, and how much power local governments genuinely retain over a private company's hardware sitting on public streets.

Beyond License Plates

Flock's situation is a preview of a much larger tension building across the country: private companies building surveillance infrastructure that outpaces the legal and contractual frameworks meant to govern it.

Cities sign contracts assuming a certain level of control and accountability. But when the underlying technology enables data sharing across jurisdictions, when security gaps allow unauthorized access, and when federal agencies can potentially route around local sanctuary policies through interconnected networks, the actual power dynamic looks very different from what elected officials originally agreed to.

LAPD's decision to let its contract lapse rather than simply renewing it with the same terms suggests city and department officials are starting to recognize that gap and push back on it directly, demanding better contractual protections before resuming a surveillance relationship rather than accepting the existing terms indefinitely.

It remains unclear whether Flock's cameras will keep operating and recording in Los Angeles despite the expired contract, since the company, not LAPD, owns the hardware. That ambiguity alone illustrates the core problem critics have raised: when private companies control surveillance infrastructure embedded throughout public spaces, an expired contract doesn't necessarily mean the surveillance actually stops.

LAPD says it wants new contract language addressing data, privacy, security, and sharing concerns before any renewed relationship with Flock moves forward. Whether Flock is willing or able to meet those demands and how the company defines the "misconceptions" it says led to this outcome will likely determine whether Los Angeles returns to using Flock's network or looks elsewhere entirely.

Meanwhile, more cities are watching. Mountain View and South Portland already walked away. LAPD, as one of Flock's largest government customers, represents a far bigger loss both financially and symbolically, as other major police departments weigh whether the tradeoffs of Flock's tracking capability are still worth the mounting privacy, security, and accountability risks.

Flock Safety built one of the largest vehicle surveillance networks in American history, 80,000-plus cameras, real-time tracking, cross-jurisdiction data sharing, largely without the kind of public debate that typically accompanies infrastructure of that scale.

LAPD's decision to let its contract expire signals that at least some of the largest law enforcement agencies in the country are no longer willing to overlook the mounting evidence: false positives that led to armed police confrontations with innocent drivers, security failures that exposed live camera feeds to the public internet, and federal agencies accessing local surveillance data through means that bypassed the officers who were supposed to control it.

Flock says these are misconceptions. The documented incidents from The Drive journalist boxed in by police over a false stolen-vehicle flag, to the DEA using a stolen police login for immigration surveillance, suggest otherwise.

For now, Los Angeles is stepping back. Whether that becomes a turning point for how America regulates private surveillance infrastructure, or just one contract dispute among thousands of similar deals still quietly renewing across the country, depends entirely on what happens next.