| Version | 2026-10-18 |
| Effective date | 18 October 2026 |
| Controller | MAVEN VERSE S.R.L. |
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 files uploaded to our account Services are stored in the European Union; mobile uploads to external services and other provider processing can take place elsewhere, as explained below. You can delete your account at any time, subject to the retention exceptions below.
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.
Missions, photographs and other uploaded content may contain personal data about other people, such as identifiable people, number plates or locations linked to someone. When a business customer determines the purposes of that processing and we handle the content on its behalf to provide the Services, that customer acts as controller and Maven Verse acts as processor. The customer is responsible for the lawful collection, instructions and disclosures it makes; we remain responsible for our own obligations. For business-processing terms and requests, contact info@mavenpilot.com.
Accounts and choices. Email address, name if provided, sign-in method, account identifier, email-verification status and sign-in, registration, verification and password-reset events. We record the legal-document versions you accepted, the time, Service and language, and your separate promotional-email preference and its changes.
Missions, MavenCloud and sharing. Mission names/tags, waypoints, polygons, routes and coordinates, flight/camera/export settings, previews and thumbnails. Sharing records include the content and permissions you select, share links and invited email addresses. We use invited addresses to deliver invitations and control the requested access.
MavenShare. The mission file you transfer, including its coordinates and settings, a temporary six-digit retrieval code, upload time and records needed to deliver and protect the transfer. It is not linked to a MavenPilot account or invited email address. After the complete file is removed, we keep a reduced per-transfer record: first-waypoint latitude/longitude with all decimal digits removed, upload date and whole UTC hour, and the app name/version declared in the mission file. It excludes the mission name, remaining route, altitude, settings, code, file identifiers, IP address, email and account identifiers. It is an individual record, not an aggregate or a guarantee of anonymity. The app fields identify the software declared in the file, not necessarily the uploading or receiving app.
MavenScene. Photographs, file names/sizes and metadata such as GPS, time, camera and aircraft details; ground-control data and coordinate systems; projects/jobs and processing settings; generated reports, models, point clouds, orthophotos and other outputs; notes, measurements and review objects; sharing settings and a one-way hash of any share password.
Mobile apps. Device and aircraft position, flight state and mission settings support flight control, Follow Me and maps. Supported features also use motion/orientation sensors, camera access and selected media. Permissions depend on the app, device and feature and can be managed in device settings. Local missions, flight records and diagnostics can include coordinates, flight times, telemetry, aircraft identifiers and file references. Local diagnostics are separate from our minimised server elevation logs.
Maven and Maven EVO do not automatically upload their complete local flight-record files to MavenPilot. You can export a selected record through device sharing tools, send it for support or, where supported, configure an AirData token and request an upload. AirData receives that selected file directly, with the token, app/version and connection information. Local upload history does not mean MavenPilot holds a server copy. Maps, place searches, heights, previews, version checks and feature checks also send network requests without an account; recipients can receive IP, app/device/request information, viewed areas, searches or coordinates. Google Maps and DJI SDKs can process technical identifiers, usage and diagnostics under their own privacy information.
Plans, payments and linked app purchases. Plan/subscription status, renewal/expiry and usage against plan limits. Paddle handles paid-plan purchases as seller of record; we receive subscription and transaction information needed to administer the service, without full card details. If you link a mobile-app purchase, Apple/Google verification records can include app/product, order/transaction references, purchase/verification dates, version/environment, purchase-recognition hashes and account-link transfer history. Retained linking records do not contain the raw purchase token or signed purchase proof. References/hashes can still identify a purchase after its account link is removed.
Website comments and avatars. Name and email are required for comments; website address is optional and a MavenPilot account is not required. We also process comment text, date, article/reply, IP, browser information and moderation status. Published comments show the chosen name, text, date and any website/avatar, rather than publishing the email/IP/browser fields. Antispam Bee performs the enabled local moderation checks; its external Gravatar, country and language checks are off. Closing comments when an article reaches 30 days does not erase its existing discussion.
Author/comment avatars load directly from Gravatar (Automattic), including after website Statistics or external media are refused. The image address contains an email-derived hash for the author/commenter; Gravatar also receives the reader's IP, browser and request information and any permitted referrer. This affects readers who do not comment. A hash is not a guarantee of anonymity. Optional cookies remembering comment details are described in the Cookie Policy.
Support and service communications. Messages you send and our replies, and delivery information for sign-in, verification, password reset, invitations, notices and promotional emails you requested. Marketing delivery records contain account references or hashed test-address references, attempt times and outcomes, separately from the marketing choice.
Usage and technical records. Servers/providers receive IP and browser information with requests. Security, error and operational records include times, outcomes and relevant context, which can include account/job references, contact details involved in an email error or purchase-provider responses. Authentication state and abuse counters are separate from usage statistics. Account-cleanup functions log account references, outcomes and errors in Cloud Logging.
Version checks record time, IP, request counts and version/source. MavenBridge sends app/build, platform, operating-system, language and operation information; exception reports can include device identifiers/names, error messages, stack traces and diagnostic context. Website Download Monitor records full IP, browser, file/version, time, outcome, requesting page and a WordPress user reference when signed in. Redirection event logs exclude IP and extra headers; requested URLs can still contain personal information, and separate redirect counters retain hit counts and last-access dates.
MavenRoute usage statistics. We collect statistics on the use of the planner, including first opens, daily usage and features used.
Website statistics. Matomo runs on our WordPress hosting only after your optional Statistics consent. It records visits, pages, referrers, browser/device information and a visitor identifier. The last two IP bytes are masked before storage; the masked IP also provides approximate location. Masking does not make every visit record anonymous. Google Analytics and Google AdSense are not used on the website.
Elevation requests. Mission-point coordinates and dataset selection are sent to the height provider to obtain results. From 17 October 2026, our server elevation diagnostics contain only time, single/batch status, point count, outcome, HTTP/numeric transport codes and elapsed time, without coordinates, bodies, provider URLs, IP, names, emails or account identifiers. The mobile apps can also call the provider directly, disclosing their connection IP and coordinates.
We do not intentionally collect special-category data, such as health, religion or political opinions. Avoid unnecessary sensitive information in uploaded content, names, notes and other free text.
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.
| Purpose | Legal basis under the GDPR |
|---|---|
| Create, secure and run your account, and let you sign in | Performance of our contract with you |
| Plan, store, process, share and deliver your missions and content; provide mobile flight functions and the exports or flight-log uploads you request | Performance of the contract; for customer-controlled content, the customer's instructions (section 3) |
| Send the emails the Services need: sign-in codes, verification, password reset, invitations, notices about your content or plan | Performance of the contract |
| Record your acceptance of our Terms and acknowledgement of our Privacy Policy | Legitimate interest in proving the agreement; legal obligation where applicable |
| Apply plans, limits and fair-use rules, including guest export limits | Performance of the contract; legitimate interest in fair and sustainable operation |
| Manage subscriptions and keep accounting records | Performance of the contract; legal obligation |
| Verify linked mobile-app purchases and enforce purchase-link transfer limits | Performance of the contract while providing the link; legitimate interest in verifying entitlements and preventing abusive reuse, including after account deletion |
| Keep the Services secure and prevent abuse | Legitimate interest in protecting users and infrastructure; legal obligation where applicable |
| Publish and moderate website discussions and display author/comment avatars | Legitimate interest in operating website discussions and presenting their authors; subject to your right to object |
| Understand how the Services are used and fix problems, including planner usage statistics and the limited MavenShare records described in sections 4 and 12 | Legitimate interest in maintaining and improving the Services, where personal data is involved |
| Answer your requests | Performance of the contract; legitimate interest in customer service |
| Send you news about features and offers | Your consent, which you can withdraw at any time |
| Optional Matomo website statistics and external video players | Your consent, requested separately through website choices; withdrawal does not affect the account contract |
| Establish, exercise or defend legal claims | Legitimate interest; legal obligation |
Where we rely on legitimate interest, you can object at any time (section 16). These GDPR legal bases do not replace any separate consent required by law for storing or accessing information on your device.
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:
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.
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.
We share personal data only as needed for the purposes above.
| Recipient | What for | Where |
|---|---|---|
| Google (Firebase / Cloud Logging) — Authentication, Cloud Firestore, Cloud Storage, Cloud Functions and logging; Google Sign-In if you choose it | Accounts and sign-in, storage of missions, previews, shares and account records; account-deletion functions and operational/audit logs | Firestore and Storage: Belgium, EU. Authentication runs on Google's global infrastructure. The deletion function runs in the United States. Cloud Logging buckets use the global location and are not restricted to Belgium or the EU (see section 14). |
| Aruba S.p.A. | Hosting of www.mavenpilot.com and its Matomo statistics, MavenRoute, MavenShare mission transfers and our account services | Italy (EU); hosting backups are separate from live application retention |
| Hetzner Online GmbH | MavenScene servers, processing and S3-compatible object storage for your photographs and outputs. Your files normally travel from your browser straight to that storage; our processing servers hold temporary copies during processing and for the cleanup period described in section 12 | Germany and Finland (EU): coordinator and object storage in Falkenstein, Germany; processing servers in Germany and Finland |
| Automattic (Gravatar) | Author and comment avatar images; receives an email-derived hash in the image address and technical request information from readers' browsers | International processing under Automattic's Privacy Policy, including access outside the EEA; see section 14 |
| Google / YouTube | External video players when you allow external media; video thumbnails may contact Google before player activation, as explained in the Cookie Policy | See Google's privacy information and section 14 |
| Google Maps / Places / Elevation; Apple Maps (MapKit) | Mobile maps, place searches and terrain-height lookups, depending on the app. Receive map/search/coordinate requests and technical connection data; the Google Maps SDK also processes technical identifiers and diagnostics. See Google's privacy information and Apple Maps privacy information | International infrastructure under the respective provider's privacy information |
| DJI (SZ DJI Technology Co., Ltd. and affiliates) | Mobile SDK registration, aircraft connection, activation/account and flight-safety functions where applicable. SDK processing can include software/device identifiers, IP address, usage/diagnostics and flight-related data, depending on version and function. Local flight/warranty records are separate from automatic SDK analytics; see DJI's privacy information and SDK terms | International processing under DJI's privacy information |
| Airdata UAV, Inc. — only when you request an upload | Receives the selected flight-record file directly from the app, your upload token, app/version information and technical connection data for analysis in your AirData account. See AirData's Privacy Policy | United States; additional international processing under its policy |
| Esri (ArcGIS imagery); Cesium GS, Inc. (preview libraries and ion content) | Mobile mission-preview imagery, software, terrain or 3D content, depending on the feature. Direct requests reveal technical connection information and the requested map/content area; this does not itself upload your saved mission file. See Esri's privacy information and Cesium's policy | United States and other countries under their respective privacy information |
| DEM.Net Elevation API (elevationapi.com), publicly identified with Xavier Fischer | Terrain heights. MavenRoute sends coordinates/dataset selection through our server without forwarding user IP, account identifiers or email. The mobile apps also make direct requests, which disclose their connection IP and coordinates. | External API: service information |
| OpenStreetMap Foundation | Map tiles in MavenScene's photo classification map and supported mobile preview layers. Your browser or app contacts it directly and it receives your IP address, request information and the map area viewed | United Kingdom |
| Content-delivery networks: unpkg, jsDelivr, Google (gstatic.com) | Delivery of software libraries; they receive your IP address and browser information | Worldwide |
| Email delivery provider: Aruba S.p.A. | Service emails and promotional emails you requested, using separate mailboxes | Italy (EU) |
| Paddle (selling entity identified at checkout) | Checkout, payment, taxes, invoicing and refunds for paid plans. Paddle is the seller of record and processes payment data as an independent controller under its own privacy policy | See Paddle's buyer privacy notice for processing locations |
| Apple and Google (app stores) | Verification of Maven mobile app purchases you link to your account, where available | United States and other countries |
| Professional advisers | Legal, accounting, tax or security advice, limited to what is necessary | EU |
| Authorities and others | Where the law requires it, to protect rights and safety, or in a business transfer subject to confidentiality | Where applicable |
The processing engine behind MavenScene runs as part of our own service and is not a separate platform you interact with. We use appropriate contractual protections where a provider processes data on our behalf. Some services above, including app stores and the AirData service you choose, also act as independent controllers under their own terms and privacy information. An up-to-date list of our providers is available on request at info@mavenpilot.com.
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.
Our web applications use browser storage to provide the Services, remember your choices and measure planner usage. This includes:
The planner usage counters currently have no automatic expiry and remain in browser storage until cleared. A first-open count refers to that browser's stored state, not a verified count of individual people. You can clear browser data through your browser settings; doing so may sign you out, delete missions you had not saved, reset settings and reset these counters. Clearing browser data does not erase usage events already received by our servers; their retention is described in section 12.
The web applications do not use advertising cookies. The website uses optional Matomo statistics and external video players according to the separate choices explained in our Cookie Policy. You can withdraw those website choices there. They are separate from accepting the Terms or acknowledging this Policy; acknowledgement of this Policy is not consent to optional tracking.
Website comment cookies. Where the comment form is available, a separate checkbox lets you ask WordPress to remember your name, email address and website in this browser for your next comment. These cookies normally last up to one year and can be removed earlier through your browser settings. They are not required to leave a comment and do not subscribe you to promotional emails.
Mobile storage and permissions. Mobile apps store missions, settings, flight records, caches, purchase-link state and, if you configure AirData, its upload token/history on your device. You can manage local records using the app's available delete/export tools and device settings. Copies you export, save to shared storage or include in a device/cloud backup may remain separately; removing the MavenPilot account does not remove them. Device backups depend on your operating-system settings and provider, and are separate from MavenCloud storage.
| Data | Period or handling |
|---|---|
| Shared account, legal acceptance and preference records | While the account exists; account deletion removes these records, with the separate exceptions below. |
| MavenCloud missions/previews; MavenRoute links, invited addresses and public missions | Until you delete the content/account or revoke/unpublish the relevant share. Recipient copies already obtained remain outside our control. |
| Complete MavenShare file and retrieval code | Code valid for 10 minutes. Cleanup normally removes the complete file between 10 and 25 minutes after upload. Delayed cleanup can delay removal without extending the code. |
| Reduced MavenShare records described in section 4 | Historical operational statistics with no fixed automatic expiry; not linked to an account and not located by account deletion. |
| MavenScene stored photographs and outputs | The plan's separate input/output retention periods shown in the Service, or earlier deletion. Incomplete uploads are normally removed within about a day. |
| MavenScene temporary processing copies | Normally removed promptly after confirmed delivery or cancellation; failed engine tasks normally receive cleanup within about two days. Pending-delivery archives can remain during a storage outage until delivery, cancellation or cleanup. Failures can delay removal. |
| MavenScene review objects and job details | Associated with the job, subject to the reduced records retained after account deletion described in section 13. |
| MavenScene usage events and machine telemetry | 12 months. Machine samples older than 31 days are replaced by hourly aggregates within that period. |
| Matomo website statistics | Detailed visits older than 180 days and reports older than 24 months are selected for daily deletion, without preservation exceptions. Delayed/failed runs can delay removal. Browser cookies have separate lifetimes. |
| MavenRoute planner usage events | Individual usage records with no fixed automatic expiry. Clearing browser storage does not erase received server events. |
| Our server elevation diagnostics created from 17 October 2026 | 30 days, through daily-file expiry with a daily task and request-time fallback. Delayed cleanup can delay removal. This period does not set the elevation provider's own retention. |
| Other application usage/error files and delivery ledgers | MavenBridge/version checks, planner-collector errors, purchase/email diagnostics and promotional-email delivery records have no fixed automatic expiry. These are separate from marketing preferences and account deletion. |
| Website download records and redirect counters | No fixed automatic expiry. The download-control cookie's short lifetime does not erase download-event records. |
| Website redirect/missing-page event logs | Selected for deletion after one week. Separate hit counters and last-access dates remain; delayed runs can delay deletion. |
| Login-code/session and abuse-prevention files | Login codes are valid 10 minutes; successful verification removes the current code and a new request replaces it. Expiry/reset of a code or rate-limit window does not itself delete every file. Leftover records have no fixed automatic expiry; legacy sessions can remain after their 90-day validity until presented and cleaned up. |
| MavenShare anti-abuse and delivery state | The scheduled task runs every 15 minutes and removes stale deduplication/rate-limit state. Other counters have no fixed expiry; unfinished recovery records remain until completion or resolution. |
| Google Cloud application logs | 30 days in the current application-log bucket. Account deletion does not selectively erase the execution logs confirming it. |
| Google Cloud required administrative/system/access-transparency audit logs | 400 days in the required audit bucket; this period does not apply to every application or audit record. |
| MavenScene service and web-server logs | Service journals use storage/rotation limits without a fixed maximum age; separate system copies rotate weekly with four archives. Web-server logs rotate daily with up to 14 archives plus the current file. Empty files or delayed rotation can leave older copies; older standalone application logs have no fixed automatic expiry. |
| Processing-console logs saved with MavenScene results | Follow the job's output retention and deletion. Removing the original processing task does not separately erase a saved result log. |
| Linked mobile-app purchase records/history | Purchase references/hashes, app/product, dates and transfer counts remain to recognise purchases and enforce linking limits, including after account deletion. No fixed automatic expiry. |
| Purchase-link verification/pending-confirmation records | Codes valid 10 minutes; pending confirmations valid five minutes. Validity expiry does not automatically erase records. Account deletion removes its associated verification requests; the limits in section 13 apply to older links and cross-account references. |
| Mobile records on your device / uploaded to AirData | Managed through local app/device controls or AirData's own account/deletion rules. Deleting the MavenPilot account does not erase those separate copies. |
| Website comments | Kept with the discussion unless removed/anonymised through moderation or a valid request, subject to legal preservation. Spam is selected for deletion after 30 days. Closing comments on an older article does not erase them. |
| Support correspondence | For handling the request and necessary follow-up. We periodically review closed correspondence manually and remove what is no longer needed, subject to legal obligations/claims. |
| Subscription and accounting records | Applicable accounting/tax requirements; Paddle retains its own seller records. Paddle payment notifications received by us are selected for daily cleanup after 365 days, including after account deletion. |
MavenShare reduced detail. Our cleanup runs every 15 minutes and retains one reduced record per transfer, with only the six fields in section 4. Coordinates are truncated towards zero to whole degrees, not rounded. This is a broad location, not a uniform-distance grid or a guarantee of anonymity. Missing/invalid first-waypoint coordinates stay absent rather than being replaced by another point. The complete mission is not kept as a historical transfer archive.
Aruba backups and provider records. Website-file backups have a rotating daily copy and a separate weekly earlier copy. The WordPress database has seven rotating daily copies; this is separate from webspace backups. Replacement cycles can leave earlier data available until the copy is replaced, particularly if backup runs are delayed. Aruba hosting logs and elevation-provider request records are separate from these customer-visible backups and our application periods.
Firebase and MavenScene backups. Deleted Firebase storage files remain recoverable for seven days before permanent removal. MavenScene database backups are encrypted and run every six hours: daily copies for a week, weekly copies for about a month and up to three monthly copies afterwards, normally about four months overall. Monthly copies can remain longer if replacements stop. Pre-release database copies are selected for deletion after 120 days, except copies protecting current/previous releases, unfinished deployments and the two newest release backups; these remain until replacement or resolution.
MavenScene photographs and outputs have no separate backup: once deleted they cannot be recovered. Backup copies are isolated and used for recovery or legal requirements. Before restored MavenScene data is made available, account deletions and verified job-deletion records are reapplied. Missing files alone are not proof of a deletion; unresolved history requires reconciliation while access remains unavailable.
Deleting live data does not immediately rewrite earlier backups. The earlier coordinate-bearing elevation diagnostic files were removed from live hosting on 17 October 2026; this does not remove provider backups. We may retain limited records longer for a legal obligation or claim. Retention, code validity, file rotation and account deletion are separate operations.
You can delete your account in account settings or write to info@mavenpilot.com. Because the account is shared, deletion removes the account and its associated content across MavenPilot Services, including MavenCloud missions/previews, MavenRoute links/public missions and invited-address references, MavenScene photographs/outputs, and legal acceptance/preferences, subject to the separate retention and backup rules in section 12.
Separate records and copies. Website comments, technical/security records, website downloads, leftover authentication/anti-abuse files and email-delivery ledgers are not all automatically located or erased through shared-account deletion. MavenShare transfers and reduced records have no account link; their availability follows section 12. Mobile/local files, exported or recipient copies and device backups remain under their own controls. Deletion does not close a separate DJI, AirData, Apple, Google or Paddle account or erase those providers' records.
For a website comment request, provide the article link and the email address used. We assess removal or anonymisation under section 16; removing a comment does not delete a separate Gravatar profile. You can also ask us to review other remaining personal records.
App-purchase links. Cleanup removes verification sessions associated with the deleted account and removes account/email fields from purchase links and transfer records it can associate with that account. Purchase references, hashes, product/app information, dates and transfer counts remain to prevent account deletion resetting purchase-link limits. They do not keep the deleted account's entitlement active. Older re-linked purchases and references in another account's pending transfer may need separate review: contact us with the app and purchase reference, without passwords or sign-in codes.
MavenScene. Photographs/results are removed. Reduced job/cost and processing-start records can remain after unlinking the owner and replacing the dataset name. They contain job code, counts, sizes, dates/timings, processing kind/quality and requested/produced output types. After storage cleanup, file/mission names, detailed settings/options and messages are cleared. Removing identity fields is not a guarantee that every remaining record is anonymous. Subscription cancellation is attempted before the local subscription record is removed; provider failures can delay cleanup while retried.
Account/content removal takes place without undue delay and within 30 days, subject to the distinct records, lawful retention and backup exceptions described above. Deletion does not recall copies already obtained by others.
We are established in the EU. Main account-content stores in Firebase are in Belgium; MavenScene object storage/coordinator are in Germany and its processing infrastructure is in Germany and Finland. These locations describe the service's data stores, not a fixed number of servers or a promise that every provider record stays in the EU.
Google authentication uses international infrastructure, the account-deletion function runs in the United States, and Cloud Logging buckets use the global location. Mapping/preview providers, DJI, AirData, Gravatar and content-delivery networks can also process data outside the EEA. Files you send directly to AirData and backups managed by your device provider have separate locations and rules.
International transfers are subject to applicable data-protection requirements. For information about a particular provider's processing and the applicable transfer arrangements, contact info@mavenpilot.com.
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.
Under the GDPR, and subject to its conditions, you can:
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.
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.
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.
We may update this Policy to reflect legal, technical or service changes. We publish each version with its date and keep previous versions available. Revision of 17 October 2026; Earlier version of 17 October 2026; 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. For material changes, we explain what changes and its likely impact through an effective notice, with appropriate advance notice before changed processing starts. This Policy is an information notice, not a request for blanket consent. Where a new or changed processing purpose requires your consent, we ask for it separately before that processing begins.
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