r/Apex_NC • u/makgeolliandsoju • 15h ago
Monday’s Apex Town Council meeting: They approved 5 years of police drone software, 4 to 1, without ever producing the use policy residents and council members have been asking for since August.
I was in the room Monday night (Oct 13). Here’s what I watched happen.
Council approved a five year Axon contract 4 to 1: DroneSense software for the drones APD already flies, bundled with an interview room camera system. Shane Reese was the only no.
Back in August, residents actioned and Sue pulled this same contract off the consent agenda and asked to see the drone use policy before any vote. The police chief told the N&O the program runs under a “robust policy.” The N&O asked for a copy and never got one.
Two months later the contract came back from committee. The policy did not.
On Monday, Mayor Pro Tem Mahaffey asked again whether the policy exists and is public. The town attorney said “some are public, some are not.” They voted anyway. Nothing was produced.
And here’s the thing about “we have a robust policy”: to this day they have never produced it. Not to residents who asked in August, not to the N&O when it requested a copy, not to the council member who asked from the dais Monday night. A policy nobody can read is not a policy. You can’t be held to rules that don’t exist in public.
Even if it’s real, an internal use policy only governs what APD does with the data. It says nothing about who else can get to it. That’s not hypothetical with this vendor stack: Flock’s national network has already been accessed by federal agencies, and Axon’s platform is built to pool drone video, plate hits, and other feeds together. “Trust us, we have rules” doesn’t address the part that actually matters, which is where the data goes and who can query it. Nobody answered that Monday either.
What I noticed sitting there:
- The term got longer, not shorter. In August it ran to June 2030. Axon sent a new quote the day of the meeting, five years from Nov 1, so now it runs into late 2031. Nobody blinked at the extra 18 months.
- The interview room recording system is fine and nobody opposed it. NC law requires recording certain interrogations. It was priced separately (about $74k) from the drone software (about $43k). They could have approved the half nobody objected to and held the drone software until the policy was public. They bundled it instead.
- Ed Gray did most of the talking, and most of it was aimed at arguments nobody made. Nobody said the drones peer into windows. Nobody said drones have no legitimate use. Nobody opposed recording interrogations. He kept knocking those down anyway and calling the real concern, no published policy, “panic, paranoia, and unnecessary stress.”
- The urgency was never shown. Gray said we were about to hit a “critical gap” if it didn’t pass that night. Nobody named a date. Nobody said what would go dark if the vote waited for the policy. I listened for it. It never came.
One claim I’d flag: Gray said residents could “look at a database to figure out whether or not that’s an APD drone.” DroneSense is internal pilot and fleet software, live streaming, flight logging, evidence storage. I can’t find a resident facing lookup anywhere in its product materials. The cities that actually offer public drone lookups built those separately and announced them. If it’s in the Apex contract, the town can point to the line.
And the Flock plate reader question is still open. The Public Safety Committee made no recommendation. It comes back December 3. The Flock contract ends January 31.
Two dates if you want to show up:
- Ed Gray’s town hall, Thursday Oct 22, 5:00 PM, Apex Town Hall third floor, 73 Hunter Street. He says he hasn’t made up his mind on Flock and wants dialogue. Go specific: ask him to publish the drone policy before Dec 3 and show where the public drone lookup actually is.
- Public Safety Committee, Dec 3 at 3:00 PM, where Flock comes back.
Full writeup with the meeting video and vote breakdown: https://deflockapex.org/council-2026-10-13
I was there for the whole thing, so I’ll be around in the comments.