This essay stands on documents you can open: Brevard’s posted draft camera policy and the Axon master terms on the city’s ALPR page, read clause by clause on Transylvania County; the Supreme Court opinions in Olmstead and Katz; the Church Committee’s published hearings; and the audit records this region’s own communities have pulled. It was written for the question that runs under every camera vote in WNC: once a system is installed, who can change the rules it runs under, and by what process?
The tools most residents accept
Start with the tool at its best, because it gets lost. A camera on a patrol car that reads the license plate directly in front of the officer answers one bounded question: is the car I am behind stolen? It looks at a vehicle the officer is already lawfully looking at. It keeps eyes on the road instead of on a keyboard. If the answer is no, nothing needs to be kept. Very few people in any WNC meeting room object to that tool, and the public comment records across this region bear that out.
The same is true of the accountability camera. A body camera under a policy the community chose, recording encounters both sides can point to afterward, with an audit trail someone actually reads, is a tool many residents asked for. Asheville’s were asked for.
Both examples sit outside this essay’s subject. The question in front of Brevard, Hendersonville, Henderson County, and every community after them is narrower: two companies, Axon and Flock Safety, sell those tools bundled with networks and defaults the tools themselves do not require, and the bundle arrives with its rules already written. This essay is about who can rewrite them.
Where the industry’s checks have come from
An industry that finds its own failures early writes that practice down; aviation did, and built public investigation and protected reporting into the whole system. The camera industry’s record, run through a four-question test in The Camera Companies’ Safety Record, shows its effective checks operating from outside: the problems in that record were surfaced by journalists, researchers, state auditors, and prosecutors, and the fixes followed the publicity. One case carries the timing plainly: in Colleton County, South Carolina, the vendor’s own audit tool, available throughout, was switched on this August and found a year of one lieutenant’s misuse within a day (ABC News 4 Charleston). For a town weighing a purchase, that record locates the working check where it has always been in this history: outside the system, in the community’s own instruments.
What “currently constitutional” has meant
When Asheville’s council debated its cameras, the city attorney provided a memo on the constitutionality of the technology, and members cited it. Take the claim at face value: courts so far have largely allowed warrantless plate scanning. The history worth knowing is what “currently constitutional” has meant before.
Warrantless wiretapping was constitutional for 39 years. The Supreme Court said so in Olmstead v. United States in 1928: no trespass, no search. An entire era of surveillance ran on that holding until Katz v. United States overruled it in 1967, finding the Fourth Amendment “protects people, not places.” The technology barely changed in those four decades. The check changed.
The CIA opened Americans’ mail for twenty years, more than 215,000 letters photographed and read under a program called HTLINGUAL, asserted lawful the entire time. It ended when the Church Committee put the numbers into the public record in 1975. The major telegraph companies gave the NSA copies of international telegrams for thirty years, a voluntary arrangement called SHAMROCK, until the same committee declassified it over the administration’s objection. The FBI’s COINTELPRO ran fifteen years and was discovered only when activists removed documents from a field office and mailed them to reporters. The NSA’s bulk phone-metadata program operated for years under a classified legal theory its operators certified as lawful, until a federal appeals court read the statute in 2015 and found the program exceeded it; Congress ended bulk collection within months.
Every one was operated by people who sincerely believed it lawful, and in each case the safeguard that ended it came from outside the program, from a committee, a court, a burglary’s documents, reporters, an audit. Mail still moves, phones still work, and police still wiretap, with warrants; the reforms each time were oversight, written down. “It’s constitutional” describes the present tense, and in this history the present tense has changed when someone outside the system checked.
Who can change a system’s rules
Set the industry’s record beside the history and the shared variable is the pen: who can change a system’s rules, by what process, visible to whom.
Brevard’s draft camera policy earns its credit first: a 30-day purge, per-search case numbers, and a public annual report, each stronger than most of the region’s existing deployments. Each of those protections lives in a police General Order, a document the chief signs and the chief can amend, with no council vote and no public notice required; the posted Axon master terms add a data program that stays on until revoked in writing and metadata assigned to an “independent Data Controller” that is not the city. None of this is hidden, and none of it requires bad faith to matter. The rules of the system, as the documents stand, can change by a chief’s signature, a vendor’s product update, or a sharing setting, and the community’s part in each of those changes is to learn about it afterward, if a record surfaces.
The same mechanism has produced every protection in this record. Denver’s council signed a one-year term, a camera cap, and a no-national-database clause, because it asked before signing. Washington State wrote a 21-day retention cap and named prohibited uses into law, and agencies that could not comply shut their systems off. Boone’s council paused expansion and ordered a public portal, and its police chief cut the sharing list 96 percent after pulling the log. The Church Committee’s reforms were ink; Katz was ink. Each protection was also a signature; the difference in every case was whose signature the change required, and whether the public could see it coming.
Deciding before signing
Brevard posted its documents before deciding: an information session on Sept 1, 2026 and a council date of Sept 8, 2026, at which the chief withdrew the request before a vote. That sequence has already produced more public reading of the actual terms than Asheville’s vote received, and it cost Brevard nothing.
The asks that follow from this essay are versions of what the pro-camera residents in our records also ask for. Put the retention, sharing, and audit rules in a document only council can change. Publish the price, the term, and the camera locations. Opt out of the vendor’s default data program in writing. Name who runs the audit and publish what it finds. If the vendor’s answer to any of these is no, that answer is information, and slower is allowed: the stolen car in front of the patrol car can still be checked tomorrow.
In February, a thirty-second Super Bowl ad showed Ring owners what their own doorbell cameras could become on a shared network, and within days the backlash led Amazon to cancel Ring’s partnership with Flock before it launched. The customers had chosen their cameras and kept them; the objection was to the network, and once the difference was visible, people acted on it. The same difference, in the systems WNC towns are being offered, is documented in How Camera Networks Share Data, and Brevard’s documents are posted now, before its vote, for anyone who wants to look.
Sources for every claim above are linked in place or live on Transylvania County (the Brevard documents, read clause by clause), Watauga County (the Boone audit), Communities that ended or limited camera contracts (Denver, Washington, Ring), Camera network misuse, documented cases, and The Camera Companies’ Safety Record. Corrections welcome; this page is meant to be checked.