Public Safety Software and Community Trust: What the Flock Backlash Teaches GovTech Founders

Flock Safety went from a quiet line item in city budgets to the most debated vendor in American local government in about a year. For GovTech founders selling public safety software, the lesson matters more than the headlines. Community trust is now a procurement criterion: a public safety software vendor must show in writing who can access the data, how long it stays, and how misuse gets caught before a city council or county commission approves the contract.

This post covers what happened to Flock, what buyers now write into policy, and how a founder under $5M ARR can turn trust into a sales advantage. It also applies the WIIFM Framework to a buying committee that now includes police chiefs, council members, and residents who speak at public meetings.

How the Flock Safety Backlash Reshaped Public Safety Software Buying

Cities and counties across the country are canceling, pausing, or rejecting automated license plate reader (ALPR) contracts. The anti-surveillance group DeFlock tracks more than 300 communities that dropped Flock. Flock itself still grows: its annual revenue run rate reached $500 million in June, up from $300 million in January, according to Bloomberg reporting.

Central Texas shows how fast the pattern spreads. Taylor, Hutto, Pflugerville, Bastrop, Leander, Elgin, Manor, and Liberty Hill all ended their contracts in recent months. Taylor announced its termination on November 2, 2026. The city paid $24,000 per year for eight readers on two state highways, and it cited weak crime-solving results and concerns about third-party access to the data.

Misuse drove much of the anger. The Washington Post documented nearly 50 cases of officers charged or accused of unauthorized use, most involving searches of current or former partners and family members. Council members read those stories, and then they asked their own vendors the same questions.

What Flock Changed in August 2026 and What It Signals About Buyer Expectations

On August 13, 2026, Flock CEO Garrett Langley announced a package of safeguards. Several of them now read like a default checklist for any public safety software vendor:

A seven-day default retention period for license plate data, down from 30 days, plus an Evidence Mode that preserves specific data for active investigations.
Offense filtering, which lets one agency allow another to search its cameras only for categories such as stolen vehicles, missing persons, or violent crime.
Required Audit Assistance, proactive lockout of abnormal users, and required case codes for law enforcement searches by the end of 2026.
Mandatory multi-factor authentication, an independent Bishop Fox security review, and a coordinated vulnerability disclosure program.
A public Transparency Portal, which more than 1,500 agencies have published, showing policy, retention period, sharing partners, and search activity.

Critics push back hard. The ACLU called the changes retreads of inadequate safeguards, and Robert Frommer of the Institute for Justice called them window dressing that leaves search decisions with police instead of judges. Langley also told Engadget that he had resisted requiring case codes and later decided Flock got that one wrong.

Whatever side you take in the policy debate, the buying lesson holds. Audit trails, retention limits, and sharing controls moved from nice-to-have to expected. A vendor that adds them after the headlines looks late.

How State and Local Rules Turn Community Trust Into Contract Terms

Governments now write trust requirements into law and policy. That moves a vendor's safeguards out of the sales deck and into the contract.

Missouri's Executive Order on License Plate Reader Data

Gov. Mike Kehoe's September 2026 executive order covers state and local agencies that receive state funding. It requires deletion of plate and vehicle images within 30 days unless an active investigation, emergency, or missing-person alert applies. It also requires written vendor certification of deletion, agency ownership of the data, a ban on sale or non-law-enforcement access, a ban on AI-powered facial recognition in these tools, and a recorded user identity and case number for every query. Penalties for misuse can include criminal charges.

City Ordinances That Require Audits and Public Review

Bloomington, Indiana adopted Resolution 2026-04 by a 9-0 vote on March 4, 2026, setting transparency rules, limits, and a public review process for ALPR technology.
Grand Rapids, Michigan applied its Surveillance Technology Policy to its existing Flock system effective September 7, 2026.
Salt Lake City's draft ordinance would require quarterly audits and an annual comprehensive review of police ALPR systems.
Atlanta's police department audited 115,578 Flock searches conducted year to date in 2026, and the mayor announced legislation to codify oversight rules.

Drone as First Responder Pilots Follow the Same Trust-First Pattern

Normal, Illinois approved a $50,000 one-year pilot of a Flock Drone as First Responder on June 15, 2026. The pilot publishes flight information with addresses redacted, and the department must return to council for renewal after 12 months. Oak Brook, Illinois reported a $275,000 annual contract for its program in 2025 coverage. Both buyers tied the purchase to public reporting.

Public Safety Software Trust Requirements: What Buyers Ask and What to Show

The table below turns the rules above into a pre-meeting checklist. A founder who can answer every row in a first call removes the longest objections from the sales cycle.

Requirement	What buyers write into policy	Real example	What your team should show
Data retention	A fixed maximum retention window	Missouri order: 30 days. Flock default: 7 days.	Configurable retention with automatic deletion and a written deletion certificate.
Data ownership	The agency owns all data, not the vendor	Missouri executive order	Plain-language contract terms and an export option.
Search auditing	Every query logs the user and a case number	Missouri order; Flock required case codes	An audit log the agency admin reads without a support ticket.
Sharing controls	The agency decides who sees its data and for which offenses	Flock offense filtering	Sharing set to off by default, with a visible sharing list.
Public transparency	A public page showing policy, retention, and usage	Flock Transparency Portal; Normal drone flight page	A public report the agency can publish in one click.
Security review	MFA, independent testing, and a disclosure program	Flock MFA and Bishop Fox review	A third-party report and a named security contact.
Technology limits	No facial recognition or new analytics without approval	Missouri executive order	A written feature-gating policy.
Exit terms	Clean termination, removal, and data deletion	Plymouth, Minnesota reportedly saw cameras stay up after a termination vote	A termination clause with a removal date and deletion confirmation.

The GovTech Founders GTM Playbook covers how to sequence these answers inside a government sales process.

Per-Unit Pricing Meets Trust Doubts: Why ROI Proof Matters More Now

When confidence drops, buyers ask whether the product is worth the money. Public pricing shows how exposed per-unit models are. Flock Falcon cameras run roughly $2,500 to $3,000 per camera per year, plus a one-time installation fee of about $250 to $350.

Public records show the same math in smaller towns. Sterling, Illinois documents list a $3,000 standard subscription and $1,500 when the city already owns the hardware. Springville, Alabama pays $27,000 to $28,000 per year for 13 cameras, and its mayor said the debate centered on whether the cameras were worth the cost, not only on privacy. Bloomington, Indiana ended a $50,000 agreement after community pushback.

Founders should price against outcomes a council can verify. Track cases cleared, response times, and hours saved, then give the buyer a one-page annual report they can read aloud at a public meeting.

Switching Public Safety Software Vendors Does Not Fix the Trust Problem

Axon, Motorola Solutions, Verkada, Rekor, and Genetec all position to win Flock's departing accounts. Denver and Longmont, Colorado signed contracts with Flock competitors this year, including Axon. Matthew Guariglia of the Electronic Frontier Foundation described the switch as swapping one color of camera for another, because the tracking capability stays the same.

Buyers who switch without new governance rules inherit the same questions. That gap gives a smaller vendor an opening. The ACLU notes that Rekor lets clients install software and process data locally. Syracuse moved to Axon and is working with Axon on a transparency portal that publishes how readers help investigations.

A vendor under $5M ARR cannot outspend Axon or Motorola Solutions. It can ship every row in the table above as a default and make each one easy to show in public.

How to Apply the WIIFM Framework When Residents Join the Buying Committee

The WIIFM Framework (What's In It For Me) assigns separate value propositions to the department head, the elected official, and the resident. Public safety software now needs all three, because a resident can end a contract with a three-minute comment and a council vote.

Department head (police chief or sheriff): faster case work, fewer manual searches, and audit logs that protect the department when someone questions an officer's search.
Elected official: a policy they can defend at a public meeting, with retention limits, data ownership, and a way to cancel.
Resident: a plain-language page that shows what the system collects, who can search it, and how long the agency keeps the data.

Honesty in the room matters as much as features. Leaked audio from an IACP conference, reported by 404 Media in October, captured Flock's CEO telling police chiefs that the online backlash came from bots. Flock also says its technology helped with about 1 million investigations last year. Council members who hear residents at the microphone every week know the opposition is real, and a vendor who dismisses it loses the elected official first.

Treat the exit path as part of the product. Plymouth, Minnesota's council voted to terminate its Flock contract in September, and local reporting says the cameras stayed up for more than a month. A documented, fast exit builds more trust than any feature.

AI mentions in a pitch can trigger security reviews and lengthen the sales cycle. Read the 9 AI Reality Filters before you add AI language to a public safety pitch, especially in states that now ban facial recognition in these tools.

Frequently Asked Questions About Public Safety Software and Community Trust

Why are cities canceling Flock Safety contracts?

Cities cite officer misuse of search data, sharing with outside agencies, weak crime-solving results, and cost. Taylor, Texas cited limited benefit and third-party data access when it ended its $24,000 annual contract on November 2, 2026.

What data retention period do public safety software buyers expect in 2026?

Expectations keep shrinking. Flock moved its recommended default from 30 days to seven days in August 2026, and Missouri's executive order caps retention at 30 days for covered agencies unless an active investigation, emergency, or court order applies. A vendor should offer configurable retention, automatic deletion, and written certification.

How should a small public safety software vendor prepare for a council vote on surveillance technology?

Bring a one-page summary of retention, data ownership, audit logging, sharing controls, and exit terms, plus a public transparency page the agency can publish. Prepare separate talking points for the department head, the council member, and residents using the WIIFM Framework.

Does switching license plate reader vendors solve community trust concerns?

No, not by itself. The ACLU and the Electronic Frontier Foundation say competitors offer similar capabilities. Buyers who switch and add retention limits, audits, and public reporting address the concern, while buyers who only swap hardware inherit the same questions.

What Public Safety Software Founders Should Do Next

Trust now sits inside the product, the contract, and the public meeting. Founders who ship retention limits, audit logs, sharing controls, a public transparency page, and a clean exit path give every member of the buying committee a reason to say yes.

Hear how other GovTech founders approach public buyers on the Built for Government podcast, then run your own go-to-market through the checklist above.

Next Steps for GovTech Founders

Try the GovTech GTM Scorecard.
Contact us to learn more.
Learn more about the energizeGTM process.
Visit the energizeGTM Library for articles, downloads, podcasts, playbooks, and frameworks.
Download the WIIFM Framework.