C-DRONE GUIDE · 17 AUGUST 2026
Sovereign or Chinese Drone: What Your Equipment Choice Means for a Mission on a Sensitive Site
A drone pilot responding to a tender for a power plant, a Seveso-classified site or a local authority may now find, buried in the technical specifications, an unusual requirement: equipment "not subject to extraterritorial legislation", or even an imposed manufacturer nationality. This is not a whim: it reflects real tensions around DJI, which dominates the professional market. What French law actually says in 2026, what a sensitive client checks in practice, and where to find an alternative.
Published on 17 August 2026, reviewed on 17 August 2026 — regulations in force as of August 2026.
DJI dominates the professional market, but the context shifted in late 2025
The vast majority of professional inspection and mapping drones used in France come from the DJI Enterprise range: a strong price-to-performance ratio, a mature sensor ecosystem (thermal, LiDAR, zoom), and mission-planning software that works. Nothing in French law bars a pilot from using this equipment for a professional civil mission: operator registration, appropriate training and professional liability insurance remain the only common-law conditions, whatever the aircraft's brand.
What has changed is the international context. In the United States, a clause in the 2025 National Defense Authorization Act required a security audit of DJI before 23 December 2025; that audit was not completed in time, and the company was added at the end of December 2025 to the Federal Communications Commission's "Covered List", which blocks new FCC authorisations for its equipment — without grounding aircraft already in service or making their use illegal. This US decision has no direct legal force in France, but it has a real knock-on effect: it feeds a wariness, among French clients who consider their missions sensitive, that is now showing up in technical specifications.
Sensitive sites: the scrutiny comes from the client, not a blanket law
To date, no French law requires "sovereign" equipment for civil drone missions in general, including on a sensitive site. What is on the rise is a case-by-case contractual requirement: some public-procurement specifications, notably for operators of vital importance (OIV — energy, water, telecoms, roughly 1,500 sites listed in France), defence-adjacent sites, or local authorities cautious about data, now spell out an equipment origin or a data-hosting arrangement. Our guide on buying drone services through public procurement explains how to read this type of clause in a technical specification document.
One frequent point of confusion is worth clarifying: the ongoing debate around the Résilience act and the military programming law, which aims to let private security staff neutralise an intruding drone above an OIV site, concerns unidentified drones flying over the site without authorisation — not the equipment of a duly mandated, declared service provider carrying out an inspection mission. The two topics cross paths in the news, but follow different logics: one is a passive-defence question against an outside threat, the other a question of trust in the subcontracting chain, closer to what our guide on the NIS2 Resilience Act and drone subcontractors covers.
What a sensitive client actually checks
Beyond the nationality printed on the shell, a demanding client mostly looks at the data chain: does the drone sync by default with a manufacturer server located outside the European Union? Does unlocking a geo-restricted zone (geofencing) go through an online account or a local certificate? Can firmware updates be verified and replayed without a permanent connection? On a consumer as much as a professional aircraft, these mechanisms usually exist for convenience, not malicious intent — but their mere existence is enough to worry a security officer who has to document their supply chain.
These concerns are not specific to one brand: the academic literature has long documented the security and privacy risks inherent to civilian drones in general. A landmark study by AlTawy and Youssef, published in 2017 in ACM Transactions on Cyber-Physical Systems, catalogues the vulnerabilities of command links, telemetry and video feeds common to these aircraft, whatever their manufacturer (see the study on Google Scholar). In practice, a provider meets these requirements by disabling cloud sync during the mission, working in local-storage mode, and supplying on request a data sheet tracing the equipment's origin and the path taken by the delivered data — an approach close to what is already expected for GDPR and drone data anonymisation.
French and European alternatives exist, with their own trade-offs
French manufacturers design and assemble professional inspection and mapping drones on national soil: that is the case for Innovadrone, based near Toulouse, whose industrial range (geomatics, thermography, technical inspection) equips clients including Eiffage, RTE and Onera. This type of equipment directly answers a requirement for full traceability from design to manufacture, without depending on a non-European supply chain.
The trade-off is real, and worth stating plainly to a client discovering the topic: the sensor catalogue is narrower than a global giant's, delivery times and spare parts can take longer, and the purchase price generally sits above Chinese equivalents — without a reliable, verifiable order of magnitude that can be stated here, since configurations vary widely. In practice, switching equipment only makes sense if the client explicitly requires it in their specifications or if the mission's context clearly justifies it: a pilot who invests in sovereign hardware without an identified need ties up capital for a still-narrow market. Our guide on which professional drone to buy covers the other selection criteria, by use case and budget.
What to remember when responding to a tender
For a drone pilot: never assume a sovereignty requirement appears in a tender — read it carefully, and absent an explicit clause, ask the client directly rather than guess. Keeping a data sheet tracing the origin and configuration of every aircraft in the fleet makes it easy to answer quickly the day the question comes up. For a client: state the requirement explicitly in the specifications rather than implying it — "equipment not subject to foreign extraterritorial legislation" or "data hosted within the European Union" are verifiable wordings, unlike a simple brand preference.
For the vast majority of missions — roof inspection, construction monitoring, real-estate photography, agricultural mapping — the question simply does not arise: equipment choice remains a technical and economic decision, as detailed in our guide on choosing a professional drone pilot. It only becomes relevant for a limited number of genuinely sensitive missions. Request a quote and mention, where relevant, any equipment-sovereignty or data-hosting constraint : it is the best way to get a suitable answer from the very first exchange.