Get email alerts on the Privacy Security topic
No spam. Unsubscribe anytime.
Committee presses for security and privacy safeguards before drone deployment
Summary
Committee members asked for a security configuration review, firm contract terms on data handling, explicit prohibitions on facial recognition and license‑plate reading, and public flight logs before the drone is deployed.
Committee members focused on technical safeguards for the proposed drone, recommending an audit of authentication and permissioning in the Axon tenancy, single sign-on and multifactor authentication, and a reviewed data‑processing agreement with the vendor. Jay and other staff confirmed that Axon currently tracks access logs and that the vendor will provide training and maintenance.
Matt recommended opting out of any vendor 'customer experience improvement' data‑sharing program unless explicitly approved by the town and asked that the committee receive notification of any vendor breach. "Recommend we opt out of that unless, you know, the town explicitly approves," Matt said. The committee requested a 30‑day predeployment checklist and periodic public reviews to build resident trust.
AI generated
The text on this page is AI generated. Summaries, highlights, analysis, and video transcripts are all produced from the original source material.
AI can make mistakes, so if you spot one, and we will fix it for everyone.
Note: the source content is unaltered by us. Any content source we link to, be it a video, an audio recording, or a document, is presented exactly as its publisher released it. That publisher is usually a government body, sometimes an individual official or another organisation.
