How Flock Safety's Three Lawsuit Tracks Create Exposure

Last verified: July 27, 2026. This is a litigation-risk tracker, not legal advice. In a Flock camera privacy lawsuit legal analysis, the first cut is not whether automated license plate readers are lawful in the abstract; it is which exposure track is actually in front of you. A suppression motion, a California statutory-damages demand, and a mistaken-stop claim do not move on the same facts.

The current record separates into three tracks: Fourth Amendment challenges to ALPR collection or querying; California state-law class actions against private deployers and related entities; and product-liability or civil-rights claims after alleged plate misreads and wrongful enforcement encounters. Some surrounding events—undisclosed data sharing, state legislation, procurement reversals, and FTC pressure—do not fit neatly into those tracks, but they change the settlement and renewal environment around them.

The table is deliberately mixed. A city attorney deciding whether to renew a Flock contract cares about Mountain View, Ventura County, El Cajon, Washington, and Oshkosh even if none of those items is the same thing as Bartholomew. A criminal defense lawyer drafting a suppression motion cares about Schmidt, Church, San Jose, and Chatrie even if none supplies a clean nationwide ALPR rule. A plaintiff lawyer evaluating a mistaken-stop claim cares less about database theory and more about the chain from plate read, to officer reliance, to detention, force, or search.

The California damages track is the sharpest multiplier

Bartholomew matters because it is reported as a damages-mechanics case, not merely another privacy objection. Rain Intelligence and Global Privacy Watch describe the California First District as recognizing actionable harm from the absence of a compliant ALPR privacy policy, without requiring a separate showing that the plate data was misused. They also describe the statutory exposure as $2,500 per person per violation, a figure plaintiffs can model at scan or collection scale if the violation attaches to the collection event [5][6].

That distinction changes negotiation posture. A claim that requires proof of downstream misuse usually forces plaintiffs to spend early money identifying who accessed what, why the access was improper, and how the individual plaintiff was harmed. A no-misuse-required theory shifts attention to deployer compliance: whether a private entity had the required policy, whether it was public, whether it contained the required content, and whether the entity collected ALPR information during the noncompliant period. If those facts are common across a class, the damages conversation moves before anyone proves stalking, identity theft, or a bad search.

The caveat is not cosmetic. The Bartholomew opinion text on Justia was inaccessible due to authentication. Before a demand letter quotes the court’s statutory interpretation, or before a defense memo concedes the no-misuse premise, counsel should pull the primary opinion and the review-denial docket. The secondary sources are strong enough to flag exposure; they are not a substitute for exact language when a reserve number is being set.

The follow-on pattern is what makes Bartholomew more than a one-off parking case. Rain Intelligence reports at least four class actions filed within six weeks against Simon Property Group, Flock Group, Sunset Development / Bishop Ranch, and related defendants, plus at least eight additional plaintiff investigations recruiting as of May 2026 [5]. The legal theory may be California-specific, but the business fact pattern is common: private sites adopted ALPR infrastructure for parking, security, or access control, and the statutory question turns on privacy-policy compliance before anyone reaches the usefulness of the cameras.

That is why data-sharing incidents belong near the California class-action file even when they are not the same claim. Mountain View’s reported 600,000 unauthorized searches by more than 250 agencies after nationwide mode was enabled, and Ventura County’s reported 364,000-query vendor-error incident with 299 immigration-enforcement queries, are not Bartholomew holdings. They do, however, put pressure on representations about who can search a network, who approved sharing, and whether the written policy matched operational reality [7].

The El Cajon suit adds a public-enforcement version of the same problem. California Attorney General Rob Bonta filed suit on Oct. 3, 2025 alleging illegal ALPR data sharing with out-of-state agencies [9]. A private Bartholomew-style plaintiff still has to prove the elements of the private statutory claim. But a municipal client defending a renewal will now face the obvious question: if sharing limits are written into the program, who verifies that the software settings and agency permissions actually enforce them?

The Fourth Amendment track is unsettled, and Chatrie does not settle it

The Fourth Amendment cases ask a different question from Bartholomew: not whether a private deployer missed a state-law privacy-policy requirement, but whether government collection or querying of plate-location data is a search, whether a warrant is required, and whether evidence should be suppressed. The consequence is different too. A defendant may care less about statutory damages than about excluding evidence; a city may care less about one suppression ruling than about whether its network design has crossed a constitutional line.

Schmidt is presently the main reported defense-side marker. WHRO reported that Judge Davis ruled on Jan. 27, 2026 that Norfolk’s ALPR system did not violate privacy, while also indicating that ALPR surveillance could reach a future tipping point [1]. That is not the same as a permanent safe harbor. A trial-court ruling on the current record, with an appeal pending in the Fourth Circuit, gives defense counsel language to cabin a suppression analogy. It does not answer how a different network scale, retention period, sharing arrangement, or query practice will look on a fuller record.

Commonwealth v. Church points in a similar direction for law enforcement, but the source posture matters. Flock’s own October 2025 blog says the Virginia Court of Appeals reversed a warrant requirement for ALPR data on Oct. 14, 2025 [2]. The case is still useful for identifying a state appellate ruling favorable to warrantless access. But a vendor blog is not where counsel should stop before telling a prosecutor the issue is safe or telling a city council the constitutional problem is over.

The San Jose litigation presses the opposite direction. NBC News reported on the Institute for Justice lawsuit challenging San Jose’s ALPR network as an unconstitutional surveillance system [3]. Its value is not that it has already produced the controlling ALPR rule; the available materials do not support that. Its value is that plaintiffs are now pleading ALPR networks as systemic dragnet searches rather than isolated database lookups.

Chatrie then enters as an analogy fight. The Record reported that the Supreme Court’s June 29, 2026 decision in Chatrie held, 6-3, that warrantless acquisition of Google Location History data was a Fourth Amendment search [4]. That fact is important for ALPR lawyers because it gives challengers fresh language about database-wide location searching. It does not automatically convert every ALPR query into a Chatrie violation.

Flock’s July 9 response reportedly argues that Chatrie does not control ALPR systems, while IJ attorney Robert Soyfer and Professor Andrew Ferguson have argued that Chatrie’s reasoning has force against ALPR dragnets [2][4]. Those are interpretive positions around a new Supreme Court decision. The next useful holding will turn on record facts: density of cameras, duration of retention, whether officers searched a named plate or mined a database, sharing scope, auditability, and whether the person challenging the search can establish standing and suppression consequences.

Misread claims are smaller on doctrine and harder on operations

The mistaken-enforcement track does not need a grand theory of surveillance to create liability pressure. It needs a bad read, officer reliance, and a concrete injury. Upchurch v. Toledo reportedly settled for $35,000 after an alleged misread contributed to a wrongful encounter involving a police dog mauling; Burkleo v. Atherton reportedly settled for $45,000; Gonzales v. Española also reportedly settled [8]. Those are not class-action multipliers. They are case files a risk manager can understand in one page.

Business Insider’s March 2026 reporting, combined with Institute for Justice documentation, identified more than 12 wrongful enforcement encounters tied to ALPR errors or reliance problems [8]. The same reporting cited an IPVM 2021 test finding about a 10% state-misidentification rate, and noted that Coralville officials described Flock accuracy as “around 90%” before that statement was later disclaimed [8]. Because the IPVM material is paywalled, the exact test design should be checked before anyone treats the percentage as an admissible expert point.

The legal significance is more practical than theoretical. If a policy allows an officer to stop a car based only on an ALPR alert, a single transposed state, stale hotlist entry, or ambiguous plate image can become the first domino in a detention, search, use-of-force event, or arrest. Washington’s SB 6002, effective March 30, 2026, addresses that operational hinge directly by prohibiting stops based solely on an ALPR match [10]. Even outside Washington, that law will be cited in policy debates because it names the failure mode that misread plaintiffs have been litigating.

Procurement and disclosure facts now feed the litigation file

Some of the most damaging facts in a Flock dispute may never appear first in a complaint. They appear in council packets, public-records responses, audit logs, and vendor settings. The Washington public-records ruling reported by EFF matters for that reason: public-records fights can expose deployment details, sharing arrangements, and internal assumptions that later become litigation exhibits [11].

Sen. Wyden’s November 2025 FTC investigation letter and Oshkosh’s April 2026 contract rescission over undisclosed heat-mapping capabilities sit in the same risk environment [12][13]. Neither is a damages award. Neither decides the Fourth Amendment issue. But both make undisclosed capability a legal-management problem: if a feature affects tracking, sharing, heat mapping, or search scope, counsel will want the procurement record to show who knew about it, who approved it, and how the public description matched the product configuration.

This is where company-scale claims should be handled carefully. The available materials note that Flock’s 90,000-to-100,000 camera count comes from the company’s own marketing materials, not an independent audit. That does not make the number useless, but it changes how it should be cited. For constitutional scale, class numerosity, or damages modeling, the better evidence is the deployer’s own camera inventory, scan logs, retention schedule, and sharing-audit export.

Exposure matrix

The practical point is separability. Flock-related risk cannot be priced as one generic privacy lawsuit category. Constitutional admissibility, California statutory liability, and mistaken-enforcement injury each depend on different records, different sources, and different timelines.

References

1. WHRO report on Schmidt v. Norfolk — WHRO, Feb. 11, 2026.
2. Flock Safety blog posts on Commonwealth v. Church and Chatrie — Flock Safety, Oct. 2025 and July 9, 2026.
3. NBC News report on Institute for Justice San Jose ALPR lawsuit — NBC News.
4. The Record analysis of Chatrie v. United States and ALPR implications — The Record, July 2026.
5. Rain Intelligence analysis of Bartholomew v. Parking Concepts and California ALPR class actions — Rain Intelligence, 2026.
6. Global Privacy Watch California ALPR compliance analysis — Global Privacy Watch, June 2026.
7. ACLU reporting on Mountain View and Ventura County ALPR data sharing — ACLU, 2026.
8. Business Insider reporting on Flock ALPR misread incidents and IPVM testing — Business Insider, March 2026.
9. Attorney General Bonta Sues City of El Cajon for Sharing Automated License Plate Reader Data — California Attorney General, Oct. 3, 2025.
10. MRSC summary of Washington SB 6002 — MRSC, April 2026.
11. EFF report on Washington public-records ruling involving ALPR records — Electronic Frontier Foundation, November 2025.
12. Sen. Wyden FTC investigation letter regarding Flock Safety — U.S. Senate, November 2025.
13. Report on Oshkosh, Wisconsin Flock contract rescission — April 2026.