A Security Setting Is Not a Security Verdict
The useful question is not whether every DJI drone is universally “safe” or “unsafe.” It is whether your exact aircraft, controller, software and data workflow meet the requirements of the mission, client and organization involved.
The RCMP’s technology audit identifies potential third-party application data-handling risks. DJI describes controls including Local Data Mode and on-premises deployment. Those are different kinds of evidence: one identifies concerns; the other describes manufacturer-provided controls. Neither, by itself, certifies your proposed operation.
This guide explains what the sources support, where their limits matter and what to request before buying. It does not approve a platform for sensitive work.
What deserves scrutiny
Where mission data travels, who can access it, which services connect externally, how copies are retained and whether your organization permits the equipment.
What is not enough
A reassurance from a seller, another agency’s deployment, a broad “secure” label or a mode name without configuration-specific evidence.
What the Evidence Does, and Does Not, Establish
The RCMP Audit of Emerging Investigative Technologies discusses third-party RPAS applications and the possibility that captured data could be recorded or stored automatically. It explicitly mentions Chinese-manufactured DJI equipment.
The audit also identifies gaps in procedures for collecting, transmitting, storing and disposing of personal information. That wider lifecycle matters: even a locally captured file can be mishandled after it leaves the aircraft.
These observations warrant investigation. They do not prove that every DJI aircraft sends mission imagery to China, establish that a particular flight was compromised or supply a current nationwide manufacturer ban.
| Evidence | Useful for | Not sufficient for |
|---|---|---|
| Agency audit | Understanding documented concerns and governance gaps. | Proving a specific data leak or certifying a present-day configuration. |
| Manufacturer documentation | Identifying intended controls and deployment options. | Independent proof that every component behaves as expected. |
| A security assessment | Evaluating its tested product, version, settings and threat model. | Automatically covering later firmware, different apps or added cloud services. |
| Another organization’s deployment | Showing a use case at a particular time. | Establishing your purchasing eligibility or security approval. |
Separate the decisions: technical risk assessment, organizational purchasing permission and mission approval are not interchangeable. A technical control does not override a prohibition in your contract or agency policy.
Local Data Mode: Useful Control, Defined Scope
DJI’s Pilot 2 public-safety guidance describes Local Data Mode as disabling internet connections between the Pilot 2 app and the internet. This is a manufacturer description of app behaviour, not a blanket certification of the controller, aircraft and every installed service.
Do not confuse operating modes
DJI’s M300 V3 firmware announcement distinguishes Standard, Restricted Network and Local Data modes. In that documented version, Restricted Network Mode still permits specified connected services, including maps, RTK and live broadcast. “Restricted” should not be read as “no network traffic.”
These are version-specific examples, not a promise that every current model exposes identical controls. Check the documentation and behaviour of the equipment you are actually evaluating.
Read assessment claims narrowly
DJI’s data-protection article quotes an FTI Consulting finding concerning application-generated data in Local Data Mode. Here, that statement is treated as a manufacturer-reported assessment finding. This guide has not independently evaluated the underlying test report or extended its findings to current equipment.
Test the complete operating procedure
Ask your security team to verify the exact mode, exceptions and external services, then test a representative mission using approved methods. Include startup, mission execution, shutdown, export and maintenance, not just a short disconnected hover.
Document what happens when an operator changes settings or reconnects the controller. A control is more useful when it can be consistently applied, checked and maintained.
Cloud Location and On-Premises Deployment Answer Different Questions
DJI’s FlightHub 2 FAQ describes public-cloud storage for users outside mainland China on AWS infrastructure in Virginia, United States, or Frankfurt, Germany. Do not infer Canadian data residency from the fact that an operator is based in Canada.
Confirm the specific service, account region, current terms and categories of information covered. A storage-region statement is not a complete explanation of support access, administrative access, backups or every related service.
Local hosting changes the responsibility boundary
DJI also describes a FlightHub 2 On-Premises deployment in which operational data is stored within organizational infrastructure. That is a deployment option to assess, not evidence that every DJI workflow is inherently local.
A local deployment still needs an owner for access management, updates, backups, monitoring and recovery. Before selecting it, request current compatibility, licensing, architecture and external-dependency details for the proposed system.
Storage location is one control, not the whole answer
Evaluate who can access the information, how access is recorded, what leaves the environment and how deletion works across copies. “Hosted locally” and “appropriate for this mission” should be separate findings in the approval record.
Follow the Data Beyond the Aircraft
Capture and field storage
Identify the imagery, coordinates, logs and other records your configuration produces. Inventory the aircraft, controller and removable media that may hold them.
Connected services
List mapping, correction, livestreaming, cloud and third-party applications used by the workflow. Record each service’s purpose and the information it needs.
Export and collaboration
Trace copies sent to workstations, processing tools, shared folders and clients. Establish authorized recipients and an approved transfer method.
Retention and retirement
Define retention rules, incident handling, backup treatment and disposal procedures. Include lost media, replaced controllers and equipment sent for service.
These are recommended review questions, not claims that every DJI product creates the same records or uses all these services. Your data-flow diagram should describe the actual configuration, including tools supplied by other vendors.
A disconnected flight does not stop someone from later uploading its files to an unapproved account. Likewise, a well-managed storage system does not automatically settle concerns about the flight application. Assess both ends of the workflow.
A Practical Pre-Purchase Review
Use the following sequence as a starting point for a review owned by your procurement, security and operational leads.
- Obtain the written requirement. Identify restrictions imposed by your organization, client or contract before comparing equipment.
- Describe the mission and information. State what you will capture, who needs it and what would happen if it were exposed or unavailable.
- Freeze the proposed configuration. Record aircraft, payload, controller, firmware, apps, services and planned network settings.
- Request an evidence package. Ask for current documentation, data flows, assessment scope, relevant terms and unresolved limitations.
- Validate representative behaviour. Have qualified staff test the configuration and document results, exceptions and residual concerns.
- Assign ownership and review triggers. Name who approves use, checks settings and reassesses changes in software, services or mission scope.
Record the conclusion precisely
A useful decision states what was assessed, for which mission, under which conditions and by whom. “Approved for this configuration and workflow” is more actionable than “DJI is secure.”
For related policy context, read our Canadian DJI restrictions explainer, the OPP policy briefing and what RCMP public records establish.
Supplier disclosure: Unmanned Canada sells DJI equipment. This article is not an independent security assessment, an agency endorsement or confirmation that a platform meets your procurement requirements.
Frequently Asked Questions
Does Local Data Mode mean the entire system is offline?
DJI describes it in terms of flight-app internet connections. Do not extend that description to every controller process, third-party app or later file transfer without checking the exact system.
Does the RCMP audit prove DJI leaked mission data?
The cited audit raises potential application data-handling risks and procedural gaps. It does not, in the passages relied on here, establish a specific compromised flight.
Is FlightHub 2 public-cloud storage automatically in Canada?
No Canadian storage location is established by the cited FAQ, which describes US or German AWS locations for users outside mainland China. Confirm your service and account configuration directly.
Does an on-premises system remove every security concern?
No. It changes the deployment and storage arrangement. Access, maintenance, external dependencies, exports and organizational acceptance still need review.
Can an offline setting override an agency’s purchasing restriction?
Do not assume so. Obtain the organization’s written determination. A technical mitigation and permission to purchase are separate decisions.
What should I request from a supplier?
Ask for documentation covering your exact configuration, data flows, connected services, assessment scope and limitations. Have your responsible reviewers decide whether that evidence is sufficient.
Start with the Mission and the Written Requirements
Unmanned Canada can help discuss equipment configurations and identify documentation to request. Bring your organization’s procurement and security requirements so unresolved approvals are clear before purchase.
Discuss Your RequirementsSources and Editorial Notes
- RCMP: Audit of Emerging Investigative Technologies, agency observations concerning third-party applications and information-handling procedures.
- DJI: Public-safety features and Pilot 2 Local Data Mode, manufacturer guidance.
- DJI: M300 V3 firmware update, historical, version-specific descriptions of network modes.
- DJI: How to protect drone data, manufacturer-reported assessment statement; not treated here as an independently reviewed test report.
- DJI FlightHub 2 FAQ, manufacturer storage-location information, Portuguese-language page.
- DJI: FlightHub 2 On-Premises & AIO, manufacturer deployment description.
Reviewed November 7, 2026. Historical documentation is identified where used. Manufacturer descriptions are attributed, not presented as independent validation. Features, terms and compatibility require confirmation for the exact product and version being considered.
General information, not legal advice, a security certification, procurement approval or flight authorization. Decisions belong with the responsible organizational authorities and appropriately qualified reviewers.
