GovernanceExpert Guide

How to Write a City Drone Privacy Policy Residents Will Trust

Drone programs are spreading across city police departments, and the pushback is spreading with them. Residents want to know what the drones record, how long the footage lives, and who gets to see it. A city that can't answer those questions in writing is in for a rough council meeting. Here's what the federal guidelines, the civil liberties groups, and the policing community each say a good policy needs, and a seven-part outline you can adapt.

Last reviewed: October 26, 2026

aerial view of a suburban neighborhood from drone height

Photo: Zac Gudakov / Unsplash

From Jonathan Dockrell, CEO & Co-Founder

The following is a personal take from our CEO on a question city councils and police chiefs keep raising about drone programs. We publish these because a privacy policy written before the controversy is far cheaper than one written during it.

The one-paragraph version

No federal rule tells a city how long it can keep drone footage or what it must publish about its flights. The closest federal document is a set of voluntary privacy guidelines from 2016, and they say they aren't a template for future laws. They also exclude emergency response, which is where most first-responder drone calls fall. So the policy is yours to write. The good news is that the civil liberties groups and the policing community disagree on a lot, but they overlap on a core: a written policy, transparency, accountability, and limits on how long data is kept. Build around those, and you have a policy both sides can read.

Why privacy is now a council issue

The ACLU's 2023 report on drone first-responder programs said more than 1,400 U.S. police departments were using drones. It said Chula Vista, California, started the country's first drone-as-first-responder program in 2019 and had logged more than 14,000 flights. Chula Vista itself dates its operations to October 2018. Those numbers are from 2023 and have almost certainly grown.

When drones respond to 911 calls across a city, people ask a fair question. If a drone is overhead, what is it recording, and where does the video go? A city council that can't answer in plain English loses trust fast. And trust, once lost, takes a program down with it.

What the voluntary federal guidelines say, and don't

In 2016, a federal agency convened drone companies, privacy groups, and trade groups. They agreed on voluntary best practices for drone privacy, transparency, and accountability. They're worth reading because they're specific.

For operators, they say to:

  • Publish a privacy policy no later than the start of data collection
  • Cover purposes, data types, retention, sharing, complaint methods, and how the operator handles law enforcement requests
  • Give people notice of the general time and area of flights where practicable
  • Avoid persistent, continuous collection unless there's a compelling need or consent
  • Keep data no longer than reasonably necessary
  • Set up a way for the public to raise privacy and security concerns, including deletion requests

Now the limits, and they matter. The document says the practices don't apply to drones used for emergency response. It says they aren't a legal standard of care, and aren't meant as a template for future mandatory laws. Law enforcement isn't listed as an exclusion, but the document is written for commercial and private operators, not police programs.

As someone who watches this space closely, I'd treat these as a good checklist and nothing more. They were never meant to bind a city.

The FAA and privacy

The FAA's fact sheet on state and local drone rules addresses privacy, but it focuses on rules cities set for other people's drones. It says a privacy-based ban on drone flights over an entire city would very likely be preempted. It also says a narrower rule, such as limiting lower-altitude flights over places where people expect privacy, like parks or schools, is likely to hold. And it says rules on harassment, trespass, and reckless endangerment remain with state and local governments.

Your own city drones are a different case, and the fact sheet doesn't squarely address them. My read is that a city has wide room to set rules for its own program, since those are choices about how its employees use a tool.

One more federal piece, since it comes up. The Remote ID rule says drones broadcast identifying and location information while flying. It says that helps the FAA, national security agencies, and law enforcement identify aircraft and locate who's controlling them. What it doesn't do is set retention or use limits for city programs. Don't let anyone tell you Remote ID covers your privacy policy. It doesn't.

What the ACLU asks for

The ACLU's 2023 report, written by Jay Stanley, is the most detailed civil liberties checklist out there. Its main asks:

  • A city council vote to approve the program and give its policies legal force
  • Use limited to emergencies first, then the most serious ones
  • A warrant when a drone would intrude on a reasonable expectation of privacy
  • No recording on the way to a call
  • Prompt deletion of sensitive footage, such as from domestic violence or mental health calls
  • No AI analytics on the footage
  • Public posting of the time, purpose, destination, and route of every flight
  • Contracts that bind any vendor with access to the data to the department's policies

The ACLU's headline position is stricter than the checklist. It recommends that communities wait before starting new first-responder programs until the picture is clearer. You can disagree with that and still borrow the checklist.

What the other side asks for

A white paper published in April 2025 by a Rutgers policing center, a law enforcement training group, and a life safety alliance takes the opposite view on pausing. It argues for keeping the programs and governing them with policy. Co-author David Grantham put it this way in the release announcing the report: "We need thoughtful policy, not paralysis." The report draws on the Five Cs, a framework from DRONERESPONDERS that includes privacy, transparency, accountability, and community engagement. It also points to data retention limits and privacy safeguards in a sample department policy.

Here's what strikes me. Both camps want a written policy, public reporting, and retention limits. They split on whether to start the program before those exist. Your council can settle that argument by putting the policy first.

Honolulu: a live example

The Honolulu Police Department started a first-responder drone pilot on August 5, 2026, covering two districts. The next day, the ACLU of Hawaiʻi called on the department to halt it until the city council passes binding oversight legislation.

According to the ACLU of Hawaiʻi, the department's policy bars random surveillance but has no warrant requirement, no independent audits, and no binding limits on footage retention or sharing. It also says the department hasn't committed to banning facial recognition. Those are the group's claims about the policy, and I haven't seen the policy myself.

The pattern is worth noting whichever side you favor. The fight isn't about whether drones help. It's about whether the rules are written down, enforceable, and approved by elected officials. A city that answers those three questions first avoids most of this.

The seven parts of a city drone policy

This outline is my synthesis of the sources above. It's analysis, not a legal standard. Adjust it with your attorney.

  1. Purpose. List the specific uses allowed, starting with emergencies. Say what's not allowed, such as random or routine surveillance.
  2. Authorization. State when a supervisor or a warrant is required. Say who can approve a flight.
  3. Recording and retention. Say when cameras record. Set short retention periods, with faster deletion for sensitive calls. Name the exceptions, such as active investigations.
  4. Limits on analysis. Decide in writing whether facial recognition or other biometric tools are banned. Residents will ask.
  5. Public reporting. Publish each flight's time, purpose, and general location, with a monthly summary. A public flight log is the single easiest trust-builder.
  6. Sharing and vendors. Say who can receive footage. Bind any vendor to the policy by contract.
  7. Oversight. Require a council vote, regular outside audits, and a complaint process with a named contact.

From a founder's perspective, the cheapest item on that list is the public flight log. It costs a spreadsheet or a web page and answers the question residents ask first: where were the drones today?

What city teams should do now

  • Draft the policy before the program starts, not after the first complaint.
  • Hold a public meeting and publish the draft ahead of it.
  • Put the final policy to a council vote so it has legal force.
  • Decide your retention periods now, and write them down in days, not "as needed."
  • Start the public flight log on day one.
  • Ask your attorney whether your state's laws add warrant or data rules on top of this.

Where I think this goes

I'll flag this section as forecast, since none of it's settled. As someone building in the drone economy, I expect more councils to demand written drone policies before they approve funding, because the Honolulu-style dispute is easy to see coming. I think public flight logs will go from a nice extra to an expected feature within a few years.

I also expect the policing community and the civil liberties groups to keep arguing over warrants and pauses. What I don't expect is a federal rule on city drone data anytime soon. Nothing I found points that way. That leaves the work to cities, which is both a burden and an opportunity.

Conclusion

A good city drone policy isn't complicated. It says what the drones are for, what they record, how long the footage lives, who sees it, and how residents can check. Write that down, publish it, and let the council vote on it. The cities that do will spend their time defending a program instead of defending a secret.

Related reading: The DFR Compliance Playbook - the policy and oversight documents a department needs before launch. Drone as First Responder (DFR) Programs: A City Guide - how these programs work, and the privacy risks cities weigh first. How to Write a City Drone Ordinance - rules for other people's drones, including privacy clauses. The FAA's DETER Program - what the FAA's settlement program leaves to local teams.

Primary sources and industry analysis

Disclaimer

This piece is informational and reflects the federal documents, civil liberties statements, and policing white paper listed above as of October 26, 2026, the date this piece was last reviewed. It isn't legal advice. State laws on police drones, recordings, and public records vary, and a city's authority over its own program depends on that law. If you're drafting a drone privacy policy, talk to your city attorney.

Frequently Asked Questions

Questions from city teams.

Answers for councils, police leadership, and city attorneys.

Is there a federal rule on how long a city can keep drone footage?

Not that I found. The federal privacy guidelines from 2016 are voluntary and exclude emergency response.

Do the ACLU and police groups agree on anything?

Yes. Both call for written policies, public transparency, and retention limits. They split on whether programs should start before those exist.

What's the easiest first step?

A public flight log. It shows residents what flew, when, and why, with little cost.