How to Challenge a Flock Camera Contract at City Council

By DeFlock Signs · Last reviewed July 18, 2026

A Flock Safety contract can turn thousands of ordinary trips through your city into searchable records. Yet the decision to buy or renew that system may appear on a council agenda as one more contract, buried between road repairs and routine purchases.

If you want your city to reconsider that decision, showing up angry is not enough. You need to make council members face what they approved, what the contract allows, what safeguards are missing, and what they are willing to put in writing.

That is what this guide will help you do.

For the full research, editable council handouts, a timed three-minute public-comment script, legal analysis, print instructions, and follow-up briefings, open the free Flock Safety ALPR Community Research & Governance Toolkit on GitHub. It was built from one persons experience challenging a Flock expansion at city council, and every document has been redacted so you can adapt it to your own community.

Your first job is to give the council a decision to make

“I don’t like these cameras” may be sincere, but it gives elected officials nothing concrete to act on. A stronger position is:

Do not renew, expand, or extend the Flock Safety contract until the city publicly answers these questions and adopts enforceable safeguards. If the vendor will not accept those safeguards, end the contract.

That demand is specific. It also blocks the easiest response: thanking you for your concern and moving to the next speaker.

Your immediate goal may be a pause rather than same-night cancellation. A pause can prevent new cameras, stop an automatic renewal, force the contract into public view, and create time for records requests and a formal hearing. If the answers reveal that local control is weak, promised safeguards do not exist, or the vendor will not accept meaningful limits, you have built the case for non-renewal or termination.

Start with your city’s record, not a national argument

Council members are most likely to listen when you begin with documents carrying their city’s name.

Before the meeting, locate as many of these as you can:

• The signed Flock Safety contract, order forms, amendments, renewals, and current online terms incorporated into the agreement.
• The agenda, staff report, meeting minutes, and video from the original approval.
• The current camera count and locations, including privately owned cameras connected to the police network.
• The written ALPR policy, if one exists.
• Data-sharing settings and the list of outside agencies with access.
• Audit reports, user-search logs, misuse investigations, and disciplinary procedures.
• Grant applications, funding sources, invoices, and the full cost after any grant expires.
• Performance reports showing how the system has been used and what results officials attribute to it.
• The renewal date, cancellation deadline, auto-renewal language, data-deletion requirements, and equipment-removal terms.

Search the city website, council packet archive, procurement portal, and police transparency page. If the records are not posted, file a public-records request. Ask for electronic copies and use the vendor name, product name, date range, and contract number when you have them.

Do not wait for every record before speaking. An official inability to produce a policy, audit, performance report, or sharing list is itself important. Say plainly: “I requested this document on [date]. The city has not produced it.”

Ask questions that expose who really controls the system

The point is not to fire off a dozen questions and hope someone answers. The point is to establish, on the public record, whether the council can govern the surveillance system it is paying for.

1. What exactly did the council authorize?

Ask for the vote, procurement authority, contract term, total cost, camera count, products, software modules, integrations, and renewal provisions. If the program began as a pilot or was purchased with grant money, ask who authorized it to continue after the pilot or grant period.

Then ask the question officials often skip: Does the contract before the council match the system operating today? A software platform can gain features, integrations, and sharing relationships without a new pole appearing on the street.

2. What information is collected about people who are not suspected of a crime?

Do not accept “it only reads license plates” as a complete answer. Ask which images, vehicle descriptions, time stamps, locations, alerts, notes, exports, and associated records are created. Ask which fields are searchable and whether other Flock products or third-party systems are connected.

The distinction matters: police may search selectively, but the system must first collect observations about ordinary drivers in order to make those searches possible.

3. Who can search the data, and who can receive it?

Ask for the number of active users, permitted purposes, required search justifications, supervisor review, and the process for removing access. Then ask for every outside agency, task force, fusion center, federal partner, regional network, contractor, or integrated platform that can search or receive city data.

For every sharing path, ask:

• Is access continuous or approved one request at a time?
• Can the local department see and audit every outside search?
• Can the recipient copy or retain the data under a different policy?
• Can a vendor setting change expand sharing without a council vote?
• Who is notified if an outside agency violates the city’s rules?

“Sharing is off by default” is not an answer about your city. Ask an accountable official to show the current setting and the written rule that keeps it that way.

4. What does “30-day retention” leave out?

Ask separately about data in the Flock platform, downloaded images, screenshots, alerts, reports, exports, case files, evidence systems, backups, legal holds, and copies received by other agencies.

A dashboard setting is not the same thing as an enforceable city rule. Ask whether the retention limit appears in an ordinance, policy, and contract; who can make an exception; whether deletion is verified; and what happens to every copy when the contract ends.

5. What proof shows that safeguards work?

“We have audits” should lead to five more questions: Who performs them? How often? What is reviewed? What violations were found? Which results are public?

Ask for aggregate numbers covering searches, reasons for searches, alerts, confirmed matches, mistaken alerts, complaints, unauthorized access, sharing violations, and discipline. If officials say those numbers cannot be disclosed, ask them to identify the law or policy that prevents an anonymized public report.

6. What measurable result justifies the cost and the intrusion?

Make the city define success. “Helpful to investigations” is not a performance measure.

Ask for the number of cases in which Flock data was searched, produced a lead, contributed to an arrest, or was material to a conviction. Ask how false alerts and dead-end leads are counted. Compare those results with the full program cost: cameras, subscriptions, connectivity, staff time, training, auditing, records responses, legal review, integrations, maintenance, and removal.

The council should be able to explain what problem the system was purchased to solve, what baseline it uses, and when the public will be told whether the program met that goal.

7. Can the city say no to the vendor?

This is the contract question underneath all the others.

Ask whether Flock can change online terms, platform settings, data practices, integrations, or available features during the contract. Ask whether the city receives notice, whether it can reject a change, and whether rejection allows termination without penalty. Ask who owns exported data, what obligations survive termination, how deletion is certified, and when equipment must be removed.

If city officials cannot explain their exit rights, they are not ready to renew.

Put enforceable demands behind your questions

Questions reveal the problem. A vote changes it.

Ask the council to reject or pause any renewal, expansion, or new feature until it adopts these minimum conditions:

1. A written ALPR policy approved in public.
2. A firm retention limit, with narrow documented exceptions and deletion verification.
3. No routine sharing outside the local department; any exception requires public council approval.
4. No audio sensing or voice-detection features in the public right-of-way.
5. An independent security and privacy assessment before renewal.
6. No vendor-initiated setting or terms change without written city authorization.
7. Public quarterly reports covering searches, purposes, outside agencies, match outcomes, complaints, and violations.
8. No new product, integration, analytics feature, or use case without a council vote.
9. Contract language allowing suspension or termination when the vendor or an outside agency violates these rules.

These are starting points, not a substitute for reviewing your state law and local charter. The toolkit’s council handout shows how to connect each request to evidence. Its deeper research files can help you verify vendor claims and adapt the demands to your city.

Build a packet council members can use

Most public-comment periods are too short to establish every fact. Your written packet carries the argument after your microphone turns off.

Keep the main handout brief. It should include:

• What your city approved and when.
• What the local policy and contract do, or fail to do.
• Three to five well-sourced examples that directly bear on local control, security, sharing, or vendor accountability.
• Your specific requests and the action you want on the next agenda.
• Links or footnotes that let council members verify every important claim.

Do not bury your strongest local fact under twenty national headlines. Do not accuse a local officer of misconduct unless the record supports it. The more disciplined your packet is, the harder it is to dismiss you as merely anti-police or anti-technology.

The GitHub toolkit includes the same materials in Markdown, Word, and PDF. Replace every [REDACTED] placeholder with your local facts, remove claims that do not apply, and re-check every source before distributing it.

Use your three minutes to make one clean argument

Public comment is not a research presentation. It is a request for action.

A simple structure works:

1. Open with the decision. Name the contract, renewal, expansion, or policy the council controls.
2. State the local gap. Identify the missing policy, hidden sharing arrangement, weak contract term, absent audit, or unanswered records request.
3. Give two or three verified facts. Choose facts that show why the gap matters.
4. Make the ask. Pause, reject, place on the agenda, require an independent review, or begin termination.
5. End with a deadline. Ask for action before the renewal date or next contract payment.

Here is a starting point:

Mayor and Council, I am asking you not to renew or expand the city’s Flock Safety contract until the public can see who searches the system, where our data goes, how deletion is verified, and whether the city can reject vendor changes. This is not a request to abandon public safety. It is a request for the council to govern a surveillance contract before paying for more of it. Please place the contract and ALPR policy on a public agenda before [renewal date], require written answers to the questions in my handout, and do not authorize another term unless the safeguards are enforceable.

Practice aloud with a timer. Cut background material before you cut the ask. Bring a printed copy even if you plan to speak from memory. The toolkit’s editable three-minute talk track also includes responses to predictable objections.

Expect the familiar pushback

“Don’t you want police to catch dangerous people?”
Yes. A useful investigative tool should be able to survive a public audit, a written policy, and enforceable contract limits. Effectiveness and accountability are not opposites.

“Our officers only use it for legitimate investigations.”
Then put those permitted uses in writing, audit compliance, and publish aggregate results. Good intentions are not a control that survives staff turnover, software changes, or outside access.

“The data disappears after 30 days.”
Ask whether that rule covers exports, screenshots, case files, backups, legal holds, and data copied by another agency. Ask who verifies deletion and where the obligation appears in the contract.

“There is no evidence of misuse here.”
The council does not have to wait for local harm before adopting safeguards. Contracts, access controls, audits, and termination clauses exist to prevent predictable failures.

“These claims are exaggerated.”
Invite verification. Hand over the sources. Separate what the vendor says, what your city’s records show, and what you are asking the council to decide. A calm answer backed by documents is more persuasive than a louder accusation.

Treat meeting logistics as part of the campaign

Contact the city clerk before the meeting. Confirm the public-comment deadline, time limit, speaker-card process, rules for handouts, and whether written material becomes part of the official record.

Arrive early. Bring one handout for every council member and key staff member, plus a clean copy for the clerk. Keep your script and supporting research with you. The toolkit’s print and distribution guide provides a practical model you can scale to your council.

Bring other residents, but do not have everyone repeat the same speech. Divide the case: one person covers the contract, another data sharing, another performance and cost, another the policy demands. Ask supporters who do not want to speak to submit written comments and attend visibly.

Do not let the issue end when the meeting adjourns

Within a day, send a short follow-up to every council member. Attach the handout, link the sources, restate the action you requested, and list any unanswered questions. Ask when the contract or policy will appear on an agenda.

Then keep a public record:

• The question asked.
• The answer given.
• The official who gave it.
• The supporting document.
• The date.
• What remains unanswered.

If the mayor, police chief, or a council member asks for more information, answer quickly and tailor it to that person’s role. The toolkit includes both a mayor follow-up briefing and a technical briefing for police leadership. Their tone matters: firm about the record, respectful toward the person, and clear about the decision you want.

If officials still refuse to act, keep working the calendar. Track notice and renewal deadlines. Ask a council member to sponsor a hearing or resolution. Organize public comments across multiple meetings. Share records with local reporters and civil-liberties groups. Make it politically harder to renew the contract quietly than to examine it openly.

The council signed the contract. The council can challenge it.

Flock debates are often framed as a choice between safety and privacy. Do not accept that frame. The immediate question is whether a private surveillance vendor should operate in your community without clear limits, public proof of performance, independent review, and a contract your city can actually enforce.

You do not have to become a surveillance-law expert before speaking. You do need local documents, verified facts, a concrete demand, and the persistence to ask again when officials do not answer.

Start with the DeflockYourCity Flock ALPR Toolkit. Download the format you can edit, replace the redactions with your city’s facts, rehearse the talk track, print the packet, and put the contract on the public record.

Then ask your council to choose: meaningful, enforceable control, or no Flock Safety contract.