How Flock Safety's New Terms Complicate Municipal Contract Exit

The hard part of a Flock Safety contract may not be approving the cameras. It may be getting out after a council changes direction, a police department loses political backing, a state-law question surfaces, or the public asks what happens to license plate data after the notice of termination goes out.

That is no longer a theoretical procurement concern. Military.com reported on July 14, 2026, citing San Francisco Standard reporting, that 82 Flock contracts had been terminated across 28 states, including 39 in the first five months of 2026.[1] NPR had reported earlier that more than 30 localities had canceled Flock contracts since 2025 amid concerns about immigration surveillance and data sharing.[2] Those figures should be used carefully; the 82-contract number depends on reporting cited by Military.com, not a termination database independently reviewed here. Still, the pattern is enough to make one contract question unavoidable: when a municipality decides to leave, what exactly can it stop?

For municipal counsel reviewing a new Flock agreement or a renewal in Q3 2026, the answer turns less on the public-facing debate over automated license plate readers than on the standard Terms & Conditions. The ACLU’s April 2026 comparison of Flock’s terms identifies four changes in the February 16, 2026 version that matter directly to exit rights: removal of prior no-data-sale language, an irrevocable perpetual license to customer data that survives termination, Flock’s exclusive control over the format and timing of data access, and broader liability protections for Flock.[3] Flock’s current public Terms & Conditions remain the operative baseline counsel should check against any order form, addendum, or agency-specific amendment before signature.[4]

Termination Is Only Useful If It Ends the Right Things

A municipal termination clause is often treated as a calendar provision: give notice, wait out the period, stop paying invoices. That is an incomplete view when the contract concerns a data system used by law enforcement. The practical exit question is whether termination stops future collection, ends vendor use of municipal data, gives the city a usable copy of records, allows verification or deletion, preserves public-records and audit obligations, and leaves disputes in a forum the municipality can realistically use.

This is where boilerplate becomes substantive law for the city. A council can vote to discontinue cameras and still leave staff to untangle archived reads, system access, evidence needs, retention schedules, pending subpoenas, insurance questions, indemnity demands, and a dispute clause pointing somewhere outside the municipality’s usual litigation path. If those issues were not negotiated before signature, the exit becomes a request to the vendor rather than an exercise of municipal control.

Flock’s product may still be operationally valuable to a police department. Some municipalities may conclude that license plate reader coverage helps investigations enough to justify the program. That decision, however, does not answer the contracting issue. Public-safety utility is not a reason to accept unexamined post-termination rights, especially where the revised terms appear to preserve vendor leverage after the municipality’s political mandate has expired.

The No-Sale Language Changed, but the Legal Point Is Assurance

The first change needs precision. The ACLU reports that Flock removed earlier language stating that it would not sell customer data.[3] That removal does not prove that Flock is selling municipal license plate data. It does not establish a past sale, a current sale, or a planned sale. The contract problem is narrower and still important: a clear promise that once allocated risk to the vendor was taken out of the standard terms.

For a city attorney, the difference is not semantic. Express no-sale language gives the municipality a clean contractual hook if a dispute later arises over monetization, transfer, or secondary use. Without it, the city may have to rely on other provisions, statutory limits, privacy representations, procurement materials, or vendor assurances. Those may help, but they are harder to administer than a direct prohibition.

This matters most at renewal or termination. A city leaving the system will want to know not only whether cameras come down, but whether data generated during the contract can be used in ways the city did not affirmatively approve. If the municipality wants no-sale protection, it should be restored expressly in the contract and tied to customer data, derived data where appropriate, post-termination survival, subcontractors, affiliates, and any data products that could be argued to fall outside the narrowest definition of customer data.

A Perpetual Data License Can Make Exit Feel Incomplete

The most consequential change for termination is the reported addition of an irrevocable, perpetual license allowing Flock to use customer data, with that license surviving termination.[3] In ordinary contract review, survival clauses can be easy to skim because many are routine: confidentiality, payment obligations, dispute provisions, limitations of liability. A perpetual data license is different. It can preserve the vendor’s rights in the very subject matter the municipality thought it was withdrawing from the platform.

The legal effect depends on the exact wording in the executed agreement, including definitions of customer data, de-identified data, aggregated data, usage data, service data, and retained copies. But the practical issue is straightforward. If the city terminates because elected officials no longer support the deployment, because a state-law issue has been raised, or because the public was told the program is ending, a surviving license may still permit vendor-side use of data collected while the contract was active.

That does not mean every surviving license is unacceptable. Vendors often need limited survival rights to provide transition assistance, comply with legal obligations, maintain security logs, defend claims, or preserve evidence subject to lawful process. The problem is breadth. An irrevocable and perpetual license should not be accepted as administrative boilerplate when the customer is a public entity handling law-enforcement data. Counsel should ask why the license must be irrevocable, why it must be perpetual, what uses continue after termination, whether the license is limited to providing services during the term, and whether any retained data must be deleted or rendered inaccessible after a defined period.

The survival issue also affects public accountability. A city can hold a meeting, announce termination, and stop future camera use. But if the vendor retains a continuing license that is broader than the city intended, residents may reasonably ask whether the municipal action changed data rights or merely stopped new collection. A well-drafted termination provision should answer that question before the controversy arrives.

Control Over Data Access Is Control Over the Exit

The second major termination problem is operational rather than abstract. The ACLU reports that Flock’s February 2026 terms give Flock exclusive control over the format and timing of customer access to data.[3] For a municipality, that can determine whether the city can actually retrieve, audit, migrate, or verify records after notice is given.

Data access provisions rarely draw the same attention as camera locations or retention periods, but they are where staff feel the contract most acutely. The city may need records for pending investigations, litigation holds, public-records requests, internal audits, state-law compliance reviews, insurance claims, or responses to a legislative inquiry. If the vendor controls when data is produced, in what format, and under what process, the city’s legal obligations can remain with the city while the practical ability to perform them sits elsewhere.

The format question is not a technical nicety. A searchable export with metadata, access logs, timestamps, user activity, retention information, and chain-of-custody fields is different from a limited download or a report generated on the vendor’s schedule. A municipality trying to evaluate compliance with state law or respond to a records request may need more than images or isolated hit reports. It may need evidence of who accessed what, when, under which sharing setting, and whether any downstream access occurred.

Counsel should therefore treat post-termination access as a core deal term. The contract should specify export rights, timing, format, metadata, audit logs, deletion certification, transition assistance, fees, and escalation procedures. It should also preserve the municipality’s ability to meet public-records, evidence, and audit duties without depending on discretionary vendor cooperation. If Flock remains the only party that can decide the mechanics of access, the city’s termination right is materially weaker than it appears on the signature page.

Liability Protections Move the Cost of a Bad Exit

The ACLU also identifies expanded liability protections in the February 2026 terms.[3] This part of the review should stay tied to exposure, not drift into a generic dislike of limitation clauses. Vendors will ask for liability caps, exclusions of consequential damages, warranty disclaimers, and indemnity limits. Municipalities accept some of those provisions every day. The issue is whether the allocation still makes sense when the vendor operates a law-enforcement data platform and the municipality may be named in claims arising from access, sharing, retention, or statutory compliance.

A city can be the public face of the program even when the vendor designed the platform, drafted the standard terms, controls certain data mechanics, and limits its own exposure. If a lawsuit or administrative claim follows, the municipality may bear defense costs, political costs, staff time, public-records burdens, and possible statutory exposure. A broad limitation of vendor liability can leave the city paying for a risk it did not fully control.

This is why liability review should be connected to the specific functions Flock performs. Counsel should compare the cap and exclusions against data misuse, unauthorized access, statutory violations, confidentiality breaches, public-records failures caused by vendor delay, security incidents, intellectual property claims, and claims arising from vendor representations. If the agreement gives Flock continuing rights in data and control over access mechanics, the liability provisions should not simultaneously make meaningful recovery unavailable for failures in those same areas.

Santa Cruz Shows Why Timing of the Terms Matters

Santa Cruz is useful because it moves the discussion out of abstraction. KQED reported that Santa Cruz terminated its Flock contract with 30-day notice on January 13, 2026, citing alleged violations of California SB 34.[5] Whatever one thinks of the underlying policy debate, the contract lesson is plain: the city had a path to send notice and end the relationship on a relatively short timetable before the February 2026 terms became the central issue in public analysis.

That older experience should not be treated as proof that all future exits will be equally clean. A city reviewing a renewal after February 2026 should not assume that a prior 30-day termination story answers questions about surviving data licenses, post-termination data access, liability caps, governing law, or arbitration. The notice period is only one part of exit. The remaining rights may determine whether the municipality can verify what happened, control what remains, and defend the decision afterward.

Santa Cruz also illustrates the pressure placed on the city attorney or procurement officer who inherits momentum. By the time a termination controversy reaches a public meeting, elected officials may be debating immigration enforcement, crime prevention, or state-law compliance. Staff still need to know what the signed contract allows: whether notice is enough, who controls data exports, what survives, and where a dispute must be brought.

Statutory and Litigation Risk Should Inform the Redlines

The California litigation context does not prove that every municipality using Flock faces the same claim. It does show why exit mechanics deserve attention before a controversy matures. Courthouse News reported that a California class action, Gibbs Mura, was filed on February 27, 2026, alleging violations connected to sharing data with federal and out-of-state agencies and seeking damages under California Civil Code section 1798.90.54, which the report described as carrying a minimum of $2,500 per violation.[6] That is a risk signal, not a universal liability conclusion.

For counsel outside California, the lesson is not to import SB 34 wholesale into another jurisdiction. The lesson is to map the contract against the municipality’s own statutory environment: public-records law, criminal discovery duties, data retention law, privacy statutes, procurement rules, home-rule limits, insurance requirements, and any state restrictions on license plate reader data. A standard vendor form may not be built around those obligations.

Vendor assurances should also be checked against written terms. The ACLU has separately argued that Flock made misleading statements to city councils, police departments, and the public in multiple settings.[7] That source is advocacy, and counsel should distinguish its framing from the actual contract text. But the practical point remains fair: if a representation matters to the municipality’s approval, it belongs in the agreement, not only in a slide deck, council answer, email, or frequently asked question.

The Forum Clause Belongs in the Exit Analysis

The ACLU’s analysis also notes that Flock’s terms use Georgia law and mandatory arbitration in Section 13.[3] That matters because termination disputes are not always about whether the city can stop paying. They can involve emergency access to data, deletion verification, indemnity tenders, public-records deadlines, litigation holds, or disputes over what rights survived. A municipality should know before signature whether those disputes will be heard under Georgia law, in arbitration, and under procedures compatible with public-entity obligations.

Some local governments have charter, ordinance, or state-law limits on arbitration, venue, indemnification, choice of law, confidentiality, or waiver of jury trial. Others may have policies requiring disputes to be heard in state court or within the jurisdiction. If those rules exist, they should be reconciled with the Flock terms before execution. Waiting until termination turns a procurement defect into a dispute-management problem.

Redlines to Put on the Table Before Signing or Renewing

Termination review should start before the contract is signed. Once the cameras are installed and the agency is using the platform, the city’s leverage is different. The cleanest negotiation posture is to treat the following provisions as business terms requiring affirmative approval, not as back-office language to be accepted with the order form.

• Restore express no-sale language. The agreement should state that Flock will not sell municipal customer data, and it should define the covered data categories clearly enough to avoid an argument that derived, aggregated, or related datasets fall outside the promise.
• Limit or delete the irrevocable perpetual license. Any survival right should be tied to identified purposes, such as legal compliance, transition, security, or claim defense, and should include deletion or de-identification obligations where legally available.
• Specify post-termination data access. The contract should require timely exports in usable formats, including necessary metadata and logs, and should identify who pays for transition assistance.
• Preserve audit, public-records, and evidentiary needs. The city should be able to verify access, sharing, retention, deletion, and user activity without depending entirely on discretionary vendor-generated summaries.
• Revisit liability caps, exclusions, and indemnity. The allocation should match the vendor’s control over platform design, data access, security, representations, and post-termination handling.
• Address Georgia law and mandatory arbitration. Municipal counsel should confirm whether those provisions are legally permissible for the public entity and workable for urgent data, records, or indemnity disputes.

None of these redlines requires a city to reject license plate readers as a matter of policy. They require the municipality to decide what control it needs if the policy judgment changes. That is the part too often missed when procurement follows operational enthusiasm. The contract should not make the city’s exit depend on vendor grace, especially where the city remains accountable to residents, courts, auditors, and state law.

Termination is not merely the right to send a notice letter. For a municipal Flock contract, it is the ability to stop future use, define what happens to existing data, recover and verify records, avoid residual exposure, and resolve disputes in a forum the city can actually use.

References

1. Flock Surveillance Cameras Face Another Blow as LAPD Won't Renew Contract, Military.com, July 14, 2026.
2. Flock contracts canceled over immigration surveillance concerns, NPR, February 17, 2026.
3. Municipalities: Beware of Changes in Flock's Legal Terms if You're Using or Considering License Plate Readers, ACLU, April 2026.
4. Terms and Conditions - Flock Safety, Flock Safety.
5. Santa Cruz the First in California to Terminate Its Contract With Flock Safety, KQED.
6. California Drivers Accuse Flock Safety of Sharing Data With Federal and Out-of-State Agencies, Courthouse News, February 27, 2026.
7. Flock Safety Credibility Lost as it Repeatedly Lies to City Councils, Police Departments, and Public Across the Country, ACLU.