Asheville Ends Flock Safety Surveillance Contract, Raising Data-Governance Questions

The City of Asheville has ended its contract with Flock Safety for a police surveillance-camera service after Asheville City Council voted 5–2 to terminate the agreement. Police access ended the following day, bringing the city’s use of the service to a close. The reports do not state the contract’s value, the duration of the agreement, or the specific terms governing the city’s access to the cameras or their data. They also provide no indication that Asheville has selected a replacement provider or begun a new procurement process.

The contract’s termination does not, by itself, resolve what happens to data collected or accessed while the service was active. The source reporting identifies residents’ ability to ask who searched the data and whether it has been deleted as outstanding issues. That makes data governance a continuing concern for the city even after police access has ended. The available information does not specify the city’s retention schedule, the status of stored records, or what procedures residents should use to submit questions; those details should not be assumed from the contract decision alone.

For municipal procurement and technology teams, the episode underscores the need to make data-handling obligations explicit before a surveillance platform is deployed. Contract language and implementation plans can address which officials may search or retrieve information, what audit records are maintained, how long data is retained, and how deletion is verified when access ends or a contract is terminated. These requirements can help agencies preserve accountability across the full contract lifecycle, including the transition out of a service. The Asheville reports do not establish that any particular clause was missing from the Flock agreement, but the public questions make these issues salient for future procurements.

The decision also has a direct business implication for Flock Safety: its municipal service in Asheville has ended, and police no longer have access through the city arrangement. No replacement vendor, new solicitation, or planned follow-on procurement has been identified. Companies pursuing similar city contracts can use the public discussion as a reminder to explain how their systems support search auditing, access controls, data retention, and deletion. For prospective buyers, those capabilities can be evaluated as operational and governance requirements alongside the service’s core technical functions, rather than treated as contract-closeout details.

• Asheville City Council voted 5–2 to terminate the city’s Flock Safety contract.
• Asheville police lost access to the surveillance-camera service the day after the vote.
• Reports identify unresolved questions about who searched the data and whether it has been deleted.
• The available reporting provides no contract value, so the financial scale of the terminated agreement is not established.
• No replacement vendor, follow-on procurement, or solicitation details were reported.
• Municipal buyers should define authorized users, search auditing, retention periods, and deletion procedures in technology requirements and contract terms.
• Agencies should consider how access and data handling will be documented during termination and transition, not only during active operations.
• Vendors competing for public-sector surveillance work should be prepared to demonstrate searchable audit trails, access controls, retention management, and verifiable deletion processes.
• The source material does not describe Asheville’s specific retention or deletion arrangements; agencies should confirm those details through their own records and applicable contract documentation.