Community research, not legal advice; consult your attorney and your insurance agent. Every claim below links its source, including the actual contract text.
APD’s Real-Time Intelligence Center will ask Asheville businesses to connect their cameras: either registering them (police know your camera exists and request footage) or integrating them (police get direct access through Axon’s Fusus platform, on a device businesses in other cities buy for ~$350 plus $150/year, auto-renewing). The Chamber recruited for the county’s version of this in 2023, with the tourism bureau’s marketing arm distributing the campaign. Before you sign anything, read what the paper actually says, because I did.
1. “Owner control” isn’t in the contract
The Fusus partner agreement (the full boilerplate is public, same template everywhere): the police agency must approve what you share; once footage is digitally requested through the software it transfers to a police cloud with no clause requiring notice to you or per-incident consent; and you hand over your camera and DVR admin login credentials (Greensboro’s NC program confirms). Real-time monitoring is limited only by “intention or expectation” language, not a prohibition. APD’s pitch, “you have total control to revoke the access at any time” (technology manager James Wingo, WLOS), sits next to a contract whose termination clauses contradict each other: one paragraph says the auto-renewing 5-year term ends only “by mutual written agreement”; another says anyone can quit anytime. Which one governs your business? Nobody will say in writing. And the same vendor’s city FAQs give opposite answers on whether police need your permission per access: Raleigh’s says yes, Kent’s says no. The signed contract matches Kent’s.
2. You can never see the audit log
“Everything is logged”: for police. No document anywhere gives the camera owner any right to the audit trail of who watched their cameras and when (the agency downloads it; you don’t), and APD’s reviews are quarterly and internal only: no external audit, confirmed on camera. The city has already refused to release its Flock audit logs to the public once (Documents).
3. If something goes wrong, you’re the defendant, not Axon
The contract’s liability section waives damages between you and the city: Nashville’s Community Review Board, analyzing this exact template, concluded there are “no established civil or legal consequences that either party can enforce on the other” (their report). Nobody indemnifies you. Axon isn’t even a party to the contract you’d sign. Meanwhile, when Flock cameras at Home Depot’s California stores drew a privacy class action, the named defendant was Home Depot, the camera host, not Flock. North Carolina recognizes the privacy tort of intrusion upon seclusion (Miller v. Brooks). The vendor gets the data, the police get the access, and you keep the risk.
4. A camera with a microphone can be a felony
NC’s wiretap law (G.S. 15A-287, a Class H felony, plus the federal Wiretap Act) requires consent from a party to the conversation. Your camera’s mic recording two customers talking to each other records a conversation you’re party to neither side of. The NC Real Estate Commission warns about exactly this; employment lawyers advise disabling audio entirely. This is not hypothetical hardware: Forest City’s Flock deployment, an hour east, advertises audio detection. Disable microphones. Ask in writing whether any networked device captures audio.
5. Integration makes you a records custodian
A networked camera is mapped as an evidence source for every agency in the system. That means preservation holds when litigation looms (auto-overwrite becomes spoliation exposure, sanctions up to default judgment), and subpoenas from prosecutors and criminal defense attorneys in cases you know nothing about. The sales pitch omits this: without integration you already have the only power that matters. Police get your footage when you choose to share it or when they bring valid legal process. Integration surrenders your discretion and keeps your liability.
6. Your insurance may not cover any of this
Modern general-liability policies carry exclusions for claims arising from “recording and distribution of material in violation of law” and access-or-disclosure of personal information; courts have enforced both, and insurers are actively tightening the forms. Ask your agent, in writing, whether footage-sharing claims are covered before you integrate. Nobody in the recruitment pipeline will ask for you.
7. The promises have failed everywhere they’ve been made
“Local control” preceded 4,000+ immigration lookups through local networks, a Texas deputy searching 83,000 cameras over an abortion, a Charlotte officer arrested for misusing the network, and 60+ cameras found streaming unauthenticated on the open internet. The NC SBI already reaches Flock cameras in Lowe’s parking lots across this state (WRAL Investigates). Asheville’s “civil liberties resolution” has no enforcement mechanism (Promise Tracker), and no functioning oversight body exists in this city at all (Oversight Theater).
8. Your customers are your business, and in this network, they’re the product
The mayor of Verona, Wisconsin, after canceling Flock: “The fact that they didn’t take the cameras down shows that we are the product.” (Bolts) Ring dropped its Flock integration after a mass customer revolt with returns and refunds; boycott pledges hit Lowe’s and Home Depot. Asheville sells independence and trust to a $2.6-billion-a-year visitor economy, and consumer research consistently shows large majorities won’t shop where they feel surveilled. The flip side is an opportunity: bookstores built brands on fighting subpoenas (Tattered Cover); San Francisco’s Castro bars just dropped facial-scan systems as a trust statement, and no “surveillance-free business” program exists anywhere in the country yet. Asheville’s could be the first. One downtown owner, Rebecca Hecht of Shining Rock Goods, is already on record: “We won’t be registering personally.” (WLOS)
The alternative that keeps you safe and useful
Keep cameras standalone · ~30-day retention · a one-page written policy: “footage released on valid warrant, court order, or subpoena, reviewed by [name]” · microphones off · post it where customers see it. You lose nothing investigatively (police can still get footage for real cases, through the front door), and you keep your discretion, your audit trail, your insurance posture, and your customers’ trust.
Three questions to ask APD/Axon, in writing, before signing anything
- Provide the exact contract an Asheville business signs, and point to the clauses that (a) require notice to me before any access or transfer, (b) give me the complete audit log of who viewed my cameras and when, and (c) indemnify my business if I’m sued over footage taken through the network. (Based on every published version: none of the three exists.)
- Once footage enters the police cloud, who can it reach (federal agencies included, in-state and out), under what standard? And when I revoke: what happens to already-transferred footage and to my DVR credentials? Reconcile the contract’s contradictory termination clauses in writing.
- What written policy, with what enforcement mechanism and what independent external audit, prevents my cameras from being used for immigration enforcement, reproductive-health investigations, or protest monitoring, and what remedy do my customers or I have if it’s violated? A resolution is a statement, not a mechanism.
If the answers are vague, that’s your answer.
Related: What Is the RTIC · Getting Flock Out · What Axon Contracts Do · Promise Tracker · Follow the Money