This page is built from a specific set of records, all of them open to you: the videos of six Asheville council meetings, timestamped where quoted; the Buncombe County Sheriff’s Office’s own camera access log, 337,838 rows covering 28 months, released by public records request in May 2026; Flock Safety’s published product documentation; and the one signed Axon contract in North Carolina that has been posted in full, Durham’s. We read them because towns across this region are being asked to vote on camera systems, and the votes keep being described as cameras, yes or no. The records describe a different decision. A town in these contracts is deciding two separate things: what its cameras record, and what network that recording joins. The second decision is the one the documents below keep turning on, because a town that removes every camera and keeps its network account keeps the searching.
The tools, at their best
Everyone in these meeting rooms wants their neighbors safe, and the tools have real uses worth naming first. A plate reader on a patrol car answers one bounded question about the car in front of the officer: is it stolen? A body camera records an encounter both sides can point to afterward; Asheville residents asked for those. A shop camera records the door for its owner to review. Each of these makes a record, for a known owner, under rules that owner answers for. The record here also credits the stewardship: on the night Asheville ended its Flock contract, councilmember Sage Turner thanked APD “for not being one of those scary statistics… for maintaining this software while we had it under our purview, safely” (Aug 25, at 3:53:53), and nothing in this page disputes that.
Two products, in the department’s own words
The clearest description of the two decisions came from the police department itself, eighteen months before the argument reached a vote. In March 2025, briefing council on camera registration, APD technology specialist James Wingo described the options for a private camera owner (March 25, 2025, at 42:09):
“whether it’s businesses or the Ring camera at your home, it can be optioned to feed into the public’s real-time intelligence center data… There’s a registry, just so we know where a camera is in a city — and then there’s also one where you could provide us full viewing capability.”
A registry records where a camera is. Full viewing capability lets the center watch it. The department offered both as a menu, which is the distinction this page is about, stated as product options.
How the search network works
Flock’s nationwide search is a feature of an agency’s account. An agency whose account has the national lookup setting on can search the shared reads of roughly 80,000 cameras across the country in one step, whatever number of cameras the agency owns. Searches leave the agency’s town through that account, and other agencies’ searches arrive into it the same way. The camera count changes none of it; during Asheville’s wind-down, the plan for a time was to keep a single Flock camera, described by councilmember Turner as pointed at a wall, and that camera would have kept the account, and the account keeps the national search.
The terms of the trade were stated on the record one county west. Asked at Jackson County’s August 4, 2026 work session whether his county can get plate data from other agencies, Sheriff Doug Farmer answered that sharing Jackson County’s own data is the only way to receive theirs (the recording, at 1:31:23). That is the bargain in the operator’s own description: an agency’s access to the network is paid for with its own community’s reads (Jackson County).
What the local record shows
Asheville’s officials confirmed this on the record, before the votes.
- May 7, 2026, five days before the RTIC vote, Turner described the keep-one-camera plan: keeping one “really… just means that we have some kind of access to the interface so that we can use those that are out there that aren’t even our cameras.” Interim Chief Jackie Stepp: “Yeah, that’s kind of right. That exactly right.” (The May 7 briefing)
- The same day, councilmember Bo Hess, arguing for the plan at 43:23: “even if Asheville got rid of every single Flock camera in Asheville, there would still be Flock cameras that you would be in contact with all over Western North Carolina… until Axon has the type of database that we can access like Flock, keeping that one Flock camera is a strategic public safety move.” The value being kept, in his own account, was the database access.
- Aug 20, 2026: Flock set a ten-camera minimum for system access, which ended the one-camera plan (the Aug 20 briefing). Mayor Esther Manheimer, the same briefing: “the cameras are technically not ours. They’re Flock’s.”
What the county’s own log shows
The one direct look this region has had inside a running network came from the sheriff’s access log. The full analysis carries the method and every count; the rows relevant here:
| Use | Events |
|---|---|
| Live views | 217,506 |
| Recorded views | 7,052 |
| Plate searches | 309 |
| Saved clips | 212 |
A camera used as a record keeper produces a log that is mostly playback after incidents. This log is 97 percent live viewing: 217,506 live views against 521 investigative uses (the searches and clips combined), or 417 live views for each one. Fifty-eight percent of all viewing was on public housing, where roughly 500 cameras feed the network and no published record shows residents were asked.
The log’s limits are part of the record: viewing durations exist for only 57.4 percent of live views, so hour figures are minimums; one live view can show a wall of cameras; events are not people; it is one agency over one period. The county also withheld every timestamp.
The question the withheld field would answer
There is a fair operational reading of the housing number: police respond to calls, and if calls come from public housing, live viewing would follow the calls. High volume could reflect workload rather than a chosen focus. The test is to line the viewing up against dispatch records for the same period, and the withheld timestamps are the field that test requires. The records request for the timestamp field and a narrow dispatch extract is written, addressed to the county, and this page will link the request and the answer once it is filed. Whichever way the numbers come back, they will be published here.
The line council members drew themselves
Three members of Asheville’s council stated the camera-versus-network distinction in their own words across five days in August, and the sequence deserves the credit of being quoted in full.
Turner, Aug 20, at 1:09:32: “I did reach out to legal, I did learn Axon has ALPRs… maybe that’s a part of the contract we wish wasn’t there… I’m not interested in dismantling body cams and dash cams.” Councilmember Maggie Ullman, the same briefing, at 59:03: the call to “get rid of Axon… starts to hit a wall where I can’t fathom pulling back on our transparency tools.” Then Ullman on Aug 25, voting yes to terminate (at 4:03:57):
“I feel like the tenor of the conversation is that all cameras, all surveillance, any data captured is bad, and I just kind of reject that. I have cameras at my house to keep me safe after I had violence at my house… to throw out all tools, body cameras, y’all, we fought really hard for those… I will support getting rid of these Flocks.”
And councilmember Hess, also voting yes, at 3:43:54: “ending one vendor’s contract is not the same as rejecting responsible technology.” Cameras at her own house, body cameras kept, the network contract ended: the positions are consistent, and they map exactly onto the two decisions this page began with.
Where the rules live
The contract does not settle any of this. The plate reader appendix in the signed Durham Axon agreement covers permits, installation, an installer’s liability, a vandalism warranty, and a seven-day acceptance window. It contains no retention period, no sharing rule, no network participation term, no use limit, and no audit duty (What Axon Contracts Do has the national pattern). The retention, sharing, and audit rules for any town’s system therefore live wherever that town writes them, and the concrete working example is nearby: Boone kept its cameras, published their locations and its policy on a public portal, and cut its sharing list from more than 1,000 agencies to about 40 after its chief pulled the log (Watauga County). The hardware stayed; the community set the network terms.
Two questions for any town
For an information session, a podium, or a letter, the two questions that follow from this record, each answerable by the people proposing the system:
- Which product is this? Does the data stay with cameras our agency owns, under our rules, or does it join a platform other agencies can search or watch? What is the network setting on day one, and what does turning it off cost?
- Whose signature changes it? If the sharing scope, retention, or network participation changes next year, does that return to a public vote, or does it change with a settings page and a department signature?
Brevard held its information session Sept 1, and on Sept 8 the chief withdrew the request before a vote; the posted documents, read clause by clause, are on Transylvania County.
Every quote above links its meeting page, timestamped to the city’s own video. The log analysis and method: Buncombe County Sheriff’s Office Fusus access log, 2024 to 2026. What a scan becomes on the network: What a plate read becomes. Corrections welcome; this page is meant to be checked.