Data report · August 2026 · Public Square Analytics

How Local Governments Are Talking About Flock Cameras

A year ago, when a city posted about its license plate readers, the post was usually a solved car theft. Today it is just as likely to be a council work session, a transparency portal, a myth-vs-fact graphic — or an announcement that the cameras are coming down. We tracked the conversation across 257 public Facebook posts from 165 city and county governments in 38 states, September 2025 through July 2026. The volume grew 14× over those ten months. And no topic we have measured — not data centers, not elections, not tax reappraisals — draws argument the way this one does.

In this report: The surge · What the posts are · The most contested topic we measure · The removal wave · Both sides of the podium · What communicators can take from this · How we measured this

The surge

Flock Safety’s automated license plate readers (ALPRs) sit in thousands of American communities, and for most of their history the official social-media record of them was quiet: an installation announcement, then the occasional recovered vehicle. That changed over this window. National reporting through the spring of 2026 — on audit logs showing out-of-state and federal lookups of local camera data, and on a wave of contract cancellations — turned a procurement item into a public question, and you can watch it arrive on government Facebook pages in real time.

Two things are true at once in that chart. The conversation grew from 4 posts to 58 per month — and its composition barely moved. Governance content (meeting notices, policy discussions, transparency explainers, removal announcements) has been the majority in nearly every month. The common intuition that government pages mostly use these cameras for we-caught-the-suspect content is simply not what the record shows: crime-case results are 18% of the conversation; process and policy are 62%.

What the posts are

The biggest single category is the least dramatic: 64 posts putting Flock or ALPR on a council or commission agenda — work sessions in Fort Collins, study sessions in Greenwood, workshops in South Portland. These are procedural posts and they earn procedural engagement (1.1× page norm) — until residents show up in the comments, which they do more than for any other agenda subject we track: 41% of council-process Flock posts with any recorded comments end up with more comments than likes.

The category that detonates is privacy and data sharing — 47 posts from 38 governments addressing who can query the cameras, how long data is retained, and what happens to it across state lines. Median engagement: 5.0× the page’s normal post. More than a third draw 25+ comments. This is where the national story lands locally, and residents treat it as the main event.

The most contested topic we measure

We benchmark contested-ness two ways: the share of posts drawing a substantial comment thread (25+), and the share that get ratioed — more comments than likes, the signature of an audience that wants to argue rather than approve.

Our June report found data centers were the most comment-heavy subject in local government, with 25.4% of posts drawing 25+ comments. Flock privacy posts beat that at 35.1% — and where a typical government post has a 1.9% chance of being ratioed, a Flock privacy post is ratioed one time in three. Nothing else we have measured comes close. The nearest comparison in our own work is rumor corrections, which get ratioed 5–9% of the time.

The single most extreme example in the dataset is Independence, Kentucky. In late July the city posted a myth-vs-fact carousel — “take a moment out of your busy schedules to learn the truth about flock cameras” — and the live post shows 115 reactions against 1.6K comments: fourteen comments for every like. The city then scheduled a public discussion for August 17 in council chambers. That sequence — explainer post overwhelmed, then a meeting called — is this topic in miniature.

The removal wave

Ten governments in our corpus publicly announced ending, deactivating, or declining to renew their Flock or ALPR programs during the window — and the pace is accelerating: one announcement in late 2025, then five in June and July 2026 alone. In order:

• Hillsborough, NC (Dec): “All Flock Safety cameras contracted by the town have been removed” after commissioners terminated the contract in October.
• Prosser, WA (Jan): press release announcing the city “Deactivates Flock Safety Cameras.”
• Mountain View, CA (Feb): the police chief turned the cameras off “effective immediately,” crediting “feedback we’ve received from concerned residents”; the council then voted unanimously to terminate the contract.
• Port Angeles, WA (Feb): three cameras “turned off and uninstalled” out of “an abundance of caution,” citing the state legislation then moving through Olympia.
• Dane County, WI (Apr): the board amended the budget to remove Flock funding and prohibit further spending, citing “reported and verified abuses of data collected through Flock’s network, including informal data-sharing with federal agencies.”
• Framingham, MA (Jun): chief, mayor and a council subcommittee jointly “made the decision not to renew.”
• South Portland, ME (Jun–Jul): ceased use and data sharing immediately after a council workshop; by June 22, “Flock confirmed all cameras have been removed and there is no active South Portland account.”
• Kaukauna, WI (Jul): “after careful consideration,” did not renew the contract that expired in June.
• Salem, MA (Jul): not renewing and removing the cameras; “insufficient protections for the ALPR data generated by Flock’s systems.”
• Clearwater County, ID (Jul): the sheriff, after “approximately nine months of use,” announced non-renewal.

Washington state deserves its own note: two of the ten are Washington cities, and both posts reference the state’s Driver Privacy Act (SB 6002, signed March 30, 2026), the first comprehensive state ALPR law — a reminder that some of this conversation is being driven from the statehouse, not the council chamber.

Both sides of the podium

The removal wave is real, but it is not the whole story — and a communicator reading only headlines would miss what the rest of the record shows.

What communicators can take from this

1. Expect the ratio, and stop reading it as failure. On this topic, comments outnumbering likes is the normal condition — it happened to the explainers, the removals, and the purchase defenses alike. The metric that matters is whether the thread is informed by your specifics or by their absence.
2. Lead with your own safeguards, not the vendor’s. The clearest contrast in the dataset: League City’s own-voice explainer (what is logged, who audits, what misuse costs) drew a proportionate thread; a link to the vendor’s website drew ten comments per like. Residents are asking what your government does, and only you can answer that.
3. Show the process, not just the verdict. South Portland’s workshop-then-decision-then-confirmation sequence produced one of the calmest comment sections in the dataset. Independence’s explainer-first sequence produced the stormiest — and the city’s pivot to a public meeting is the correction the pattern suggests.
4. State reasons on the way out, credit results on the way in. Salem named exactly why it was leaving and acknowledged what the cameras had done; Huntington’s mayor took questions on why it was buying. Both were received better than same-category posts that announced without explaining.
5. Keep publishing the case results. They are 1.4× content with a 94% applause rate, and they are the concrete half of a debate that otherwise runs abstract. The strongest ones, like Kittitas County’s, put the human witness first and the technology second.
6. Watch your statehouse. Washington’s Driver Privacy Act reshaped two of the ten removals in this dataset. If your state is debating an ALPR bill, the vocabulary of your next council meeting is being written there.

How we measured this

Frequently asked questions