LAPD Ends Flock Safety Contract Over Privacy Concerns: What It Means for ALPR Developers

The Los Angeles Police Department announced Saturday that it will let its three‑year agreement with Flock Safety lapse. The decision follows statements from the department’s chief information officer that the contract raised “serious concerns” around civil liberties, privacy, and data security. Flock’s network of license‑plate‑reading cameras has been a key source of vehicle data for law‑enforcement agencies across the United States. By pulling the plug, the LAPD joins a growing list of municipalities questioning the unchecked expansion of automated surveillance. For developers who build or integrate ALPR systems, the move signals a shift toward stricter data‑governance expectations.

What happened

The LAPD let its three‑year contract with Flock Safety expire on Saturday, citing “serious concerns” about civil liberties and privacy, according to CIO Dean Gialamas. The department said it needs a new agreement that clearly defines data ownership, storage duration, and sharing limits before any future deployment.

Flock operates a national network of at least 80,000 cameras that scan license plates and create searchable vehicle fingerprints. The company’s service has been used by roughly 5,000 law‑enforcement agencies, and several cities—including Mountain View, CA and South Portland, ME—have already terminated similar agreements over privacy worries.

An LAPD Inspector General audit conducted in late 2025 recommended halting new ALPR deployments until enforceable data‑handling rules are in place, reinforcing the department’s decision to pause the Flock arrangement.

Why it matters

The termination highlights a growing tension between public‑safety technology and constitutional protections. When a high‑profile agency like the LAPD pulls back, it forces other jurisdictions to scrutinize their own data‑retention policies, audit trails, and the legal authority to share information with federal immigration agencies. For developers, the shift means that contracts will increasingly demand explicit privacy clauses, limited data lifespans, and transparent governance structures, or risk losing market access.

How to think about it

When designing or integrating ALPR solutions, adopt a privacy‑by‑design mindset: limit data collection to what is strictly necessary, enforce short retention windows (e.g., 7‑30 days), and encrypt data at rest and in transit. Embed audit logs that record every access request, and provide mechanisms for community oversight or opt‑out where feasible. Contractually, require clear ownership clauses that prevent automatic sharing with federal agencies without a warrant. Finally, build modular systems so that components can be disabled or re‑configured without dismantling the entire deployment.

FAQ