Since 2023, dozens of American communities have removed, defunded, or blocked the same systems Asheville just bought. This page is about how, because the pattern across every documented win is strikingly consistent, and it tells Asheville’s opposition exactly where to aim.
Every rollback ran through one of three gates: a renewal or appropriation date, an audit revelation, or a vendor caught lying. Not one city won on outrage alone.
Officials change their minds: here’s what changes them
The question that matters for a 6–1 council: do supporters ever flip? Constantly. Ranked by potency, with receipts:
1. The vendor lies to their faces. Oshkosh, WI approved its Flock renewal 5–2 on April 21, 2026, after a Flock rep denied the system could build movement heat maps. The police chief’s own staff told him it was false; he verified it himself the next morning. Two days later the council rescinded 7–0: every yes vote flipped in 48 hours. Deputy Mayor Joe Stephenson: “I don’t know how this body can govern if someone tells untruths.” (Fox 11 · ACLU’s catalog of Flock’s misrepresentations to councils) Sedona’s arc was identical: Flock told council Aug 13, 2025 there was “no data-sharing going on”; by month’s end it admitted CBP had accessed Sedona’s data; unanimous termination Sept 9. Vice Mayor Holli Ploog: “not, in my opinion, an honorable company.” (KNAU)
2. An audit shows their own safeguards failing. The cleanest champion-to-skeptic arc is Austin’s Chito Vela, the council member who authored the 2023 reinstatement with a 7-day retention limit. The 2025 city audit found 20%+ of searches had no documented justification and retention exceeded his own limit. Vela, publicly: “Careful thought is needed on data privacy and legal protections before considering any ALPR program.” The safeguards that failed were the ones he himself wrote, which is why their failure convinced him. (KUT · EFF) Denver’s council went from accepting a pilot to unanimously rejecting renewal after audit logs showed its data searched 1,400+ times by or for ICE. Council member Jamie Torres, on the vendor-swap vote that followed: “Fool me once, shame on you.”
3. Constituents show up in volume, especially across party lines. Macon County’s commission chair Josh Young “dreaded” the vote and leaned toward his sheriff, then polled constituents in ordinary interactions and found informed residents “nearly unanimously against.” His explanation for flipping: “I work for the people, the people put me here.” Commissioner Barry Breeden (a former sheriff’s deputy, self-described 50-50 going in) flipped the same night. A hundred-plus residents, mobilized in three weeks largely via one commissioner’s Facebook posts. (Smoky Mountain News)
4. Legal risk gets real. San Marcos council members explicitly discussed pending Flock lawsuits before letting their contract die. The 4th Circuit’s pending Norfolk case (The National Wave) binds North Carolina.
Anatomy of the wins: the mechanics worth stealing
- Austin: the audit-before-renewal maneuver. In March 2025, rather than fight the renewal head-on, opponents got council to extend only until an audit completed. The audit manufactured the evidence that killed the program three months later. An audit is the easiest thing a fence-sitting council can grant, and in Austin it ended the program.
- San Marcos: the pre-filed exit. Staff sent Flock the non-renewal notice before the decision meeting as a placeholder. Council then deadlocked 3–3, and because the notice was already filed, the tie meant expiration. Procedural inertia flipped to favor exit.
- Nashville: threshold math. The Fusus contract failed 20–18 because passage required 21 affirmative votes: absences and abstentions functioned as no votes. The two-dozen-organization coalition whipped the threshold, not just the noes.
- Evanston: breach termination, and the enforcement fight after. The Illinois Secretary of State’s audit (CBP access in violation of state law) gave Evanston a breach predicate to terminate mid-contract. Then Flock reinstalled the cameras without authorization, and the last ones came down only after a press inquiry, months later. Lesson: the motion must specify deactivation date, removal deadline, data deletion, and verification. A termination vote without deadlines and verification can be quietly reversed.
- Fort Collins: the procurement foul. Police had signed the Flock deal without a council vote. Six months of steady public comment later, council canceled 6–1 and froze any re-procurement until a citywide surveillance policy exists. (Asheville parallel: APD’s ALPR policy was revised to reference the RTIC a week before council approved it; the machinery-before-democracy pattern is the same lever.)
- Verona & Dane County, WI: the network-density attack. Verona’s mayor articulated it openly: “Once they’re out in Dane County, they become less useful for other law enforcement agencies.” Remove nodes, degrade the network’s value regionally. When Flock stalled removal, the mayor had the cameras bagged in black plastic and the county sheriff’s office later covered its own. (Bolts) For WNC: Macon already took out twelve nodes. Every county that follows shrinks the 500-mile net around Asheville.
- Hillsborough, NC: read the contract aloud. The town killed its program on the contract text alone: the clause letting Flock disclose data to “any government entity or third party” on its own “good faith belief.” A May 12 Asheville commenter read the same clause into our record (6:04:23 on the video). Asheville’s version of this tactic is blocked by one fact: the executed Axon contract still isn’t public. Which is why it’s records-request #1 on Documents.
What backfires
- Vandalism. The national wave of camera destruction has produced felony charges (Class 2 felonies in Illinois, an 18-year-old charged in Florida, a congressional candidate charged in Tennessee) and handed Flock and police a victimization narrative that organizers then had to spend credibility distancing themselves from. A Flock camera near Carrier Park was vandalized August 7. The documented record says plainly: it doesn’t remove systems (councils and audits do), and it damages the people doing the work that does.
- The vendor-swap trap. Denver removed Flock and hired Axon 7–6. Savannah re-awarded Fusus’s function to Axon. ACLU-Wisconsin’s Jon McCray Jones: replacing Flock with another ALPR company “doesn’t solve the underlying problem”; communities end up “playing a game of Whack-A-Mole with surveillance companies.” Asheville skipped straight to the Axon endgame, which means the goal here isn’t “cancel Flock,” it’s capability governance: what the system may do, regardless of whose logo is on it. Full treatment: Getting Flock Out.
- Winning without codifying. Austin’s win is already under siege: a May 2026 crime spree had the mayor calling to bring ALPRs back, Texas DPS installed state cameras in the city, and APD kept querying neighboring towns’ Flock systems. The cities whose wins stick are the ones that passed a surveillance ordinance (Austin’s TRUST Act, Fort Collins’ policy freeze, Madison’s CCOPS) so a news cycle can’t quietly reverse them.
Asheville’s exit map: a 7.5-year contract is not a life sentence
The Axon bundle forecloses the easy non-renewal gate until the 2030s. What remains, all documented in other cities:
- Annual appropriations. Government Axon/Flock deals bill annually and carry non-appropriation clauses: Macon, Dane County, Pittsboro, and Columbia, MO all exited by defunding, not terminating. Every Asheville budget cycle is a live vote on the RTIC.
- Audit-before-anything. The Austin maneuver, adapted: council motion that no expansion, renewal, or new feature activates until quarterly audits are published. The city already refused a Flock audit-log request once (Promise Tracker); make the refusal itself the issue.
- Feature-activation votes. Axon and Flock add AI capabilities mid-contract. A council rule requiring a public vote before any new capability turns on (facial recognition, audio analytics, new sharing) governs the system without touching the contract.
- Breach and misrepresentation. Sedona terminated for dishonesty and demanded a prorated refund; Oshkosh rescinded an agreement induced by false statements. If the vendor claims made to Asheville’s council prove false (and the claims inventory on this site exists to test exactly that), the same predicates open here.
- The Sourcewell soft spot. The Axon deal rode Sourcewell cooperative pricing, piggyback contracts that skip local bidding and typically import zero locally negotiated data-governance terms. Demanding a local data addendum (ownership, deletion, no-sharing, audit rights) is a legitimate procedural lever council can pull mid-contract.
- Codify before the next crisis. A CCOPS-style ordinance (the blueprint) is what makes any of the above durable.
The toolkits, so nobody starts from scratch
- DeFlock Apex’s NC records-request generator and model ALPR governance ordinance: the most polished NC-specific artifacts; their audit-log analysis (15,335 searches, up to ~100,000 cameras reached per search, 28% with no reason recorded) is the template for what Asheville’s logs would show.
- The DeFlock-community ALPR toolkit: council handouts, 3-minute talk tracks, briefings for mayors and deputy chiefs, and nine post-approval asks that map one-to-one onto an RTIC oversight ordinance. Its doctrine matches this site’s: lead with governance; pair every concern with a specific ask.
- Oakland Privacy’s Fighting Local Surveillance toolkit: 17 model documents for the long campaign.
One more honest note: no city that removed these systems has documented a crime increase attributable to removal, while Atlanta’s homicide clearance rate fell during a 5,000-camera buildout. The burden of proof never belonged to the opposition.
Related: The National Wave · Speak at Council · Promise Tracker · WNC and NC · Oversight Theater