City Councilman Joe Seconder Statement on Flock during the City Council meeting on February 23, 2026:
“Thank you for putting the all this together here Mr. McCormick [Flock representative]. I don't debate the value and benefit at all and appreciate our Police Department and Chief up here speaking verbally to us. I spent over 25 years [working in ] technology. I've worked at Oracle. I’ve sold software to the Department of the Army, DoD and Federal [agencies] in cloud environments. I understand SOC-1, SOC-2, FEDRAMP, NIST and so on.
However, I don't expect any of these people [elected officials], and I shouldn't have to hear that here [low-level technical security matters from a cloud application vendor]. I would say right now if we're supposed to be voting on this now I, I'm not ready to make a decision. If I had to be forced to I would say no.
What I would like -- and I understand Mr. McCormick you're here [from Flock] and look I was in [software] sales - but I'd rather have a CISO- type person talk to our CISO -- so I would ask Eric [Linton – City Manager] to have our IT director Ginger LePage do a presentation to the council on her findings. Looking at your SOC-2, your SOC-1 reports - looking at all the trust, privacy, data security, and governance gaps and so on and let me hear that from our IT director then let me hear that from our legal. And if it's in the terms and conditions specifically in the contract then we can go with that. If it's verbally we can't. It needs to be in writing in legal [terms & conditions in the contract].
So I I'm just a big process guy and I - we [City Council] - shouldn't have to understand your technology and topologies, and multifactor authentication, and the terms and conditions of license agreements, and no sale of data, and data sharing, and so on. We shouldn't have to be having that type of conversation here [to the City Council]. I'd rather have our IT director presenting that to us and having staff do the due diligence and say here's all of your concerns and [presenting findings with a] green, amber or red from our staff [in a] presentation. That's what I would propose.”
Video here: https://youtu.be/556mAErkhzQ?si=12m6tyjR_TbkpJf5&t=5275
My specific concerns & asks directed back to the Dunwoody City Manager, Eric Linton for action & next steps
I want to be clear: this is not about being anti-technology or anti-police. It’s about governance.
The Flock ecosystem now includes license plate readers, live cameras, drones, and 911 integration. That’s a significant public safety infrastructure. With that level of integration, we have a responsibility to ensure the contracts and data controls are airtight.
There are five areas that deserve deeper review:
First, our agreement incorporates online Terms & Conditions by reference. Those website terms can change. We need to freeze the governing version and ensure no amendments apply without written City approval.
Second, the contracts should explicitly prohibit secondary use of Dunwoody data — including AI training, product development, benchmarking, or commercialization — unless the City expressly approves it.
Third, we need clear sharing governance. Who can access our data? Which agencies are approved? Are nationwide sharing settings enabled? How often are those settings reviewed? That should be documented and audited.
Fourth, security controls must be mandatory and enforceable — especially multi-factor authentication for every user, clear audit logs, and defined breach notification timelines.
Fifth, the liability structure should not cap responsibility in cases of gross negligence or serious data security failure. Taxpayers should not bear that risk.
None of these issues mean the technology is ineffective. But they are governance issues that require structured oversight.
We can support public safety tools and insist on strong privacy protections at the same time. Those are not mutually exclusive.
Lastly, I'd like council to be presented with the city's internal governance, risk and control policies that permit access to these types of systems and data.