Questions to Ask Before Approving Flock Cameras

The short version

Before approving Flock cameras, a city should ask the same questions it would ask before buying any recurring surveillance system: what problem is this supposed to solve, what exact products are included, how much does it cost over the full term, who can search the data, how long is the data kept, and what happens if the city wants out.

The question list matters because public Flock debates rarely fail on hardware specs. They fail when residents discover late that a camera contract was handled like ordinary purchasing, that sharing settings were unclear, that audit logs were not reviewed, or that renewal language made the program harder to revisit.

A clean approval should leave a public record strong enough that a resident, reporter, auditor, or future councilmember can understand the program without relying on verbal assurances.

1. What exactly is the city buying?

The first question is not whether the city is buying Flock. It is which Flock products, features, and integrations are being approved. A fixed license plate reader pilot is different from a broader public-safety platform that can include video integration, live camera feeds, sound detection, crash detection, drone workflows, or advanced search features.

Cleveland City Council file 1367-2025 shows why this matters. The ordinance title describes a contract with Flock Safety for an integrated technology safety solution, including hardware, maintenance, and technical support for up to three years, with two one-year renewal options. That is a wider decision than a simple camera count.

Before a vote, councilmembers should require the order form, product list, camera count, location policy, integrations, optional modules, and any future expansion path to be posted publicly.

2. What is the full multi-year cost?

Flock deals are often presented as subscriptions, pilots, renewals, or bundled contracts. The headline first-year number can hide the real obligation if the city does not publish the full term cost, renewal pricing, discounts, installation costs, hardware removal terms, and staff time needed to manage records and oversight.

A useful council packet should show total cost by year, total contract value, what products are included, whether discounts expire, whether the city can reduce camera count later, and whether cancellation creates any fees or hardware obligations.

The public should not have to reverse-engineer the price from attachments after the vote. If the contract lasts three years, five years, or auto-renews, the public conversation should cover that whole period.

3. What public process is legally required?

Some states and cities require more than routine procurement for ALPR systems. California's SB 34 framework is the clearest example. It requires a public agency that operates or intends to operate an ALPR system to provide an opportunity for public comment at a regularly scheduled public meeting before implementing the program, along with a written usage and privacy policy.

Even outside California, the principle travels well. ALPR cameras collect searchable vehicle-location records, so approval should happen in public with the contract, policy, and oversight rules available before residents speak.

Coralville, Iowa is the cautionary example. Little Village reported that residents pushed back after a Flock contract signed by the police chief came to public attention, and that the purchase had been treated as routine with no real public discussion about ALPR or Flock before approval.

4. How long is data retained?

Retention is one of the most important policy choices because it defines how long ordinary plate reads remain searchable. Flock's public terms define the retention period as the period that footage and associated metadata are stored by Flock, as specified in the applicable order form.

That means residents need the order form, not just a presentation slide. Troy, Michigan's public Flock order form listed a 30-day retention period. South Pasadena's 2026 debate included public discussion of reducing retention from 30 days to 15 days.

The approval motion should name the retention period, explain who can change it, and require a new public review if the city later wants a longer period.

5. Who can search the data?

A camera program is only as narrow as its access rules. The city should say which employees can use the system, what training is required, whether searches require a case number or written reason, whether supervisors review use, and whether access ends immediately when a user changes roles.

The same question applies to outside agencies. Council should ask whether any federal, out-of-state, regional task force, fusion center, private entity, neighboring agency, or vendor-connected network can search local data. If the answer is no, the city should publish the settings and audit records that prove it.

A policy that says access is limited is not enough by itself. The public needs to know how that limit is enforced inside the software and how violations are found.

6. What do the audit logs show?

Audit logs are the proof layer. Flock says every search is recorded, tied to a user, and reviewable, and that transparency portals can show public-friendly search audit information. That is useful only if the city actually reviews the logs and reports what it finds.

Before approval, council should ask what fields are logged, who reviews them, how often review happens, whether network searches are included, whether audit logs can be exported, and what gets reported publicly without exposing active investigations.

The strongest approval language requires routine internal audit review, a public annual summary, and a clear consequence path when a search violates policy.

7. What happens at renewal?

Renewal rules can turn a controversial pilot into permanent infrastructure. Some order forms use automatic renewal language unless one party gives notice before the term ends. That may be normal software-contract language, but it is a poor fit for surveillance technology if no one calendars a public review.

Council should ask whether the contract auto-renews, who can exercise renewal options, when notice is due, and whether staff must return to council before the next term. The better rule is simple: no renewal without updated cost, use metrics, audit findings, public comments, and a fresh vote.

If the city cannot explain the renewal path in one paragraph, the contract is not ready.

8. What data rights survive termination?

Ending the contract should not leave unanswered questions about data. Council should ask what customer data is deleted, what can be downloaded before deletion, what vendor-owned or derivative data remains, whether anonymized outputs survive termination, and whether the city can audit deletion.

Berkeley's Police Accountability Board flagged vendor data rights and post-termination derivative-data concerns in its 2026 Flock review. That kind of issue is easy to miss if the public debate only covers whether cameras help solve cases.

A city should not approve a contract until residents understand the difference between city-controlled records, vendor platform data, and any data the vendor may retain or use after the contract ends.

9. What public reporting will residents get?

A Flock program should have public reporting that survives staff turnover. Useful reports include camera count, approved locations or location rules, total searches, hotlist alerts, outside-agency searches, audit findings, retention settings, sharing partners, policy violations, and examples of cases where ALPR data materially helped an investigation.

The point is not to publish sensitive case details. The point is to prove the system is being used under the rules the city promised. Without public reporting, residents are asked to trust a system they cannot see.

A council that supports Flock should want this reporting. If the program is working and being used properly, the data should make the case stronger.

The council checklist

Before approving Flock cameras, ask for the order form, master terms, product list, camera count, location policy, total multi-year cost, retention period, user-access rules, search-purpose rules, sharing settings, audit-log process, public reporting plan, renewal calendar, cancellation rights, data-deletion terms, and legal compliance memo.

Then ask one harder question: if a resident files a public-records request six months from now, can the city prove the program matched what council approved.

If the answer is not clearly yes, the vote is early. Flock cameras may be legal and useful in some cities, but approval should come after the guardrails are public, not after residents discover the gaps.

Sources used

Flock Safety, Customer Terms and Conditions: https://www.flocksafety.com/legal/terms-and-conditions

Flock Safety, Privacy, Data & Civil Liberties Policies: https://www.flocksafety.com/trust

Flock Safety, How Flock Builds Transparency into Public Safety Technology: https://www.flocksafety.com/blog/how-flock-builds-transparency-into-public-safety-technology

California Legislature, SB 34 bill text, Automated license plate recognition systems: use of data: https://leginfo.legislature.ca.gov/faces/billNavClient.xhtml?bill_id=201520160SB34

Cleveland City Council, File 1367-2025, ordinance authorizing a contract with Flock Group, Inc. dba Flock Safety: https://cityofcleveland.legistar.com/LegislationDetail.aspx?ID=7714153&GUID=D5D4E9A9-CED2-4198-9998-FCD9349ED5A4&Options=ID%7CText%7CAttachments%7COther%7C&Search=flock

City of Troy, Michigan, City Council agenda item and Flock order form, Bid Waiver: Flock Safety ALPR Camera System, August 18, 2025: https://apps.troymi.gov/Meetings/Meetings/DownloadPDF/6883733

Berkeley Police Accountability Board, Flock Safety vendor concerns and surveillance technology recommendations, March 18, 2026: https://berkeleyca.gov/sites/default/files/2026-03/March%2018,%202026%20PAB%20Recommendations_Surveillance%20Tech.pdf

Little Village, Coralville City Council ends Flock contract signed by police chief after backlash, February 26, 2026: https://littlevillagemag.com/flock-alpr-cameras-removed-coralville/