Flock Safety loses Bandera, TX contract as councilmember pushes internet and phone ban

Why it matters

Civic tech founders are selling into communities, not just agencies. Bandera shows how quickly opposition can turn a pilot into a PR and ops crisis. Build a consent and transparency playbook early or risk contract churn, vandalism, and policy blowback that can cascade across your pipeline.

After Bandera, Texas voted 3-2 to immediately end its contract with Flock Safety (@FlockSafety), a dissenting councilmember said he will push a sweeping ban on internet access, phones, and cameras across the town, according to a report in 404 Media.

What happened

The Bandera City Council, serving a town of roughly 900 people, voted to terminate its agreement with the surveillance startup that sells AI license plate reader cameras, a decision recorded in a meeting video (3-2 vote). Bandera had used a state grant to install eight Flock Safety cameras, but the rollout became a flashpoint: residents repeatedly packed meetings to object to government surveillance, and the poles holding the cameras were vandalized and had to be replaced at the town's expense, 404 Media reported.

After the vote, Councilmember Jeff Flowers, who opposed canceling the contract, said he will introduce what he calls the Bandera Declaration of Digital Independence. In a letter published by the Bandera Bulletin, Flowers wrote that he will propose "a total ban on all cellular and GPS-capable devices for all operations within city limits" and "a total termination of all internet services and electronic record-keeping. We are going back to 1880, paper ledgers and cash only."

Why founders should pay attention

For founders building civic tech and public safety tools, Bandera is a sharp reminder that product-market fit in the public sector includes community consent. Even a small municipality can become a national flashpoint if residents feel blindsided or surveilled.

What stands out in Bandera is not just the contract reversal, but the operational friction that preceded it: repeated vandalism, the municipality paying to fix hardware, and months of public meetings before a vote. Those are not edge cases; they are hidden line items in the cost of selling into local government when a product is perceived as imposed rather than adopted.

If you are selling AI-enabled infrastructure like license plate readers, here are playbook moves this episode underlines:

• Treat deployment as a community onboarding problem, not a procurement checkbox. Publish clear retention policies, access controls, and audit trails up front so residents can evaluate risks before a pole goes in the ground.
• Share outcomes in plain language. If a system prevents thefts or helps recover vehicles, report the stats regularly and be specific about false positives and safeguards.
• Price in friction. Budget for vandalism-resistant installs, replacement cycles, and staff time to attend public forums. If a town picks up those costs, expect backlash.
• Align on off-ramps. Make contract terms, data ownership, and removal processes as transparent as installation plans.

What to watch next

Flowers said he will bring his proposals to an upcoming council meeting, per the Bandera Bulletin letter. Whether the measures advance or stall, the episode has already reframed the debate from a technical procurement to a community values fight.

For Flock Safety's team, the Bandera vote will likely be studied by other small-town councils weighing similar tech. For founders in this category, expect more scrutiny, more data questions, and more demands for documented privacy guardrails before the first camera goes live.