Privacy Fight Forces LAPD to Drop Flock Cameras for Now

Los Angeles Police Department has stopped using Flock cameras, turning a contract expiration into a test case for how cities govern police surveillance data. The immediate pressure lands on city buyers, police technology vendors, and residents whose routine driving can be captured by automated license plate readers.

The LAPD’s three-year deal with Flock Safety, signed in July 2023, expired over the weekend and was not renewed because of data privacy concerns, according to Engadget. Flock operates 138 cameras in LA, used to check vehicle license plates tied to stolen cars or vehicles registered to fugitives.

This is not a routine procurement pause. It signals that privacy terms are now core infrastructure, not legal boilerplate attached after deployment.

LAPD buyers are treating Flock cameras as a data-control problem

The central issue is not whether Flock cameras can help police find vehicles. LAPD officials acknowledge the system is used for that purpose. The dispute is over what happens after the plate is read, who controls the resulting data, and which agencies can access it.

Dean Gialamas, LAPD’s chief information officer, put the concern plainly:

“The sticking point is around having very clear terms about who owns the data, what happens with the data once they collect it,” Gialamas told the Los Angeles Times.

He said the LAPD would stop using Flock “until we can get those data, privacy, security and sharing concerns ironed out through a contractual relationship.”

That sentence is the heart of the story. The LAPD did not say license plate readers are useless. It said the contract did not resolve enough questions around data ownership, privacy, security, and sharing.

The operative question for city procurement teams: if a surveillance tool works, but the city cannot fully govern the data, is it still acceptable to deploy?

Flock’s model gives police speed, but it also creates searchable location records

Flock Safety cameras are pole-mounted systems that scan license plates. In Los Angeles, the stated use is to help authorities track vehicles reported stolen or registered to known fugitives, according to the Los Angeles Times.

That makes the tool attractive to police. It can compress a manual search into a database query. But the same feature creates the privacy problem. A plate read is not just a snapshot. In aggregate, repeated reads can become a searchable record of vehicle movement.

XOOMAR analysis: this is why license plate readers trigger a different privacy debate than ordinary street cameras. The concern is not only image capture. It is database structure, access permission, retention, auditability, and secondary use.

The sources do not specify Los Angeles’ Flock retention period, hit rates, warrant thresholds, or contract value. That matters. Those missing numbers are not trivia. They determine whether the system is a narrow investigative aid or a long-lived location archive.

For readers tracking the broader data-governance problem, XOOMAR has also covered exposure risk in Customer Records Stolen in Lidl Data Breach Across Europe and the cybersecurity side of AI tooling in Three GPT-5.6 Models Thrust OpenAI Into Cybersecurity. The common thread is access control. Who can see sensitive data, and under what rules?

The Los Angeles numbers show Flock is only one layer of a bigger ALPR system

The Flock dispute sits inside a larger LAPD automatic license plate reader setup. A report from LAPD Inspector General Matthew Barragan, cited by the Los Angeles Times, said the department’s ALPR system includes:

That scale changes the contract debate. If Flock cameras go dark, Los Angeles still has other license plate reader infrastructure. The issue is governance across vendors and systems, not one brand name.

The inspector general recommended pausing new ALPR deployments and new contracts until stronger rules exist. The report said:

“Contracts or agreements shall establish enforceable requirements governing data security, privacy, access controls, retention and auditing to protect Department ALPR data and ensure accountability for its collection, use and disclosure.”

That is unusually direct language for a surveillance audit. It names the weak points: data security, privacy, access controls, retention, auditing, use, and disclosure.

One question now hangs over every ALPR contract in Los Angeles: can the city prove that each vendor follows enforceable rules, or is oversight split across informal arrangements?

Residents, privacy advocates, police boosters, and Flock are pulling in different directions

Los Angeles is not dealing with a single constituency. It is dealing with at least four.

Flock has rejected the premise that the LAPD pause reflects a real flaw in its system. A spokesperson called the decision a “surprise” and said:

“We are confident that through ongoing discussions with LAPD, we can clear up the current misconceptions that led to today’s disappointing pause,” the spokesperson said. “We hope to resume our successful partnership with the department soon.”

Flock has said it contracts with roughly 5,000 law enforcement agencies nationwide, according to the Los Angeles Times. TechCrunch reported that Flock has a network of at least 80,000 cameras around the U.S.

That scale explains why the Los Angeles decision will be watched outside California. If a city as large as Los Angeles demands tougher terms, smaller jurisdictions may face pressure to show whether their contracts answer the same questions.

Other ALPR vendors now inherit the same scrutiny

The LAPD inspector general report said three vendors, including Flock, provide technology and related services. It also said the department does not have formal contracts or agreements in place for all services to address ALPR data-security, privacy, and access-control requirements.

That detail broadens the story. Other ALPR vendors cannot treat Flock’s problem as isolated. If Los Angeles applies the audit’s logic consistently, every provider may need to answer the same checklist.

XOOMAR analysis: the contract standard is moving from “does the camera work?” to “can the vendor prove controlled access, deletion, audit logs, and limits on disclosure?” That shift is expensive in operational terms, even if no contract value is available in the sources. It requires legal language, technical controls, and oversight procedures that survive beyond a sales pitch.

The sharpest pressure point is federal sharing. Flock has reportedly shared data with state and federal authorities, including U.S. Immigration and Customs Enforcement, even though California has legislation restricting what details companies can share with government officials, according to Engadget. Flock says its technology complies with California law, according to the Los Angeles Times.

So the practical question for competing vendors is simple: can they prove compliance before a controversy forces a pause?

Mountain View shows how a pause can become a termination

Los Angeles is not the only city where Flock has run into resistance. In Mountain View, California, officials turned off 30 Flock cameras in February after federal and state law enforcement agencies accessed city data in violation of city policies, according to the Los Angeles Times. Weeks later, the Mountain View City Council voted to terminate its contract with Flock.

That sequence matters. First came access concerns. Then a shutdown. Then contract termination.

Los Angeles has not gone that far, based on the supplied sources. Its contract expired, and officials are seeking stronger protections. The city attorney’s office had previously been working on a new contract, though the current status is unclear.

Flock cameras also face cybersecurity scrutiny. Engadget notes that the company’s cameras have been exposed as having multiple cybersecurity flaws. TechCrunch reported that Flock has faced security lapses exposing cameras and data, and that lawmakers urged federal consumer authorities to investigate concerns including police user logins not protected with multi-factor authentication.

For residents, this moves the issue beyond abstract privacy. A poorly governed surveillance system can fail through policy drift, unauthorized access, or weak security.

The next fight is not one LAPD contract, it is network access

Los Angeles has shown that a surveillance contract can be stopped when privacy, security, and sharing terms are not strong enough. But durable protection will require rules that outlast one department, one vendor, and one budget cycle.

The next phase will likely center on regional access. Flock’s value to law enforcement comes from searchable networks, not just local camera counts. That means the real governance problem is who can query the data across jurisdictions, under what approval standard, and with what audit trail.

Evidence that would strengthen the LAPD’s position includes a new contract with enforceable limits on ownership, retention, access controls, auditing, deletion, and third-party sharing. Evidence that would weaken it would be a quiet restart without public terms, or continued ALPR expansion before the inspector general’s recommendations are addressed.

For cities buying Flock cameras or similar police technology, the lesson is blunt: privacy controls are no longer optional paperwork. They are the product.

Impact Analysis

• LAPD’s decision shows police surveillance contracts are increasingly being judged on data privacy and control, not just effectiveness.
• The expired Flock deal could influence how other cities negotiate ownership, sharing, and retention terms for license plate data.
• Residents may see fewer automated plate scans by LAPD while the city resolves concerns over who can access driving-related data.