Legal

Privacy Policy

This policy explains what personal data Prefably processes, why, for how long, with whom it is shared and how to exercise your rights, in accordance with the General Data Protection Regulation (GDPR) and the French Data Protection Act (loi Informatique et Libertés).

At a glance

  • We collect only what is necessary to operate your account, your projects, your AI generations, the Unity plugin and billing.
  • Your database and your files are hosted in the European Union (Ireland).
  • To run an AI task, your instructions and the necessary content are sent to model providers, some of which are located in the United States, with safeguards governing these transfers.
  • We do not use your instructions or your creations to train AI models, and we do not sell your data.
  • Payments are processed by Stripe: we never see your full card number.
  • You can access, export or correct your data, or delete your account, at any time.

Article 1 — Controller and contact

1.1. The controller is [TO BE COMPLETED: company name], [TO BE COMPLETED: legal form], registered with the Trade and Companies Register (RCS) of [TO BE COMPLETED: city] under number [TO BE COMPLETED: SIREN], with its registered office at [TO BE COMPLETED: address] (“we”).

1.2. For any question about your data or to exercise your rights: [TO BE COMPLETED: dedicated email address, for example privacy@…] or by post to the address above.

1.3. Data Protection Officer (DPO). [TO BE COMPLETED: contact details of the DPO if one is appointed, or delete this paragraph.] [Drafting note: appointing a DPO is, a priori, not mandatory for a small organization whose core activity is not large-scale systematic monitoring; to be confirmed with counsel.]

1.4. Our role. We act as controller for the management of your account, the Services, billing and security. Where you are a business user and you process, by means of the platform, personal data of third parties on your own behalf (for example faces or names in your files), you are the controller of that data and we act as processor (Article 16 of the Terms of Use).

Article 2 — Data we collect

The data below is collected from you or generated by your use of the Services. Mandatory fields are indicated when you enter your information; without them, we cannot create your account or provide the requested service.

CategoryDataSource
AccountEmail address, verification status, password (stored in irreversibly encrypted form by our authentication provider), display name and avatar (optional), creation and update datesYou
Login and securityIP address, browser and device type (user agent), authentication sessions and tokens, login timestampsYour device
Projects and creationsProjects, Workflows and their versions, custom blocks, templates, folders, labels, style guides, delivery profiles, Assets (files, metadata, tags)You and the Services
AI instructions and resultsInstructions (prompts), input and output data of runs, Generated Content, errors, model and provider used, tokens consumedYou and the Services
Conversational assistantConversation history (messages, title, model used)You and the Services
Unity pluginInstallation name, Unity and plugin version, date of last activity, installation token (stored in hashed form), Unity project name and path, current selection and project asset catalog when you share them, commands and tasks executed, Asset deliveriesThe plugin
Connectors and keysConnected service, label, external account, permissions granted, encrypted access credentials; encrypted personal API keys (last four characters visible)You and third-party services
Usage and CreditsUsage events (task type, quantity, tokens, estimated cost), Credit reservations and debits, packs purchased, refund requestsThe Services
BillingStripe customer ID, Plan, subscription status and periods, invoices (number, amounts, currency), payment notifications sent by Stripe (which may include name, billing address, country, VAT number, card type and last four digits)You and Stripe
Technical diagnosticsInterface error reports (message, page concerned), server error log; email addresses, passwords, tokens and keys are automatically removed from themYour device and our servers
Desktop applicationWorking data, generated files and technical log stored on your computer; session kept in the Windows secure vault; periodic update checksYour computer
Communications with usMessages sent to support, content reports (notices), appealsYou

We do not collect special categories of data within the meaning of Article 9 GDPR, and we ask you not to include any in your instructions or files. We never receive your full bank card number. We do not use any audience measurement, advertising or behavioral tracking tools. Desktop application data stored on your computer remains under your control: we have no access to it, except for data that is synchronized with your account.

Each processing operation is based on one of the legal bases set out in Article 6 GDPR. When the periods indicated expire, the data is deleted or anonymized.

PurposeData concernedLegal basisRetention period
Creating and managing your account, authenticating youAccount, loginPerformance of the contract (Terms of Use)Lifetime of the account; inactive Free account deleted after 24 months, following a warning
Providing the Services: projects, workflows, AI generations, chat, library, Unity plugin, connectors, desktop applicationProjects and creations, instructions and results, conversations, Unity, connectors and keysPerformance of the contractLifetime of the account, or until you delete them; items moved to the trash: permanently deleted after 30 days; generated files no longer used by any Asset: deleted after 14 days
Managing Credits and usage limitsUsage and CreditsPerformance of the contractLifetime of the account; anonymous aggregated data thereafter
Managing the storage quota after a change of PlanAssets, PlanPerformance of the contractRead-only for 30 days, then deletion of the oldest files exceeding the quota (Article 15.5 of the Terms of Use)
Managing subscriptions, payments, refundsBilling, CreditsPerformance of the contractDuration of the business relationship, then 5 years in archive for evidentiary purposes (civil limitation period)
Issuing and retaining invoices and accounting recordsBillingLegal obligation (Article L123-22 of the French Commercial Code)10 years from the end of the financial year
Retaining proof of your consent to immediate performance and of your waiver of the right of withdrawalOrder, timestamp, consent givenLegal obligation and legitimate interest (evidence)5 years after the order
Ensuring security, limiting abuse (rate limiting of requests per IP address, multiple accounts, circumvention of limits)Login, usageLegitimate interest (protecting the platform and its users)Per-IP-address counters: in memory, a few minutes; login sessions: until they expire or you log out; login logs: 12 months
Diagnosing and fixing technical errorsTechnical diagnosticsLegitimate interest (reliability of the service)Automatically rotated error log (file capped at 5 MB), and no more than 12 months [Drafting note: maximum period to be set]
Responding to identification requests from authoritiesAccount, loginLegal obligation (LCEN, French Law on Confidence in the Digital Economy)12 months from the login or the creation of the content
Handling content reports and appeals (DSA)Reports, decisions, communicationsLegal obligation (Regulation (EU) 2022/2065)2 years after the decision [Drafting note: proposed period, to be validated]
Responding to your support requestsCommunications with usPerformance of the contract or legitimate interest3 years after the last communication
Handling your requests to exercise your rightsIdentity, request, responseLegal obligation (GDPR)5 years after the response
Improving the platform (operating statistics, failure rates, costs)Usage, in aggregated formLegitimate interest (improving the service)Individual data: lifetime of the account; anonymous statistics: no time limit
Informing you of significant changes and of events concerning your accountEmailPerformance of the contractLifetime of the account

Account deletion. When your account is deleted, your account data, projects, Assets, conversations, connections and Unity tokens are erased from the production database. They may remain in encrypted backups for [TO BE COMPLETED: Supabase backup retention period, for example 7 days], after which they are permanently overwritten. Only the data that the law requires us to keep (invoices, proof of orders) is retained, in a separate, restricted-access archive. Deleting the account also terminates any ongoing subscription and deletes your customer record at Stripe. [Drafting note: technical issue to be fixed — the current account deletion procedure erases invoices and payment notifications from the database, then deletes the Stripe customer, without separate archiving; provision must be made to retain invoices for 10 years before going into production.]

Article 4 — Artificial intelligence features

4.1. What is sent. When you launch a generation, run a Workflow or write to the assistant, we send the selected AI Provider only what is necessary for the task: your instruction, the context of the Workflow or conversation, and the files or style guides you attach to it. We do not send it your email address or your billing data. Files produced by fal.ai are retrieved and then stored in our European storage space.

4.2. Choice of provider. For tasks paid for with Credits, the request is processed, depending on the model tier selected, by OpenRouter (“eco” and “standard” tiers, with OpenRouter forwarding the request to the model provider: for example Anthropic for Claude Haiku), by Anthropic directly (“advanced” tier), or by fal.ai for images and 3D models. The provider and model used are recorded in the run history. The other providers (OpenAI, Google Gemini, Groq) are called only if you use your own API key (Article 4.4).

4.3. No training. We do not use your instructions, your files or your Generated Content to train or fine-tune AI models. We use the business offerings (APIs) of AI Providers, whose terms in principle provide that data is not used for training and is retained only for a limited period, mainly for abuse detection. [Drafting note: legal decision and verification required — check, for each provider, the retention period for requests and the absence of training; on OpenRouter, disable in the account settings access to providers that retain or train on requests, which often concerns free models; in particular, check the provider imposed for the “eco” tier (“darkbloom”, model gpt-oss-20b). The code does not send any user identifier to providers, which is consistent with paragraph 4.1. If reuse of prompts to improve the service is contemplated, add a purpose based on legitimate interest with a simple right to object, or on consent.]

4.4. Personal keys. If you use your own API key, the request is sent to the provider with that key: that provider then processes your data in accordance with the contract you have entered into directly with it.

4.5. Content you provide. Do not include in your instructions or files personal data of third parties without a legal basis, or any special categories of data. If you upload the image or voice of a person, you must have their permission.

4.6. No automated decision-making or profiling. The AI features are used to produce the content you request. We do not take any decision concerning you based solely on automated processing that produces legal effects or similarly significantly affects you, and we do not carry out profiling for advertising purposes. Automated safety filters may block a request; any moderation measure targeting your account is subject to human review.

Article 5 — Recipients and processors

5.1. Your data is accessible only to authorized members of our team, within the limits of their duties. We do not sell or rent your data.

5.2. We use the following processors, bound by a contract compliant with Article 28 GDPR:

ProviderService providedData locationSafeguard for transfers outside the EU
SupabaseDatabase, authentication, file storage (Assets), sending of login emailsEuropean Union (Ireland, eu-west-1 region)Possible access from abroad for support purposes: [TO BE VERIFIED: SCCs or DPF according to Supabase’s data processing agreement]
[TO BE COMPLETED: application server host]Hosting of the server and the web interface[TO BE COMPLETED][TO BE COMPLETED]
StripePayment, subscriptions, invoices, refunds, VAT calculationEuropean Union and United States[TO BE VERIFIED: Data Privacy Framework certification and standard contractual clauses]
OpenRouterAccess to the text models of the eco and standard tiers; forwarding to the model provider (Anthropic, “darkbloom”…)United States (and the country of the model provider)[TO BE VERIFIED]
Anthropic (Claude API)Text model of the advanced tier: assistant, Workflow creationUnited States[TO BE VERIFIED]
fal.aiGeneration of images (FLUX) and 3D models (Trellis)United States[TO BE VERIFIED]
[TO BE COMPLETED: desktop application update server]Distribution of updates (IP address, installed version)[TO BE COMPLETED][TO BE COMPLETED]
[TO BE COMPLETED: email service provider, if a custom SMTP is configured]Confirmation and password reset emails[TO BE COMPLETED][TO BE COMPLETED]

[Drafting note: list compiled from the code (configuration file and outgoing calls) and the database. The server is not yet hosted: fill in the selected host. The code provides for Resend for emails (not connected to date: emails are sent from Supabase’s default server) and Sentry for error tracking (not used); add them if they are activated. Pollinations is still called as a fallback for the game content analyzer when no platform model is configured: remove this path or add it to the list.]

5.3. Services you connect. When you connect GitHub, Figma, Notion, Perforce or another service, or use your own API key, exchanges with that service take place at your initiative; that service acts as the controller of its own processing, in accordance with its privacy policy.

5.4. Authorities. Your data may be disclosed to administrative or judicial authorities that request it under the conditions provided for by law.

5.5. Corporate transactions. In the event of a merger, acquisition or sale of business, your data may be transferred to the acquirer, who will be bound by this policy; you will be informed of this.

Article 6 — Transfers outside the European Union

6.1. Your database and your files are stored in the European Union. However, the execution of AI tasks and certain payment processing operations involve a transfer of data to the United States.

6.2. These transfers are governed by one of the safeguards provided for by the GDPR:

  • the European Commission’s adequacy decision of July 10, 2023 on the EU–U.S. Data Privacy Framework, for certified U.S. providers;
  • failing that, the standard contractual clauses adopted by the European Commission (Decision 2021/914), supplemented where necessary by additional measures (encryption in transit, minimization of the data transmitted).

6.3. You can obtain a copy of the applicable safeguards by writing to us at the address given in Article 1. [Drafting note: before publication, check for each U.S. provider its certification on the official Data Privacy Framework list (dataprivacyframework.gov), sign the data processing agreements (DPAs) and carry out a transfer impact assessment for non-certified providers.]

Article 7 — Cookies and local storage

7.1. No cookies set by us. The platform does not use cookies. It uses your browser’s local storage to: keep you logged in; remember your interface preferences (provider and model selected in the chat, groups expanded in the workflow editor, server address, connectors displayed); keep the history of the game content analyzer, which runs entirely in your browser. In the desktop application, the session is kept in the Windows secure vault. In accordance with Article 82 of the French Data Protection Act (loi Informatique et Libertés), this storage is exempt from consent because it is strictly necessary for the service you request. Stripe’s payment page sets its own trackers, which are necessary for payment security and fraud prevention.

7.2. Other trackers. We do not use any audience measurement, advertising or social media trackers; no consent banner is therefore required. If we were to add one, it would be subject to your prior consent, unless it meets the exemption conditions set by the CNIL (the French data protection authority), and this policy would be updated. [Drafting note: to be revisited if an analytics tool is added; a banner would then have to offer “Accept all” and “Reject all” at the same level, with the choice retained for 6 months.]

7.3. Management. You can delete cookies and local storage from your browser settings; you will then be logged out.

Article 8 — Security

We implement technical and organizational measures appropriate to the risks, including:

  • encryption of communications (HTTPS) and of data stored by our hosting provider;
  • isolation of each user’s data through access rules at the database row level (Row Level Security);
  • encryption of connector credentials and personal API keys, with encryption key versioning;
  • storage of Unity plugin tokens in hashed form, with the possibility of revocation;
  • no storage of bank card numbers, which are processed by Stripe;
  • access restricted to authorized personnel only, logging of sensitive operations and regular backups.

In the event of a personal data breach that presents a risk to your rights, we notify the CNIL within 72 hours and, if the risk is high, we inform you without undue delay.

Article 9 — Your rights

9.1. In accordance with Articles 15 to 22 GDPR, you have the following rights:

  • access: obtain confirmation that we process your data and receive a copy of it;
  • rectification: correct inaccurate data, in most cases directly in the account settings;
  • erasure: obtain the deletion of your data, in particular by deleting your account, subject to the data that the law requires us to retain;
  • restriction: request the temporary suspension of a processing operation, for example while a dispute is being examined;
  • portability: receive the data you have provided to us in a structured, machine-readable format, and transmit it to another service; your Assets can be downloaded from the platform as a ZIP archive, and other data is provided to you on request [Drafting note: the code allows ZIP export of Assets; full account export (JSON of Workflows, conversations, etc.) remains to be developed];
  • objection: object to processing based on our legitimate interest on grounds relating to your particular situation, and at any time to direct marketing;
  • withdrawal of consent: at any time, for processing based on consent, without affecting the lawfulness of prior processing;
  • post-mortem instructions: set instructions regarding the retention, erasure and disclosure of your data after your death (Article 85 of the French Data Protection Act).

9.2. Exercising your rights. You can exercise your rights at the address given in Article 1. We respond within one month, which may be extended by two months for complex requests, in which case we will inform you. If we have reasonable doubts about your identity, we may ask you for additional information, preferably by verifying access to the account’s email address rather than requesting an identity document.

9.3. Complaints. If you believe that your rights have not been respected, you may lodge a complaint with the Commission nationale de l’informatique et des libertés (CNIL, the French data protection authority), 3 place de Fontenoy, TSA 80715, 75334 Paris Cedex 07, www.cnil.fr, or with the supervisory authority of your country of residence in the European Union.

Article 10 — Minors

The platform is accessible from the age of 15 (Article 4.1 of the Terms of Use). We do not knowingly collect data concerning children under 15. If you become aware that a child under 15 has created an account, contact us: we will delete it. [Drafting note: to be aligned with the minimum age ultimately adopted in the Terms of Use.]

Article 11 — Changes to this policy

We may update this policy, in particular when a provider or a feature is added. The date of the last update appears at the top of the document. In the event of a significant change (new purpose, new type of data, new transfer), we will inform you by email or within the platform before it takes effect.

Working document prepared on October 27, 2026, to be validated by a lawyer or legal professional before publication.