Phone: (202) 833-1460 Washington DC Farragut North Metro

Privacy safeguards for drones at Australian public protests

Privacy considerations when conducting overt surveillance of public protests extend beyond placing a drone in plain sight. A police, council or emergency-service aircraft above a crowd in Melbourne, Sydney, Adelaide or a regional town may be visible while its sensors, recordings and sharing systems remain hidden. That imbalance can turn a safety tool into a source of suspicion.

Overt operation can support trust when the agency explains what the drone is doing, who controls it and what happens to the footage. In Australian public debate, a “fair go” and being “upfront” carry familiar weight, yet a visible aircraft does not disclose persistent tracking, biometric analysis or onward sharing with another agency.

Privacy should therefore be an operational control. Agencies need to define the mission, test necessity and proportionality, restrict collection, limit access and retention, and provide oversight. These safeguards matter when crowds include families, journalists, people seeking health care or participants whose attendance could expose them to harm.

Why overt surveillance still creates privacy risk

An aerial camera can follow individuals across an event, link them to vehicles or other datasets and reveal patterns unavailable from ground level. Even without facial recognition, timestamps, movement routes, clothing and interactions may support later identification. Thermal imaging adds further inference, particularly where illness, housing status or other vulnerabilities can be inferred.

Public space is not a privacy-free zone. A reasonable expectation of privacy depends on context, and a dense protest can limit practical alternatives. Agencies should also consider peaceful assembly, the chilling effect of monitoring, and the interests of bystanders who never joined the event. Overt means observable, not consequence-free.

Follow the law in each Australian jurisdiction

Australian privacy law is divided across jurisdictions. The Commonwealth Privacy Act 1988 generally applies to Commonwealth agencies, while police and public-sector bodies in NSW, Victoria, Queensland and elsewhere work under their own applicable statutes, policies and law-enforcement exceptions. Relevant examples include the Privacy and Personal Information Protection Act 2014 (NSW), Privacy and Data Protection Act 2014 (Vic) and Information Privacy Act 1992 (Qld).

Surveillance-device and listening-device laws may also govern particular capabilities, regardless of whether the platform is airborne. Requirements for authorisation, notices, record keeping or restrictions differ, so an agency should not assume that public filming by an attendee has the same legal status as agency-led aerial surveillance.

CASA rules add an aviation layer: registration thresholds, remote operator certificates, operator accreditation and activity approvals depend on the aircraft, location and mission. In Australia’s public-safety market, services may come from in-house crews or council-contracted providers, so procurement documents must assign privacy, security and deletion duties. Obtain current CASA, legal, privacy and information-security advice before approval.

Build privacy into mission planning

Create a written mission and privacy impact assessment before deployment. State the safety problem, specify the sensor and any analytics, identify who may be observed, and record why a drone is less intrusive than ground cameras, observers or coordination with event organisers. Define collection limits, exclusion areas and conditions that would pause the mission.

Map the data lifecycle rather than only the flight. Decide what is collected, viewed in real time, recorded, retained, shared and ultimately destroyed. Restrict system access by role, encrypt transfers and logs, and set short, event-specific retention periods unless a lawful investigation justifies an extension.

Use a decision log and a named authorising officer. Test likely scenarios, including crowd surges, missed GPS links, accidental recording of nearby homes and requests for footage. A post-event review should record deviations, deletion confirmations and any second use of the material.

Keep the operation visible and proportionate

Visible aircraft should be supported by visible governance. Post notices in plain language stating the agency, purpose, sensors, operating period, contact point and whether footage is being recorded. Where safety permits, brief organisers and participants before launch, and explain that people may ask questions without that interaction being recorded.

Keep each capability tied to the mission. Avoid thermal imaging, facial recognition and individual tracking unless necessity, legal authority and safeguards are documented. Narrow fields of view where feasible, avoid nearby private premises, and never treat a public event as blanket permission to retain every detail.

Make safeguards operational and easy to audit

Transparency works best when it can be tested. The boundary between encouragement and manipulation described in ethical influence in yoga offers a useful parallel: officials should explain the protective purpose of surveillance without claiming that visibility makes collection automatically necessary or acceptable. Public-safety messaging should invite scrutiny rather than pressure people into acquiescence.

Publish the agency’s protocol, incident commander’s authority, complaint route and review process. Give community liaison officers a prepared explanation for questions on the day and establish a process for media enquiries. After the event, publish a short outcomes statement describing what was collected, how it was used and whether it was deleted.

Operational recommendations

Commit to accountable practice before deployment

Choice of platform should be the final operational decision, not the first. The following comparison helps commanders select the least intrusive option that meets a defined safety need.

Deployment option Main privacy risk Additional controls Appropriate fit
Ground coordination and human observers Less persistence, but bystanders may still be recorded Clear briefing and defined sightlines Routine awareness where ground teams can manage the area
Overt drone with live situational awareness only Reduced storage risk, though operators may still identify individuals No routine recording and restricted live access Broad safety overview without an evidence-retention need
Overt drone recording video Identification and movement tracking across the event Defined retention, access logs and authority for evidence use A specific, time-limited need requiring recorded material
Thermal or biometric analysis Sensitive inferences and possible false matches Higher-level authorisation, testing, human review and oversight Exceptional necessity rather than default monitoring

A recorded flight requires stronger controls than live situational awareness, and analytics require stronger controls still. Every deployment should have a named authoriser, documented legal basis, audit trail and route for handling public complaints. A drone should not become the default because it offers a convenient view of the crowd.

Ahead of the next demonstration, agency leaders should approve and publish a one-page privacy protocol, brief every pilot and controller on its limits, and schedule a post-event audit. Make privacy accountability a standing condition of public-safety drone operations, so transparent practice becomes routine rather than a response to concern.