Five cities canceled Flock. Not one of them took the cameras down.

On October 21, 2026, the Reno City Council voted 5-2. The question on the table was not whether to cancel the Flock Safety contract for license plate readers. It was whether to expand the existing Axon Enterprise contract to include them.[2] The vote was to expand, not to switch off. What Reno bought was more than 200 plate readers — 136 for police vehicles and roughly 50 solar-powered fixed “Outpost” cameras — replacing the prior Flock hardware.[1][10]

The Durango Police Department put the same point in one official sentence, with no hedging: “This is a change in technology providers. It is not an end to DPD’s use of automated license plate recognition (ALPR).”[25]

This is not one isolated case. Five documented jurisdictions switched vendors in 2026 without uninstalling anything: Reno (Nevada), Fairfield (Connecticut), Caldwell (Idaho), Asheville and Apex (North Carolina), plus Durango (Colorado). And two went the other way: New Bedford (Massachusetts) banned the system outright[19][21], and St. Johns County (Florida) revoked the permits.[17][18]

Reno’s October 21 meeting had been on the official agenda for weeks — the draft agenda memo dated October 9 already listed it[24] — which means the vote was not an emergency reaction. It was a scheduled decision.[2]

What actually got negotiated

The interesting part isn’t who won. It’s what the council wrote into the contract. Reno’s five conditions were concrete: data retention at 15 days — down from 30 — quarterly audits — down from every six months — quarterly public reporting, and termination without penalty on 30 days’ notice.[3][8] The whole package: $21.8 million over eight years, running January 1, 2027 through December 31, 2034.[1]

Caldwell went 4-1 on October 5, 2026, and didn’t just change vendors. It went from 45 cameras to 65.[7][23] The new budget was $6.7 million over ten years, though the money was already approved in the police department’s FY2027 budget — the council only decided how to allocate it.[13]

The justification was volume, not privacy: the police department’s own transparency portal recorded 405,661 vehicles in 30 days.[5]

What Caldwell left behind is on the record too. The original resolution authorized 10 Flock cameras at $30,000 per year, with auto-renewal.[20] That’s the contract a city decides to change vendors on: few cameras, a recurring annual number, no exit clause.

Fairfield did remove everything. As of October 5, no Flock equipment remained in the city, and police now use 54 Axon readers, with 21-day retention and monthly audits run by internal affairs.[4]

And what they bought isn’t just plate readers. Axon’s fixed Outpost camera combines live video streaming, plate reading, and vehicle attribute recognition in a single unit.[22] That’s exactly the kind of hardware consolidation that makes “switching vendors” a platform decision rather than a camera swap.

The number that matters: the vendor doesn’t set your retention window

Here’s the lesson, and it isn’t anecdotal. On August 13, 2026, Flock changed its default retention from 30 days to 7 days and introduced “Evidence Mode,” with its own analysis that more than 90% of searches without a full plate happen within a week.[12] But that default applies to law enforcement customers. Private-sector customers keep whatever retention terms their account already established.[14]

And the window isn’t the vendor’s call either. The state’s is. Connecticut and Washington mandate 21 days by law, regardless of what the vendor’s Order Form says.[11]

Durango wrote down the thing no contract should have to: “The 21-day retention period does not grant officers unrestricted authority to search 21 days’ worth of information. Retention and access are separate issues.”[25] Retention and access are two different controls. If you only negotiate one, the other stays at whatever the default was.

The contradiction nobody resolved

At the Douglas County meeting, the Sheriff’s Division Chief said it plainly: “Currently right now with Flock, we do not own that data.”[26] That was the stated reason for the switch — alongside a contract priced at $22,772,754.11 across 120 months that swaps roughly 50 Flock cameras for 100 Axon Outposts.[26]

But Flock’s own published terms say the opposite: “As between Flock and Customer, all right, title, and interest in and to Customer Data belong to and are retained by Customer,” with a limited license back to operate the service and improve it.[27] The page explaining this is the vendor’s own material — it is what the vendor publishes, not independent verification of what actually happens to the data in practice.

Both versions stay, each one attributed. That’s the whole point: data ownership in the analytics layer isn’t resolved by the vendor’s standard contract. You resolve it yourself, separately.

Three clauses for your RFP

This documented pattern — cancel the vendor, keep the technology, swap the hardware — is not a national movement. It’s five jurisdictions, plus Colorado. Don’t generalize it. But you can use what they renegotiated:

1. A retention-window clause with a number and an exception. Write the number of days and the exception (“unless tied to an active investigation”) into the contract. Don’t inherit it from the vendor’s default, because the default moved from 30 days to 7 days overnight[12] and because state law can override it.[11]

2. A data-ownership and audit-trail portability clause. Who owns the search history, what format it comes in, and how fast you get it when the contract closes. The Douglas County Sheriff thought his department didn’t own the data[26]; Flock’s published terms say it does[27]. Neither answer is worth anything if it isn’t in your contract in writing.

3. An exit right that survives the contract. Thirty days to terminate without penalty, and no penalty for early exit if the vendor unilaterally changes terms. That’s what Reno explicitly bargained for, and it’s what most don’t get.[3]

One honest note on scope. Not every documented jurisdiction bought more cameras. Apex, after discovering that roughly 99% of searches of its data were not conducted by its own police, limited sharing to North Carolina and the four surrounding states[15] — a tightening, not an expansion. Its June 9, 2026 council presentation had documented sharing with about 1,000 police agencies, with federal agencies automatically excluded.[16] That’s the share-with-everyone model Apex cut back. And in Asheville, the vendor switch came alongside an audit that found 2.7 million searches between April and June 2026.[9]

And on the other end, New Bedford negotiated nothing. The council voted 8-3 on September 24 to give initial approval to an ordinance barring the city from operating plate readers, and on October 8 the city gave written notice canceling the Flock contract, which expired November 12.[6] The pattern holds: either you renegotiate the terms, or you switch the system off. What didn’t happen in any of these cases is the middle option.

P.D. Your current contract for the video layer — fixed cameras, analytics, or both — does it state a number of days for retention in writing, or are you inheriting the vendor’s default? It’s the cheapest and most revealing question you can ask your own contract.

📰 Sources: 27 verified documents (government primary records, specialist trade press, and official vendor material), all accessed 2026-10-24. The full list, with the verbatim quote behind every figure, is in the sources block below.

Sources

  1. Route Fifty (Michael Lyle) — Out of the Flock and into the Axon: Asked to dump license plate readers, Reno just switches brands — trade_press, accessed 2026-10-24
  2. This Is Reno — Reno police seek $22M, eight-year Axon deal for body cams, license plate readers, Tasers, drones and AI tools — trade_press, accessed 2026-10-24
  3. Reno Gazette Journal / Tacoma News Tribune (Mark Robison) — Reno City Council votes 5-2 to switch surveillance camera contractor — trade_press, accessed 2026-10-24
  4. KTVN 2News — Reno Council approves Axon contract despite privacy concerns — trade_press, accessed 2026-10-24
  5. KOLO (Tisha Potijaroen) — Reno council approves Axon consolidation contract — trade_press, accessed 2026-10-24
  6. City of Reno, NV — Draft Agenda Memo, 10/21/26 Reno City Council Meetings (official document) — government_doc, accessed 2026-10-24
  7. CT Insider — Fairfield ditched Flock. Here’s what replaced it. — trade_press, accessed 2026-10-24
  8. BoiseDev (Erin Banks Rusby) — City votes to ditch Flock, expand its automated license plate reader count with another vendor — trade_press, accessed 2026-10-24
  9. Boise State Public Radio (Julie Luchetta) — Caldwell votes for more License Plate Readers, approves $6.7 million contract with Axon — trade_press, accessed 2026-10-24
  10. KTVB — Caldwell approves $6.7M surveillance and technology contract with Axon in a 4-1 vote — trade_press, accessed 2026-10-24
  11. City of Caldwell, Idaho — City Council agenda, October 5, 2026 (official document) — government_doc, accessed 2026-10-24
  12. City of Caldwell, Idaho — RESOLUTION 41-25, Flock Safety License Plate Reader Cameras (official document) — government_doc, accessed 2026-10-24
  13. WLOS / Nexstar 13 (Rian Stockett) — Asheville residents press police on 2.7M license plate reader searches cited in audit — trade_press, accessed 2026-10-24
  14. ABC11 / WTVD I-Team (Jon Dowding) — NC police department limits Flock data sharing as public concerns grow — trade_press, accessed 2026-10-24
  15. Apex Police Department — ALPR presentation to the Town Council, June 9, 2026 (department document) — government_doc, accessed 2026-10-24
  16. City of Durango, Colorado — Durango Police Department Will Transition ALPR Program from Flock Safety to Axon (official announcement) — government_doc, accessed 2026-10-24
  17. Kim Monson Newsroom — Douglas County $22.8 million Axon contract replaces Flock cameras — trade_press, accessed 2026-10-24
  18. The New Bedford Light (Eleonora Bianchi) — City won’t renew Flock contract — trade_press, accessed 2026-10-24
  19. City of New Bedford, Massachusetts — Ordinance on Automated License Plate Readers (ALPR) and Mass Location-Tracking Technologies (official text) — government_doc, accessed 2026-10-24
  20. WBSM — New Bedford license plate reader ban — trade_press, accessed 2026-10-24
  21. St. Johns County, Florida — official recording of the Board of County Commissioners, October 20, 2026, with full transcript — government_doc, accessed 2026-10-24
  22. News4JAX (Heather Bazley) — In split vote, St. Johns County commissioners revoke permits for all license plate readers on county roads — trade_press, accessed 2026-10-24
  23. Flock Safety — Flock Updates Privacy, Accountability, Security, and Transparency Safeguards (Garrett Langley, CEO) — vendor_primary, accessed 2026-10-24
  24. Flock Safety — What Flock’s Privacy and Security Updates Mean for Private Sector Customers — vendor_primary, accessed 2026-10-24
  25. Flock Safety — State-Specific Contractual Provisions (updated September 17, 2026) — vendor_primary, accessed 2026-10-24
  26. Flock Safety — Data Ownership (plain-language explanation of Section 4.1 of the Customer Terms and Conditions) — vendor_primary, accessed 2026-10-24
  27. Axon — Axon Announces New Fixed ALPR Camera Solutions and Next-Gen AI Advancements (press release) — vendor_primary, accessed 2026-10-24