Privacy Policy.
Specific, readable, and honest.

1. Who we are

Mappi Studio is a browser-based tool for designing and rendering animated map videos. The Service is operated by the team behind mappi.studio. For any privacy-related question, request, or complaint, you can reach us at privacy@mappi.studio. For general support, write to support@mappi.studio. For security disclosures, write to security@mappi.studio.

For the purposes of the EU/UK GDPR, we act as the “controller” of the personal data described in this policy when you use Mappi as an individual user. When we process User Content on your behalf to render videos, we may also act as a “processor” for that content.

2. Scope of this policy

This policy applies to personal data we collect through the Mappi website, the in-browser editor, our API endpoints, our render pipeline, transactional emails, and any other interaction you have with Mappi.

It does not apply to third-party websites or services that are linked from Mappi (for example, the destinations you preview through Google services, the Stripe-hosted billing portal, or external pages referenced in our blog). Those third parties have their own privacy policies, which we recommend reading.

3. Information we collect

We collect only the data we need to operate Mappi, keep your account secure, deliver renders, and improve the product. The categories below describe what we collect and where it comes from.

3.1 Information you provide directly

• Account information — your email address and a hashed password when you sign up with email; or your email address, name, and avatar URL when you sign in with Google OAuth.
• Profile and preferences — display name, language, theme, and similar settings you configure inside the editor.
• User Content — the destinations, routes, labels, custom pins, images, brand assets, colors, themes, animation settings, and other inputs you create or upload while building your map videos.
• Render requests — the configuration we send to our render pipeline so it can produce your MP4 file (camera path, route geometry, styling, aspect ratio, resolution, and similar parameters).
• Communications — messages, attachments, and feedback you send to us via email, support form, or any other channel, including refund and security reports.

3.2 Information collected automatically

• Device and browser data — browser type and version, operating system, screen size and device pixel ratio, language, time zone, and approximate IP address.
• Usage data — pages visited, features used, buttons clicked, errors encountered, render durations, and similar product analytics events. We use this to understand how Mappi is used and where it can be improved.
• Log data — request timestamps, status codes, referrer, request paths, and other server logs needed to operate and secure the Service.
• Cookies and similar technologies — see Section 9 for details on the cookies we set and why.

3.3 Information from third parties

• Identity providers — when you sign in with Google, we receive your email, name, profile picture URL, and a stable Google account identifier from Google. We never see, store, or transmit your Google password.
• Payments — when you subscribe to Mappi Pro, Stripe processes the payment and shares with us limited information such as your customer ID, subscription status, the last four digits and brand of your card, billing country, and invoice metadata. We never see or store your full card number.
• Map and place data — when you search for a location, our server proxies the request to Google Places (and, for some features, Azure Maps). The query text and coarse request metadata are sent to those providers under their terms.

3.4 What we do not collect

• We do not collect precise device GPS or live location. The “locations” in your projects are the destinations you choose to add — not your physical position.
• We do not collect your contacts, photos library, microphone, or camera input.
• We do not knowingly collect data from anyone under 13 (see Section 13).
• We do not buy personal data from data brokers and we do not enrich your account with third-party advertising profiles.

4. How we use your information

We use the information described above for the specific purposes listed below. Wherever possible, we minimize the data used and rely on aggregated, pseudonymized, or short-lived data instead of personal identifiers.

• Provide the Service — authenticate your account, render your User Content into videos, deliver your exports, and let you manage your projects across devices.
• Operate paid plans — process subscriptions, manage entitlements, send receipts and renewal notices, handle refunds, and recover failed payments through Stripe.
• Communicate with you — send transactional and security emails (sign-in confirmations, password resets, billing receipts, render notifications, important policy updates). Marketing emails, if any, are only sent with a clear opt-out.
• Improve and develop Mappi — analyze aggregated product usage, debug errors, prioritize features, and design new ones. Where possible, we work from aggregated metrics rather than individual records.
• Keep the Service safe — detect and prevent fraud, abuse, scraping, credential stuffing, payment chargebacks, and policy violations; rate-limit and protect the render pipeline.
• Comply with the law — respond to lawful requests, enforce our Terms, defend our rights, and meet tax, accounting, and audit obligations.

4.1 We do not train AI models on your content

We do not use your User Content, your projects, your renders, or your private prompts and assets to train any machine learning or generative AI model, whether ours or a third party’s. Aggregated, anonymized telemetry (for example, “users on Pro export X% in 16:9”) may be used internally to improve features, but it cannot be tied back to any individual.

4.2 We do not sell your personal information

We do not sell, rent, or trade your personal information for monetary or other valuable consideration. We do not engage in cross-context behavioral advertising. The only third parties that receive your personal data are the sub-processors listed in Section 6, and only to the extent necessary to operate the Service.

5. Legal bases (EU/UK users)

If you are in the European Economic Area, the United Kingdom, or Switzerland, we rely on the following legal bases under the GDPR (and equivalent local laws) to process your personal data:

• Performance of a contract — to provide you with the Service, run your renders, manage your account, and process your subscription. (Article 6(1)(b) GDPR.)
• Legitimate interests — to keep the Service secure, prevent abuse, debug, analyze aggregated usage, and improve Mappi, in a way that does not override your rights and freedoms. (Article 6(1)(f) GDPR.)
• Compliance with legal obligations — to retain billing records, respond to lawful requests, and meet tax and accounting requirements. (Article 6(1)(c) GDPR.)
• Consent — for any optional data uses where consent is required (for example, certain non-essential cookies). You can withdraw consent at any time. (Article 6(1)(a) GDPR.)

6. Sub-processors and infrastructure

Mappi runs on a small number of trusted infrastructure providers. We share only the personal data each provider needs to deliver its part of the Service, under written data-processing agreements where applicable. The current list is:

We will update this list when we add or remove a sub-processor that processes personal data. Material changes will be communicated as described in Section 14.

7. When we share information

We share personal data only in the limited situations below, and only the minimum amount needed:

• With sub-processors — as described in Section 6, to operate, secure, and deliver the Service.
• With your consent — when you ask us to share information with a third party, for example by connecting an integration or generating a public share link.
• For legal reasons — to comply with applicable law, court orders, subpoenas, or other valid legal processes; to enforce our Terms; or to protect our rights, property, or safety, and that of our users or the public.
• In a corporate transaction — if Mappi is involved in a merger, acquisition, financing, or sale of assets, your personal data may be transferred as part of that transaction. We will require any successor to honor the commitments in this Privacy Policy or to give you notice and a meaningful choice.
• In aggregated or de-identified form — we may share aggregated statistics that cannot reasonably be used to identify you (for example, total renders per month).

8. International data transfers

Mappi and several of our sub-processors are based in, or operate infrastructure in, the United States and other countries outside your home jurisdiction. When we transfer personal data internationally — for example, when you create an account from the EU and your data is stored on US-based Supabase or Vercel infrastructure — we rely on appropriate safeguards.

• Standard Contractual Clauses (SCCs) approved by the European Commission and the UK addendum, where applicable.
• Adequacy decisions, where the destination country has been recognized as providing an adequate level of protection.
• Additional contractual and technical measures, including encryption in transit and at rest, access controls, and minimization.

You can contact privacy@mappi.studio to request more information about the transfer mechanisms we use for a specific provider.

9. Cookies and similar technologies

Mappi uses cookies and similar technologies (such as localStorage and sessionStorage) for the limited purposes below. We do not use cookies for cross-site advertising profiling.

9.1 Strictly necessary

These are required for Mappi to function: authentication and session cookies set by Supabase Auth (HttpOnly, Secure, SameSite), CSRF protection tokens, and load-balancing cookies. Disabling them will break sign-in.

9.2 Functional

Local storage entries that remember your editor preferences, last-used theme, dev-mode toggles, and recent project selections so the editor opens in the state you left it.

9.3 Analytics

PostHog sets a pseudonymous identifier so we can understand which features are used and where users get stuck. The identifier is not linked to your real-world identity in our marketing systems and is never sold. Where required by law, we will request your consent before enabling non-essential analytics.

9.4 Browser controls

You can clear or block cookies through your browser settings. Mappi also honors the standard “Global Privacy Control” signal where it is legally required.

10. Data retention

We keep personal data only for as long as necessary to provide the Service, comply with our legal obligations, resolve disputes, and enforce our agreements.

• Account data — kept while your account is active. If you delete your account, your account record and associated User Content are removed from our active systems within 30 days, except for the items below.
• Backups — encrypted backups containing deleted data are rotated out within 90 days from your deletion request.
• Billing records — invoices, subscription history, and tax records are retained for the period required by applicable accounting and tax law (typically 7 years).
• Security logs — short-term logs (request, error, and abuse logs) are retained for up to 90 days, longer where needed to investigate a specific incident.
• Anonymized analytics — aggregated, non-identifiable usage statistics may be retained indefinitely.

11. Your privacy rights

Depending on where you live, you may have some or all of the rights below in relation to the personal data we hold about you.

• Access — request a copy of the personal data we have about you.
• Rectification — ask us to correct data that is inaccurate or incomplete.
• Deletion (“right to be forgotten”) — ask us to delete your personal data, subject to limited legal exceptions.
• Restriction — ask us to restrict processing of your personal data while a request is being resolved.
• Objection — object to processing based on our legitimate interests, including direct marketing.
• Portability — receive a portable, machine-readable copy of certain data you have provided to us.
• Withdraw consent — where we rely on consent, withdraw it at any time without affecting prior processing.
• Lodge a complaint — with your local data protection authority (for EU/UK users) or other regulator with jurisdiction.

11.1 California (CCPA/CPRA) rights

If you are a California resident, you have the right to know what personal information we collect, why we collect it, and who we share it with; the right to delete and correct your personal information; the right to opt out of any “sale” or “sharing” of personal information (we do neither); and the right not to be discriminated against for exercising your rights.

11.2 How to exercise your rights

You can exercise most rights from inside Mappi: update your email and profile in account settings, manage your subscription via the Stripe billing portal, or request account deletion in settings. For anything else, write to privacy@mappi.studio. We will verify your identity before responding and will reply within the timeframes required by applicable law.

12. How we protect your data

We apply the security practices described on our Security page across authentication, data, infrastructure, and engineering. In summary:

• TLS 1.2+ encryption in transit on every request, AES-256 encryption at rest for stored data.
• Supabase Auth with HttpOnly, Secure, SameSite session cookies, and OAuth 2.0 sign-in with Google. We never see your password.
• Postgres Row-Level Security so users can only access their own rows.
• Server-side proxying of third-party APIs so secrets never reach the browser, and least-privilege access controls internally.
• PCI DSS Level 1 payment processing via Stripe — Mappi never sees or stores your full card number.
• A documented incident-response process for handling security events.

No system is perfectly secure. If you discover a vulnerability, please report it to security@mappi.studio so we can fix it before it can be exploited. Do not publicly disclose the issue until we have had a reasonable opportunity to investigate.

13. Children’s privacy

Mappi is not directed to children under 13, and we do not knowingly collect personal data from children under 13. If you are under the age of majority in your country, you must have permission from a parent or legal guardian to use the Service.

If you believe a child under 13 has provided personal information to us, please contact privacy@mappi.studio and we will delete the information from our systems.

14. Changes to this policy

We may update this Privacy Policy from time to time to reflect changes to the Service, our sub-processors, or applicable law. The “Last updated” date at the top of this page always reflects the latest version.

For material changes — for example, a new category of data, a new sub-processor that processes personal data, or a change in legal basis — we will give you reasonable advance notice (such as an in-app banner or an email to your account address) before the change takes effect. Your continued use of the Service after the effective date constitutes your acceptance of the updated policy.

15. Contact us

For privacy questions, requests, or complaints, write to privacy@mappi.studio. For general support, write to support@mappi.studio. For security disclosures, write to security@mappi.studio. We aim to acknowledge requests within a few business days and respond fully within the timeframes required by applicable law.