MavenPilot Privacy Policy

This Privacy Policy explains how MAVEN VERSE S.R.L. ("Maven Verse", "we", "us" or "our") collects, uses, stores, shares and deletes personal data when you use your MavenPilot account, our account-based services and features available without an account: MavenRoute, MavenCloud, MavenShare and MavenScene (together, the "Services"), as well as our mobile apps and the website www.mavenpilot.com.

In short. We use your data to provide and protect your account and the Services, and to understand their use as explained below. Your missions, photographs and results are yours: we do not sell them, we do not use them for advertising or profiling, and we do not use them to train artificial-intelligence models. We send promotional emails only if you ask for them. Our account databases and your uploaded files are stored in the European Union; some providers also process limited data elsewhere as explained below. You can delete your account at any time, subject to the retention exceptions below.

1. Who is responsible

For the processing described in this Policy, the controller is:

MAVEN VERSE S.R.L.
Str. Biharia nr. 26, Etaj 3, Ap. BIR3F, Sector 1, 013981 București, Romania
Trade Register no. J2024045170009 — CUI 50958671
Email: info@mavenpilot.com

We have not appointed a Data Protection Officer. Send any privacy question or request to info@mavenpilot.com.

2. What this Policy covers

• The MavenPilot account, which is shared by all the Services.
• MavenRoute, our web mission planner. You can use much of it without an account; your missions then stay in your browser unless you save them to MavenCloud or share them.
• MavenCloud, where you store missions linked to your account. Sharing missions through links and publishing them in a public area are features of MavenRoute with no separate service name.
• MavenShare, temporary mission transfers using a six-digit code between MavenRoute and the Maven or Maven EVO apps, or between those apps. Transfers are not linked to a MavenPilot account.
• MavenScene, our cloud photogrammetry service, when it is available to you.
• Our mobile apps (Spark Pro, Maven, Maven Lite, Maven EVO and VR Pro). They send us mission data when you choose a MavenShare transfer, and account-related data when you use MavenPilot account features from them. Flight logs they create stay on your device and reach us only if you choose to send them to us. Apps built on the DJI Mobile SDK are also subject to DJI's own privacy policy.
• The website www.mavenpilot.com. Its cookies are described in our Cookie Policy.

3. When we act on someone else's behalf

Missions, photographs and other content you upload may contain personal data about other people, for example people, number plates or properties visible in images, or locations linked to someone. When a business customer uploads such content for its own purposes, that customer is the controller and we act as its processor: we handle the data only on its instructions and to provide the Services, and a data processing agreement can govern that relationship. The customer is then responsible for informing the people concerned and for having a legal basis. We help as the law and that agreement require.

4. The data we process

Account data. Email address, name if you provide it, the sign-in method you use (email and password, Google, or email code), your account identifier, whether your email is verified, and sign-in, registration, verification and password-reset events.

Your legal acceptance and preferences. The version of these documents you accepted, when you accepted it, from which Service and in which language; whether you agreed to receive promotional emails, and every later change to that choice. We keep these records to prove what you agreed to.

Missions and MavenCloud data. Mission names and tags; waypoints, polygons, routes and their coordinates; altitude, speed, camera, overlap, action and export settings; previews and thumbnails of your missions.

MavenShare transfer data. The mission file you choose to transfer, including its coordinates and settings, a temporary six-digit retrieval code, upload time and technical records needed to provide and protect the transfer. The transfer is not associated with a MavenPilot account or an invited email address. This does not mean the mission content is anonymised: coordinates or other content can identify a place or person, and technical requests include an IP address. After scheduled cleanup, we keep a limited record for each uploaded mission: only the first waypoint latitude and longitude with all decimal digits removed, the upload date and whole hour in UTC (no minutes or seconds), and the app name and version declared in the mission file. These are individual transfer records, not only aggregate counts. The app fields describe the software declared as having generated the file, not the recipient or necessarily the app used to upload it. Section 12 explains retention and what is excluded.

MavenRoute sharing data. Your shared and public missions, their links and settings, and the email addresses of the people you invite to a restricted share. For those people, we use the address only to send the invitation and to let them open what you shared.

MavenScene content. Uploaded photographs, file names and sizes; their metadata, which can include GPS position, time, camera and aircraft details; ground control data and coordinate systems; project and job names and settings; notes, measurements and other review objects; the Generated Outputs; share settings, including a one-way hash of any share password you set.

Plans and payments. Your plan, subscription status, renewal and expiry dates, and usage measured against your plan limits. Payments are handled by Paddle, which acts as seller of record (see section 9): we receive the information needed to manage your subscription, such as the plan, status, country and invoices, but never your full card details.

Maven app ownership (where available). If you link a Maven mobile app purchase to your account, we receive from Apple or Google the information needed to verify that purchase, such as transaction identifiers, the product purchased and the purchase date. We store purchase tokens only in a one-way hashed form.

Messages. Emails you send us and our replies; delivery information for the emails we send you, such as sign-in codes, verification, password reset, invitations, notices and, if you asked for them, promotional emails.

Usage and technical data. Like any website, our servers and our providers receive your IP address and browser information with each request. MavenRoute also sends us basic usage events: the start and end of a planning session, missions created, imported or exported and in which format, map and mission type changes, overlay imports, the chosen language, guest export limits being reached, and the creation and deletion of an account together with the sign-in methods it used. These events do not contain your name, email address or account identifier. We also keep security, error and operational logs.

Website statistics. On www.mavenpilot.com we use Matomo, hosted with our WordPress website, only after your optional statistics consent. It records visit time, pages viewed, referrer, browser/device information and a visitor identifier. The last two bytes of visitor IP addresses are masked before storage, and the masked address is also used to enrich visits, for example with approximate location. A visitor identifier or referrer can still be personal data; IP masking does not make every visit anonymous. Google Analytics and Google AdSense are not used on the website.

Elevation-service diagnostics. From 17 October 2026, our terrain-height endpoints record only the UTC time, whether the request is for one point or a batch, the number of points, outcome, HTTP and numeric transport-error codes, and elapsed time. These diagnostic records do not contain coordinates, request or response bodies, provider URLs, IP addresses, names, email addresses or account identifiers. Coordinates are still sent to the elevation provider as necessary to obtain terrain heights, as explained below.

Places and coordinates you look up. To show maps, satellite imagery and terrain heights, and to search for places, the Services send the map area you are viewing, the coordinates of your mission points and the text you search for to the map and elevation services described in section 9.

We do not intentionally collect special categories of data, such as data about health, religion or political opinions. Please avoid putting such information in mission names, notes or other free text.

5. Where the data comes from

Mostly from you: when you create an account, plan and save missions, upload content, share it or contact us. Some data is generated by the Services as you use them, such as outputs, logs and usage events. Some comes from third parties: Google, if you sign in with Google; Paddle, for subscriptions; Apple or Google, to verify app purchases. A person who shares content with you, or invites you by email, gives us your email address or the content they share.

6. Why we use data, and our legal basis

Where we rely on legitimate interest, you can object at any time (section 16).

7. How we treat your missions, photographs and results

We use them only to provide what you ask for: to validate and store uploads, generate previews, exports and outputs, keep them according to your plan, run the shares you configure, give the support you request, keep the Services secure and comply with the law. We do not:

• sell or rent them;
• use them to show advertising or to build advertising profiles;
• use them to train, fine-tune, evaluate or create artificial-intelligence or machine-learning models; or
• publish them or reuse them for unrelated purposes.

We may use aggregated operational figures, such as numbers of jobs, processing times and error rates, to run and improve the Services. For MavenShare, we also retain the individual records with reduced detail described in sections 4 and 12 to measure transfer volumes, broad geographic use and app-version compatibility. Those records are used for internal operational statistics and maps, not public mission sharing or advertising profiles.

Our staff do not routinely look at your content. Authorised staff may access it only when necessary to provide support you requested, investigate a technical or security problem, prevent abuse, restore the Services or meet a legal obligation, and only as far as needed.

8. Promotional emails

We send news about features and offers only if you tick the dedicated box, when you create your account, in the acceptance window, or later in your account settings. That box is never pre-ticked and is separate from the acceptance of our Terms.

We do not sell your email address or share it for another company's marketing, and we do not send spam. Every promotional email includes a link to unsubscribe in one click without signing in, and you can switch the preference off in your account settings at any time. We record when and where you gave or withdrew consent. Service emails your account needs, such as sign-in codes or notices about your content, are not promotional and are not affected by this choice.

9. Who we share data with

We share personal data only as needed for the purposes above.

The processing engine behind MavenScene runs as part of our own service and is not a separate platform you interact with. We choose our providers carefully and bind them to protect your data. An up-to-date list of our providers is available on request at info@mavenpilot.com.

10. Mission transfers, shares and public missions

MavenShare transfers. Anyone who has the six-digit code can retrieve the mission while it is valid, normally for 10 minutes after upload. You choose who receives the code. The transfer does not use a MavenPilot account or an email invitation. Its retention is described in section 12.

MavenRoute mission links and public missions. The mission copy you choose to share becomes available according to the link permissions you select, including restricted access for invited email addresses or access for anyone with the link. Public missions can be seen by anyone who visits the public area. These MavenRoute features are separate from MavenShare.

MavenScene shares. Job outputs become available according to the sharing settings you choose. For password-protected shares we store only a one-way hash of the password. Visitors can open permitted public shares without an account. We process visitors' IP addresses and technical data to deliver and protect shared content.

Revoking a share, or deleting the mission or job, stops access through our Services but cannot erase copies that recipients have already downloaded or recorded.

11. Data stored in your browser

Our web applications store in your browser only what they need to work:

• your sign-in state;
• your settings and preferences, such as language, units and display options;
• missions you are working on;
• a count of exports made without an account, to apply guest limits;
• temporary copies of mission previews and map tiles, to make loading faster; and
• in MavenScene, temporary tokens that unlock password-protected shares.

The web applications do not use advertising or tracking cookies. If we ever add optional analytics or similar technology, we will ask for your consent first where the law requires it. You can clear this data in your browser; doing so may sign you out, delete missions you had not saved and reset your settings. The website uses optional Matomo statistics and external video players according to the separate choices described in our Cookie Policy. You can withdraw those choices there without changing your account or marketing preference.

12. How long we keep data

MavenShare after a transfer expires. Our cleanup runs every 15 minutes. Before deleting the complete mission file it saves one reduced record per uploaded mission in a monthly log. The record contains only the six fields described above. We remove all decimal digits from the first waypoint coordinates, truncating towards zero, not rounding; for example, 41.9028 becomes 41 and -33.987 becomes -33. This gives a broad location, not a uniform 100 km grid or a guarantee of anonymity. If the first waypoint is missing or invalid, the record has no position; we do not substitute another point. The record excludes the mission name, other waypoints, altitude, flight settings, notes, the retrieval code, file identifiers, IP address, email address and account identifiers. App name/version may be missing when the file does not provide usable values. We do not keep the complete mission as a historical transfer archive.

Elevation diagnostics and historical files. Elevation diagnostic files created before 17 October 2026 can contain coordinates, request and response bodies. They remain separate from the new minimal diagnostics and currently have no fixed automatic expiry; the new 30-day cleanup does not apply to those historical files. The new diagnostic expiry does not change the retention of missions saved to your account or the elevation provider's own records.

Separate technical records and hosting backups. Short-lived technical state needed for abuse prevention, retries and safe cleanup is separate from the monthly transfer log. Hosting access/security logs may contain IP addresses, and provider backups may retain earlier copies. The transfer cleanup does not by itself erase those logs or backups; their retention is separate, and confirmed hosting details can be requested from us. We do not claim that deleting the mission file removes every technical trace of a transfer.

Website hosting backups. Aruba hosting backup copies are separate from the live files, including daily and weekly copies that are replaced through the provider's backup cycle. They can retain earlier files after live deletion; delayed backup replacement can extend that availability. The 30-day elevation diagnostic rule and Matomo expiry apply to the live application records, not to a promise that each provider backup is erased at that same moment.

Backups and deleted files. Deleted files in our Firebase storage remain recoverable for 7 days and are then permanently removed. The MavenScene database, which holds your account details and job records, is backed up in encrypted form every six hours. Scheduled copies are kept daily for a week, weekly for a month and then monthly for three months, so normally for about four months; up to three monthly copies are retained until newer monthly copies replace them, so they can remain longer if the backup schedule is interrupted. A copy is also taken before each software release; these are deleted after 120 days, except recovery copies protected for the current or previous release, unfinished deployments, and the two newest release backups. These remain until replacement or resolution of the deployment. MavenScene photographs and outputs are not backed up: once deleted they cannot be recovered. Backup copies are kept isolated, are not used for ordinary purposes and are restored only to recover from a failure or where the law requires; before restored MavenScene data is made available again, we reconcile deleted accounts against our account service and reapply Job deletions using verified deletion records. Missing files alone are not proof that a Job was deleted. If deletion records are unavailable or incomplete, restored data is kept unavailable while we reconcile it manually.

We may keep limited records longer where the law requires it, for accounting or to establish or defend a legal claim.

13. Deleting your account

You can delete your account at any time from your account settings, or by writing to info@mavenpilot.com. Because the account is shared, deletion removes your account and your content from all MavenPilot Services, including your MavenCloud missions and previews, your MavenRoute mission links and public missions, the email addresses you were invited with in other people's shares, your MavenScene photographs and outputs, and your legal acceptance and preference records, subject to the backup period in section 12.

MavenShare transfers and their reduced operational records are not linked to your account; deleting the account does not identify or remove those records. Their availability and retention follow section 12. Deleting an account does not recall mission copies already imported by recipients.

One exception, because a job code and its cost history are permanent for each project: the record of a MavenScene job is anonymised rather than deleted. What survives is a row carrying no reference to you, with the dataset name replaced by a placeholder, holding only the job code, counts, sizes, dates and timings, the kind of processing and quality chosen and which outputs were requested and produced, and unreachable from every part of the Service; the record of each processing start (dates, number of photographs and whether it counted towards the allowance) is kept the same way. File names, mission names, processing settings and engine options, which may include the boundary of the area, and messages are cleared once your files have been removed from storage. Your photographs and the results generated from them are removed.

Removal of your account and its associated content from every Service happens without undue delay and in any case within 30 days, subject to the separate records and retention exceptions described in section 12 and above, such as accounting records of past payments.

14. International transfers

We are established in the European Union, and our account data in Firebase is stored in Belgium. Some providers, such as Google for authentication and for the account-deletion function, Mapbox and the content-delivery networks, may process data outside the European Economic Area, including in the United States. Your missions, photographs and results are stored in the European Union: Firebase in Belgium; MavenScene storage in Germany, with temporary processing copies in Germany and Finland. Where this happens we rely on an adequacy decision, such as the EU–US Data Privacy Framework for certified providers, or on the European Commission's Standard Contractual Clauses, with additional safeguards where appropriate. Ask us at info@mavenpilot.com for details.

15. Security

We use technical and organisational measures suited to the risk, including encrypted connections, access controls and ownership checks for private data, protected sharing options, expiring tokens, rate limiting and deletion workflows, and we review them as the Services evolve. No online service can be completely secure: protect your sign-in methods, share links carefully and tell us promptly if you suspect unauthorised access. If a personal-data breach occurs, we assess it and notify the supervisory authority and, where required, the people affected, as the law requires.

We do not take decisions about you based solely on automated processing that have legal or similarly significant effects. Automatic features, such as applying plan limits or proposing how to group photographs, do not have that kind of effect, and proposals require your confirmation.

16. Your rights

Under the GDPR, and subject to its conditions, you can:

• ask whether we process your data and get a copy of it;
• have inaccurate or incomplete data corrected;
• have your data deleted;
• restrict processing in certain cases;
• object to processing based on our legitimate interest;
• receive the data you gave us in a structured, commonly used, machine-readable format, and have it sent to another provider;
• withdraw consent at any time, without affecting processing that took place before; and
• complain to a data protection authority.

Write to info@mavenpilot.com. We may ask you to confirm your identity. We reply within one month, which the law allows us to extend in complex cases, and we will tell you if we do. If we act only as processor for a customer's content (section 3), we may pass your request to that customer or help it answer.

Our lead supervisory authority is Romania's National Supervisory Authority for Personal Data Processing (ANSPDCP), www.dataprotection.ro. You may also complain to the authority of the EU country where you live, work or where the alleged infringement took place.

17. Children

You must be at least 16 to create a MavenPilot account, and at least 18 to buy a paid plan. We do not knowingly collect data from children below these ages. If you believe a child has given us personal data, contact us and we will take appropriate steps.

18. Legal requests and business changes

We may preserve or disclose information where we reasonably believe it is required by a valid legal process or necessary to protect rights, safety and the Services. We check requests for their legal basis and limit what we disclose; where the law allows, we inform the person concerned.

If Maven Verse is involved in a merger, acquisition, financing, reorganisation or sale, data may be disclosed under confidentiality and transferred subject to this Policy. Your content is never sold on its own for advertising or data-broker purposes.

19. Changes to this Policy

We may update this Policy to reflect legal, technical or service changes. We publish each new version with its version date and keep previous versions available. Version of 27 September 2026; Version of 26 September 2026; Version of 15 May 2026. Minor corrections or clarifications that do not change how we process your data do not require a new acknowledgement. If a change is material, we tell you in advance through the Services and, where appropriate, by email, and we ask you to confirm that you have read the new version before you continue using your account. If a change requires your consent for a new purpose, we ask for it separately.

20. Contact

For privacy questions, requests to exercise your rights or complaints:

MAVEN VERSE S.R.L.
Str. Biharia nr. 26, Etaj 3, Ap. BIR3F, Sector 1, 013981 București, Romania
Email: info@mavenpilot.com