Privacy · effective July 15, 2026

Local-first is a data boundary, not a marketing phrase.

This policy explains what stays on your machine, what leaves it when you request an online service, and what account and operational data Fanta keeps.

01

Local projects

Stay on your disk unless you intentionally send or sync them.

02

Hosted generation

Content is sent to run the requested job; operational metadata may be retained, while request bodies and pixels are designed not to be logged by Fanta.

03

Model training

Fanta does not train models on private documents, prompts, uploads or outputs.

04

Your choices

You can request access, correction, deletion or export of applicable account data.

Last updated and effective: July 15, 2026

1. Scope and controller

This Privacy Policy applies to the Fantaisa website, waitlist, account platform, private-alpha Fanta application, hosted generation services and support interactions (together, the “Service”). “Fanta,” “Fantaisa,” “we,” and “us” refer to the operator of those services.

It does not replace the privacy terms of a model provider, API provider or external service you intentionally connect. Their processing is governed by their own policies.

2. Information we collect

Information you provide

  • Email address, name or account identifiers used for the waitlist, sign-in and activation.
  • Plan, seat, credit, invoice and transaction metadata. Payment-card details are handled by our payment provider rather than stored directly by Fanta.
  • Support messages, diagnostics and attachments you intentionally send.
  • Prompts, reference media and settings you intentionally submit to hosted generation or another connected service.

Information generated by use

  • Basic device, browser, operating-system, referral and page-interaction information for website performance and analytics.
  • Account, entitlement, device-activation, credit-ledger and job metadata needed to operate the Service.
  • Security, error and abuse-prevention records. Product telemetry and diagnostic upload in the native editor are opt-in where offered.

3. Local documents and editor data

Fanta projects are local-first. FNX files, linked assets, file paths, canvas content and Git history stay in the project location you choose and are not uploaded merely because you open or edit them.

Content leaves your device only when you choose a feature that requires it—for example hosted generation, cloud account services, a third-party provider, sync or sharing when available, or a support attachment you send.

4. Hosted generation and model providers

When you request hosted generation, the prompt, uploaded reference content and settings must be transmitted to infrastructure that performs the job. Fanta’s hosted platform is designed not to persist or log raw request bodies or image pixels as routine application logs. We may retain operational metadata such as account, model, job identifier, timestamps, status, safety outcome and credit cost.

Temporary copies may exist in memory, queues, caches or infrastructure long enough to complete, secure and deliver the request. Providers and infrastructure vendors may process content on our behalf under their applicable terms.

Fanta does not use private projects, prompts, uploads, outputs or support attachments to train models. If we ever want to use work for research, training, marketing or a case study, we will ask for separate permission.

5. Website analytics, waitlist and cookies

The website may use Vercel Analytics and Speed Insights, PostHog and, when configured, Google Analytics to understand page performance, referrals and conversion events. These services may process truncated network, browser, device, page and interaction information and may use cookies or similar browser storage according to their configurations.

When you join the waitlist, your email, source page and campaign parameters are sent to a configured waitlist destination and may also be recorded in PostHog so the signup is durable even when browser analytics is blocked.

You can block non-essential browser analytics using browser privacy controls or content blockers. Blocking analytics does not prevent use of public pages.

6. How and why we use information

  • Provide accounts, activation, editor services, generation, credits, billing and support.
  • Authenticate users, secure the Service, prevent abuse and enforce plan limits.
  • Operate the waitlist and send requested product or administrative messages.
  • Diagnose failures and improve reliability, usability and model routing.
  • Meet legal, tax, accounting and compliance obligations.

Where applicable, the legal bases are performance of a contract, our legitimate interests in operating and securing the Service, consent for optional processing, and compliance with legal obligations.

7. Service providers and disclosure

We share information only as needed with providers that support hosting, analytics, authentication, communications, billing, fraud prevention, support and model inference. Current integrations may include Vercel, PostHog, Google Analytics when configured, account-authentication services, Polar for billing, and model or infrastructure providers used for a job you request.

We may also disclose information when required by law, to protect users or the Service, or as part of a merger, financing, acquisition or asset transfer subject to appropriate safeguards. We do not sell local project files or private creative content.

8. Retention, transfers and security

We keep information only as long as reasonably necessary for the purpose collected, including account operation, billing records, security, dispute resolution and legal obligations. Retention periods vary by category; you may contact us for details about a specific record.

Providers may process information in countries outside yours. Where required, we use contractual or other lawful safeguards for international transfers.

We use technical and organizational safeguards appropriate to the nature of the information. No system or transmission method can be guaranteed completely secure, so do not send passwords, private keys or unnecessary sensitive data to support.

9. Your privacy rights and choices

Depending on your location, you may have rights to access, correct, delete, restrict or object to processing, receive a portable copy, withdraw consent and complain to a supervisory authority. Mandatory exceptions may apply, including records we must keep for legal or security reasons.

To make a request, email privacy@fantaisa.net from the account address where possible. We may need to verify your identity before completing a request.

The Service is not directed to children under 13, and users must also meet any higher minimum age required by their country. We do not knowingly collect personal information from children in violation of applicable law.

10. Changes and contact

We may update this policy as the product and providers change. Material changes will be identified by a new effective date and, when appropriate, an account or product notice.

Privacy questions and requests: privacy@fantaisa.net. General product support: support@fantaisa.net. You can also review the Terms of Service.

Support is part of the alpha

Answers, troubleshooting and a direct line to the team

Installation, credits, local files, privacy, model providers and editor workflows are covered in one practical support center.

Open Support & FAQ