Privacy policy
This policy explains what personal data MosaicEarth processes, why it is needed, who may receive it and how you can exercise your rights.
LAST UPDATED · 10 NOVEMBER 20261. Controller and scope
Nil Sicart Moragas, operating as MosaicEarth, is the controller for account, service administration and the personal data described in this policy. Identification and contact details are in the legal notice. This policy covers mosaicearth.app, app.mosaicearth.app, official Desktop activation and optional cloud synchronization from Desktop and the connectors.
Privacy questions or rights requests can be sent to [email protected]. Service identification and contact details are also set out in the legal notice.
2. Information we process
- Account and authentication data: username, email address, account status and the external sign-in provider you choose.
- Project and asset data: uploaded source files, derived web files, coordinates, metadata, descriptions, tags, capture dates, visibility, price and licence choices.
- Public and shared content: creator identity, asset details and saved viewer state where you publish an asset or generate a sharing link.
- Billing and transaction data: euro payments, plan allowances, subscriptions, purchases, creator earnings, legacy credit records where applicable, invoices and payment status. Payment card details are handled by Stripe and are not stored by MosaicEarth. For creator withdrawals, Stripe Connect collects identity and bank details on its hosted pages; MosaicEarth stores connected account identifiers, readiness status, withdrawal amounts and transfer/payout identifiers and states, not bank account numbers or identity documents.
- Support and communications: messages, completion emails, internal notifications and your communication choices.
- Technical and security data: IP address, browser and device information, request logs, error events, sign-in attempts and fraud or abuse signals.
- Desktop activation and synchronization: account identity, a hashed device identifier, the computer name you provide, activation and expiry times, transfer manifests, file sizes, checksums, revision associations and transfer progress.
- Cookies and similar storage: the essential session, security and service data described in our cookie policy.
3. Purposes and legal bases
4. Public assets and sharing links
Publishing a MosaicAsset makes its preview, geographic position, creator, descriptive metadata, price and applicable licence discoverable through the public globe. Acquiring users may obtain the original file under the recorded licence.
A private asset is not listed for public acquisition. Public or unlisted sharing can make a scene available to people with its link, subject to the access rules of its layers; viewing does not itself grant download or editing rights. Treat unlisted links as confidential and disable sharing when it is no longer intended. Uploading a synchronized revision does not publish it.
5. Service providers and recipients
We use providers only where needed to operate MosaicEarth. Depending on the feature you use, recipients may include:
- Operator-managed application infrastructure stores accounts, project metadata, files and operational backups; Cloudflare provides secure delivery, connectivity and R2 object storage. Netlify hosts this public information website as static pages.
- RunPod receives the selected inputs for requested cloud photogrammetry or Gaussian processing on temporary compute workers. Desktop local processing runs on your own computer instead.
- Stripe handles checkout, subscriptions, payments and creator payout verification through Stripe Connect. Google, GitHub or Microsoft receive authentication requests only when you choose that sign-in provider.
- Microsoft Azure Communication Services and configured mail services deliver account and operational messages. Azure is not the current application database or primary project hosting platform.
- Map providers include Esri World Imagery, Re:Earth / Mapterhorn terrain, OpenStreetMap, EOX and IGN/PNOA. Detailed satellite tiles load directly from Esri using an individual temporary basemap session. MosaicEarth issues that session without sending an account password, activation grant or project file to Esri. The session broker records a hashed random client identifier and a daily pseudonymous connection identifier for service limits; it does not record the viewed coordinates. Terrain normally passes through MosaicEarth’s public terrain cache and Cloudflare; a direct Re:Earth connection is used if that gateway fails. The bundled NOAA terrain fallback does not contact an external terrain provider. Your browser’s tile requests can disclose your IP address and the area being viewed. Place searches are forwarded to the Photon geocoding service; avoid entering private information in a place search. Provider links and attribution are on the map sources page.
- User-selected processing nodes receive inputs when you explicitly use that node. Their operator is responsible for its own hosting and retention. GitHub serves the public source and release downloads; Docker and package registries receive requests needed to install or update local engines.
Providers may process connection data or requested files outside the European Economic Area, depending on the selected service and processing location. International transfers are subject to the applicable GDPR safeguards, such as an adequacy decision or standard contractual clauses. Contact [email protected] for information about the providers and transfer safeguards relevant to your use. We do not sell personal data.
6. Retention
- Account data is normally kept while the account is active and for the limited period needed to resolve closure, fraud, security or legal issues.
- Cloud files are retained according to your account, storage quota, deletion requests and applicable service terms. Current Free, Pro and Studio plans do not apply the former automatic 15-day expiry to files simply because they are private. Originals and supporting files transferred by synchronization use cloud storage too.
- Published assets, recorded licence acceptances and acquisition records may need to remain available to preserve the rights of creators and acquiring users.
- Billing, tax and transaction records are kept for the period required by applicable law.
- Security logs and backups are retained for proportionate operational, recovery or legal periods, then deleted or overwritten. The appropriate period depends on the record and any incident or legal requirement.
Local Desktop and connector data
Using the source edition locally does not require a MosaicEarth account or upload your project to MosaicEarth. Official activation and engine delivery contact our service but do not, by themselves, upload project contents. Public maps, searches and external layers can still contact their providers.
Cloud transfers occur when you request synchronization or cloud processing. Disconnecting a cloud session does not remove local copies. Uninstalling Desktop preserves the workspace; you control deletion of local files and backups. Connector credentials or sessions are handled by the chosen client. You remain responsible for personal data in your captures and for the lawful basis for processing it; where MosaicEarth processes personal data on an organisation’s behalf, the applicable data-processing arrangements must also cover that use.
7. Your rights
Depending on the circumstances, you may request access, correction, deletion, restriction, portability or object to processing. Where processing is based on consent, you may withdraw it at any time without affecting earlier lawful processing.
Send requests to [email protected] from the account email where possible. See the data deletion procedure for account closure. You also have the right to complain to the Spanish Data Protection Agency (AEPD) or another competent supervisory authority.
8. Your responsibilities for uploaded data
Geospatial imagery and models may reveal people, homes, vehicles, restricted sites or other personal and sensitive information. Before uploading or publishing, you must have the necessary rights and lawful basis, apply appropriate minimisation or masking, and comply with privacy, intellectual-property, property, aviation and security rules that apply to your capture and use.
9. Security
We use access controls, encrypted transport, restricted administrative permissions, audit records, backups and operational monitoring appropriate to the service. No online system can guarantee absolute security. Contact [email protected] if you believe an account or asset has been exposed.
10. Changes and contact
Material changes will be announced in the service or by email when appropriate. The revision date above identifies the current version. Questions can be sent to [email protected].