Privacy policy

1

Data controller

DRONOPS SAS acts in two capacities, depending on the data. It is the controller of the data it processes on its own account: the public site and early access, sign-in accounts, billing, communications to users, the partner programme, platform security and cookies. For this processing, the controller is:

DRONOPS SAS
119 Boulevard du Président Wilson, 33000 Bordeaux, France
SIREN : 102 986 635
Email : rgpd [at] dronops.io

For the data that the operator of uncrewed aircraft records on the platform — its remote pilots' files, flights and missions, declarations and authorisation requests, CERFA forms, MANEX, documents sent to the authorities and its account's activity journal —, the controller is the operator: article UAS.SPEC.050 of Regulation (EU) 2019/947 requires it to keep these records. DRONOPS SAS processes them as processor, on its behalf and on its instructions, under the data processing agreement annexed to the terms of use and sale.

2

Data collected

DRONOPS collects the following categories of data, depending on whether you use the public site or the application:

Data	Nature	Source	DRONOPS's role
Public site and early access — email address, registration date and time, consent	Required	Early-access form on the public site	Controller
Sign-in account — title, first name, last name, email address, phone, language, password (hashed), last sign-in date, paired mobile devices	Required	Account creation, then use of the application	Controller
Kbis representatives — name and capacity of the directors and representatives listed on the client company's Kbis extract, 30 at most; no email address, no postal address, no date of birth, no phone	Required	Entered by the operator, from an extract the trade register already publishes openly	Processor for the operator
Remote pilot file — title, first name, last name, email address, phone, date and place of birth, postal address, role, status, cumulative flight hours, licence numbers, scans of titles and certifications	Required except the phone, the date and place of birth and the postal address	Entered by the operator or by the remote pilot, copied to each of the pilot's operators. The date of birth is used to check the minimum age of article 9(1) of Regulation (EU) 2019/947 and is printed on the CERFA declaration filed with the prefecture; it stays optional.	Processor for the operator
Flights and missions — date, time and place of take-off and landing of the AIRCRAFT, actual duration, crew, occurrences, checklists, batteries used	Required	Entered and recorded during operations. This is the AIRCRAFT's location: the remote pilot's own position is not collected.	Processor for the operator
Documents transmitted to third parties — copies of documents (insurance, titles, authorisations)	Required	A copy frozen at the moment it is transmitted to an airspace manager or an authority, in support of a flight authorisation request	Processor for the operator
Logs — customer and back-office activity journal (author, author's email address, date, action, object touched, IP address) and server technical logs	Automatic	System	Processor for the operator's activity journal; controller for the back-office journal, the takeover journal and the technical logs

DRONOPS does not collect any sensitive data within the meaning of Article 9 of the GDPR and does not carry out any automated profiling.

3

Purposes and legal bases

Purpose	Legal basis	Description	DRONOPS's role
Providing the service	Performance of the contract (art. 6.1.b)	Opening and keeping your account, preparing and following your missions, managing your fleet	Controller for the sign-in account; processor for the operator's missions and fleet
Regulatory record of the remote pilot and of flights	Legal obligation of the operator (art. 6.1.c)	Keeping, on the operator's behalf, the records article UAS.SPEC.050(1)(g) of Regulation (EU) 2019/947 requires of it	Processor for the operator
DGAC and préfecture declarations, authorisation requests	Legal obligation of the operator (art. 6.1.c)	Filing, in the operator's name, declarations and flight authorisation requests, with the attachments that accompany them	Processor for the operator
Billing and collection	Performance of the contract (art. 6.1.b)	Issuing the invoices for your subscription and collecting them	Controller
Access and modification journal	Legal obligation of the operator (art. 6.1.c) for its activity journal; legitimate interest of DRONOPS (art. 6.1.f) for the back-office journal and the takeover journal	Knowing who wrote what and when, as a security measure under article 32 GDPR	Processor for the operator's activity journal; controller for the back-office journal, the takeover journal and the technical logs
Early access and product communications	Consent (art. 6.1.a)	Telling you when the service opens, sending you news about its progress and, if you open an account with the same address, granting you the early-access offer	Controller
Communications to application users	Legitimate interest (art. 6.1.f)	Informing you, as a professional user, of changes to the service you use. You may object at any time from « My account » or through the unsubscribe link in every e-mail.	Controller
Partner attribution and commission	Legitimate interest (art. 6.1.f)	If you arrived through a partner's link or code, linking your account to that partner and computing the commission owed to them on your subscriptions. The partner receives, on its monthly statement, a customer reference that tells it nothing about who you are, never your name, and the amounts billed excluding VAT that its commission is based on; nothing else. To count the openings, visitors and signups of each partner link, every opening is written to a log: the code, the time, the landing page, the device type (computer, mobile or tablet) and a fingerprint of the IP address computed with a key that changes every day of the French calendar, never the address itself. The robots that build the preview of a shared link are not logged.	Controller

How consent is collected: By submitting the early-access form on the public site, you agree to receive communications from DRONOPS about the progress of the platform. This notice is displayed explicitly below the form submission button, in accordance with CNIL recommendations. That consent covers this form alone: each other processing described above rests on the legal basis given on its row.

You may withdraw your consent at any time via the unsubscribe link in each email or by contacting rgpd [at] dronops.io.

4

Retention period

Data	Duration	Reason
Remote pilot file — identity and qualifications	At least 3 years	Leaving the organisation, or changing position inside it — UAS.SPEC.050(1)(g)(i)
Competence file — licences and scans of titles	3 years	Deactivation of the remote pilot. A remote pilot nobody deactivates is never swept: a departure is recorded by deactivating the file.
Recorded flights and missions	At least 3 years	The information being recorded — UAS.SPEC.050(1)(g)(iii)
Copies of documents transmitted to managers and authorities (except the filed CERFA and the town hall request, below)	90 days after the mission reaches a terminal state, and at most 3 years after transmission	The terminal state of the mission (completed, not flown, cancelled); the hard bound counts from the transmission. Whichever falls first wins.
Sign-in account	Term of the contract	Closure of the customer account
Kbis representatives (name, capacity)	As long as the operator keeps them	Nothing expires the list; these entries are erased when the customer account is closed, except in the signed editions of the MANEX (see below)
Operator's activity journal (what is written in the customer account, including during a takeover)	3 years	The event. Legal obligation: this journal protects the records the operator must keep under UAS.SPEC.050(1)(g), and it is kept as long as they are.
Back-office journal and takeover journal	365 days	The event
Journal of calls to the authorities' and Stripe's APIs (body sent and response received)	365 days, whatever the outcome of the call	The call. An erasure request does not reach these lines: they are the trace of an act performed before a French authority on a customer's behalf, or of a billing exchange with Stripe.
Journal of e-mails sent by DRONOPS (recipient's address, subject, date and status of the sending; never the content of the message)	The last 20,000 e-mails sent, all recipients together	A number of e-mails, not a period: each new e-mail sent pushes out the oldest. An erasure request does not reach these lines: they are the proof that an e-mail was sent.
E-mails that never left — sendings abandoned after several attempts: recipient, subject, reason for the failure and a copy of the message, kept so that it can be sent again	90 days	The failed sending. An erasure request deletes them too.
Names in the MANEX revision history and in its signed editions (organisation chart, accountable manager, emergency contacts, remote pilots, revision history), with the telephone number and e-mail address of emergency contacts and remote pilots, and the remote pilots' certificates (number and dates)	3 years after it leaves service	Leaving service: for an edition, its replacement by a newer signed edition; for the edition in force and the revision history, the closure of the customer account, never while the account is open. An erasure request does not reach this data: the signed MANEX is an enforceable document handed to the DSAC.
CERFA filed with the prefecture — the name of the person who sent it, recorded at sending, and everything the declaration prints: the accountable manager's last name, first name and role; the operator's contact telephone number and e-mail; the commanding remote pilot's title, last name, first name, telephone number, e-mail, date and place of birth and postal address, as the contact on the day of the flight; each second remote pilot's last name, first name, telephone number, e-mail, date and place of birth and postal address (three at most); for a sole trader, his address; the handwritten signature or stamp affixed in section 7. It is handed to the mission's remote pilots, external ones included.	3 years after the mission's terminal state	The mission's terminal state (completed, not flown, cancelled); an open mission or one awaiting closure does not start the clock. Until then, neither an erasure request nor the closure of the customer account reaches this data: the filed CERFA is a signed document handed to the prefecture, and rewriting it would amount to falsifying it.
Request sent to the town hall (temporary occupation of public land) — the name of the person who sent it, the message sent and the letter, which prints the commanding remote pilot, the operator's contact telephone number and e-mail, the name and role of the manager under the signature, and, for a sole trader, his name and address	3 years after the mission's terminal state	The mission's terminal state (completed, not flown, cancelled); an open mission or one awaiting closure does not start the clock. Until then, neither an erasure request nor the closure of the customer account reaches this data: the request sent is a document handed to the town hall, and rewriting it would amount to falsifying it.
Server technical logs	180 days	The event. CNIL recommendation on event logs (deliberation no. 2021-122).
Payment traces	365 days	The event
The subscription's customer and invoices, held at Stripe: company name, e-mail address of the account that subscribes, postal address and intra-community VAT number	At least 10 years	The invoice. Accounting obligation: an invoice and its supporting documents are kept ten years (article L123-22 of the French Commercial Code). An erasure request does not reach this data.
Partner attribution and commission: the link to your account, the account name and the customer reference, with the partner, the code, the dates and the amounts excluding VAT	10 years after the end of the commission period or the last commission line, then anonymisation	The commission period. Accounting obligation: the statements and the transfers to the partner are kept ten years (article L123-22 of the French Commercial Code). At the end, the link to your account, its name and the customer reference are erased; the partner, the code, the dates and the amounts remain, with no way to tie them back to you.
Partner link log: code, opening time, landing page, device type and fingerprint of the IP address	25 months	The opening of the link: the 24 months of the commission period plus a margin.
Early access — active prospect	At most 3 years	The pre-registration or the last contact, whichever is later; opening an e-mail is not a contact. At that term, the registration is erased at DRONOPS and from the Brevo list.
Early access — address never confirmed	6 months after the last reminder	An address typed into the form but never confirmed from its mailbox is erased at that term, and its confirmation link stops working. When no reminder was sent, the term runs from the pre-registration.
Early access — after unsubscription	3 years	The unsubscription, as read at Brevo. The address is kept so that you are not written to again, the minimum the CNIL recommends, then erased at DRONOPS and at Brevo.
Account never confirmed	30 days	Creation of the account
Terminated customer account — period during which the account remains accessible, before its closure	30 days	The termination pronounced in the back office. Nothing is erased during that period.

A period preceded by “at least” is a regulatory minimum: nothing erases the data when it ends. A row with no period in days or years is erased by the event its reason names, and by that alone. After the other periods, data is permanently deleted or irreversibly anonymised.

5

Data recipients

Your data is processed by DRONOPS SAS and passed to the following recipients, each for the purpose stated and only insofar as you use the function concerned:

Sub-processors

These providers process data on behalf of DRONOPS and on its instructions, including, as sub-processors, the data DRONOPS processes on behalf of operators.

Sub-processor	Role	Location
Brevo SAS formerly Sendinblue	Email platform — contact management and communications dispatch. The contact record we send carries your first and last name, your e-mail address, your language, your role and your operator's name, its département, its fleet size, its plan and the date you last signed in.	🇫🇷 France — EU
OVH SAS	Site hosting and technical data storage	🇫🇷 France — EU
Stripe Payments Europe, Limited	Subscription payments — checkout and invoicing Stripe also processes some of this data on its own account, notably against fraud and for its legal obligations: see Stripe's privacy policy.	🇮🇪 Ireland — EU
MapTiler AG	Basemap tiles, fetched from our servers: your IP address is never sent to it	🇨🇭 Switzerland — outside the EU

Third-party services called by your browser

These services receive nothing from our servers: your browser contacts them to display the page, and they receive your IP address as a result. They act as independent controllers, under their own privacy policies.

Third-party service	Role	Location
OpenStreetMap OpenStreetMap Foundation	Basemap tiles drawn by your browser	🇬🇧 United Kingdom — outside the EU
IGN French national geographic institute	Aeronautical and relief layers, and ground elevation under a flight zone (Géoplateforme)	🇫🇷 France — EU
data.gouv.fr API Adresse and API Découpage administratif	Address search and identification of the commune under a point on the map	🇫🇷 France — EU
YouTube Google Ireland Limited	Video player of the Tutorials screen, loaded only when you start a video (youtube-nocookie.com)	🇮🇪 Ireland — EU, with processing in the 🇺🇸 United States
neway data AG	VFR aeronautical chart layer	🇱🇮 Liechtenstein — EEA

Third-party services called by the mobile app

These services receive nothing from our servers: the app installed on your phone contacts them, and they receive your phone's IP address as a result.

Third-party service	Role	Location
OpenFreeMap Hyperknot Software Kft.	Mobile app basemap, drawn tile by tile: it receives the phone's IP address and the map areas viewed	🇭🇺 Hungary — EU
Expo 650 Industries, Inc.	Mobile app updates, checked when it opens: it receives the phone's IP address, its operating system, the installed app version and a random token	🇺🇸 United States — outside the EU

Authorities and public bodies

These recipients receive, in your name and through us, the declarations and requests you file with them.

Recipient	Role	Location
DGAC AlphaTango	Flight declarations and notifications filed in your name	🇫🇷 France — EU
Clearance USSP service provider	Filing of flight intentions with air navigation services, when you use that function	🇫🇷 France — EU
Annuaire des entreprises French State	Verification of your organisation SIRET number at signup	🇫🇷 France — EU
Prefectures	CERFA 15476*04 declarations filed in your name with the prefecture, by e-mail	🇫🇷 France — EU
Town halls	Requests for temporary occupation of public land sent in your name to the town hall, by e-mail	🇫🇷 France — EU

The sub-processors DRONOPS uses are bound to DRONOPS SAS by data processing agreements compliant with Article 28 of the GDPR. Where DRONOPS SAS is itself the operator's processor, these providers are its sub-processors, authorised by the data processing agreement annexed to the general terms. Your data is never sold or transferred to third parties for commercial purposes.

6

Transfers outside the European Union

Your data is hosted in France, at OVH. Some of the recipients listed above are however established outside the European Union: the table below states, for each, the country concerned and what governs the transfer.

Recipient	Country	Transfer safeguard
Stripe	🇮🇪 Ireland — EU, with processing in the 🇺🇸 United States	Data processing agreement signed with the provider, incorporating the European Commission standard contractual clauses. The provider contracts from Ireland and may involve its United States establishment.
OpenStreetMap	🇬🇧 United Kingdom — outside the EU	Adequacy decision of the European Commission (Implementing Decision (EU) 2021/1772, extended until 27 December 2031 by Implementing Decision (EU) 2025/2574): the United Kingdom provides a level of protection recognised as equivalent to that of the Union.
Expo	🇺🇸 United States — outside the EU	Adequacy decision of the European Commission for companies certified under the EU-US Data Privacy Framework (Implementing Decision (EU) 2023/1795): 650 Industries, Inc. states that it is certified under this framework; its status can be checked on dataprivacyframework.gov.
YouTube	🇮🇪 Ireland — EU, with processing in the 🇺🇸 United States	Adequacy decision of the European Commission for companies certified under the EU-US Data Privacy Framework (Implementing Decision (EU) 2023/1795): the provider states that it is certified under this framework; its status can be checked on dataprivacyframework.gov.
MapTiler AG	🇨🇭 Switzerland — outside the EU	Adequacy decision of the European Commission: Switzerland provides a level of protection recognised as equivalent to that of the Union.

You may ask us for a copy of the safeguards applicable to these transfers by writing to rgpd [at] dronops.io.

7

Your rights

In accordance with the GDPR and the French Data Protection Act, you have the following rights over your personal data:

Right of access Obtain a copy of the data we hold about you

Right to rectification Correct inaccurate or incomplete data

Right to erasure Request deletion of your data ("right to be forgotten")

Right to object Object at any time to processing for prospecting purposes

Right to restriction Temporarily freeze the use of your data

Right to portability Retrieve your data in a structured, machine-readable format

Withdrawal of consent Withdraw a consent you gave at any time, without affecting the processing carried out before the withdrawal

Post-mortem instructions Set instructions on the retention, erasure and disclosure of your data after your death (Article 85 of the French Data Protection Act)

If your data was recorded by an operator that uses DRONOPS — your remote pilot file or the flights you took part in, for example —, address your request first to that operator, which is the controller. If you send it to us, we forward it to the operator without delay and help it respond.

To exercise these rights, contact us at rgpd [at] dronops.io. We will respond within one month of receiving your request. This period may be extended by two further months where necessary, taking into account the complexity and number of requests; we will then inform you within the first month, with the reasons for the extension. We may ask you to verify your identity where we have reasonable doubts.

8

Cookies No tracker without consent

Until you have agreed to anything, the site places only the cookies strictly necessary for it to work, listed in the first table below. No advertising targeting cookie is used.

Strictly necessary cookies, exempt from consent

Cookie	Type	Duration	Purpose
__Secure-DRONOPS_SESSION_*	Technical	Session — deleted when the browser closes, and after 8 h of inactivity at the latest	Keeps your session during the visit: sign-in, chosen language, messages shown only once.
__Secure-DRONOPS_SESSION_*_REMEMBER	Technical	30 days, extended on every visit — deleted when you sign out	Keeps you signed in on this browser once the session has ended. Set only if you tick "Stay signed in" when signing in.
__Host-*	Security	Deleted as soon as the form is submitted	Checks that a submitted form comes from a page of this site and not from a third-party one.
dronops_device	Security	30 days, extended on every sign-in	Recognises this browser after a successful sign-in, so it can still sign in while repeated attempts from elsewhere lock your account. It holds no personal data and does not keep you signed in.
dronops_target_path	Technical	Deleted as soon as you sign in or sign out, and after 8 h at the latest	Remembers the page you were opening when your session had expired, to bring you back to it once you sign in again. Set only in that case.
cc_cookie	Technical	6 months	Stores the decision you make on this panel, so that you are not asked again on every page.
mercureAuthorization	Technical	Session — deleted when the browser closes; the authorisation it carries expires after one hour and is renewed while you use the application	Allows real-time display of updates to your missions while you are signed in. Placed only in the application, once you are signed in.
dronops_trial_chip_dismissed	Technical	30 days; the banner may then reappear	Remembers that you closed the offer banner shown under the top bar, so that it is no longer shown. A display preference you ask for yourself; placed only in the application, once you are signed in.

Cookies placed only with your consent

Cookie	Type	Duration	Purpose
DRONOPS_REFERRAL	With your consent	Depends on the link: usually 30 days, 13 months at most	Remembers the code of the partner link you arrived through, to offer it when you sign up. Set only if you accept the « Link that brought you » category, and erased as soon as you withdraw that consent.

Strictly necessary cookies are exempt from consent (Article 82 of the French Data Protection Act, CNIL guidelines of 17 September 2020). The others are placed only once you agree, which the banner asks for on your first visit. The “Cookies” link at the foot of every page reopens that choice at any time.

Today, no audience measurement tool and no support chat is in service on the site: should either become so, it will be named here, with its publisher and what it stores on your device, before it places anything.

9

Contact & complaints

For any question regarding the protection of your personal data:

DRONOPS SAS — Data protection contact
119 Boulevard du Président Wilson, 33000 Bordeaux
Email : rgpd [at] dronops.io

If you believe your rights are not being respected, you may lodge a complaint with the Commission Nationale de l'Informatique et des Libertés (CNIL) :

CNIL — 3 Place de Fontenoy, TSA 80715, 75334 Paris Cedex 07
Website : www.cnil.fr

Table of contents