Privacy and data

This page describes the data used by FuturAI’s current features. The operator’s legal identity, a dedicated privacy contact and retention periods still need to be specified. No compliance certification is claimed.

Clerk handles sign-in. FuturAI stores an account identifier, an email address and the profile information you provide: username, photo, country, biography and links. FuturAI does not manage passwords directly. Ideas, projects, contributions, votes, discussions, comments, challenge entries and Arena sessions are stored so they can be viewed and tracked. Some of this information is public, depending on the feature or setting you choose.

Account data lets you sign in and links contributions to your profile. Stored content supports collaboration, version history and community features. Language preferences select the French or English interface. Technical information may be processed to protect the service and limit abuse.

API keys added in settings are encrypted in the database using AES-256-GCM. When you generate content in the Arena, the server decrypts the key to call your selected provider. Key encryption does not mean your prompts are end-to-end encrypted. Authentication, access controls and isolated previews reduce risk. They do not guarantee that incidents cannot occur. Do not include secrets, sensitive personal data or confidential documents in prompts or public posts.

The “locale” cookie remembers your language choice for one year. Clerk uses its own cookies for sign-in. Ollama mode keeps creations in this tab’s memory. They disappear when you leave or reload the page unless you have downloaded the HTML files.

Clerk handles sign-in. Vercel hosts the application. Platform data is stored in a PostgreSQL database. These services have their own privacy policies and retention settings. In the Arena, your prompt and the information needed for generation are sent to your selected AI provider. Its terms, pricing and retention policy apply. External images and links you open may also contact third-party services.

In the local workshop, AI requests go directly from your browser to Ollama on your computer. This mode uses a locally installed model and does not send these requests to FuturAI’s AI APIs. Results stay in the tab until you choose to share them. Preparing publication temporarily saves the selected version in your browser; only submitting the form sends the prototype to the site and makes it public with your project. Browsing FuturAI remains normal web browsing. Downloading Ollama or a model uses the corresponding distribution services. You are responsible for the HTML files you download.

Account data and stored content remain in the database until deleted. The “My data” page lets you initiate deletion of your Clerk account and associated application data. Some audit logs remain after this operation. Provider logs, backups and copies follow those providers’ own policies. Copies already downloaded or shared by other people cannot be removed through FuturAI. Retention periods for these items still need to be specified.

You can edit your profile, remove an API key in settings and download a JSON export from “My data”. The export includes the categories listed on that page; it is not a copy of every log or record held by service providers. You can also request account deletion from “My data”. See the previous section for the limits of this operation.

The operator’s legal identity and a verified channel for personal data requests need to be published here. No data protection officer or specific response time is claimed. The site’s discussions let you ask about using FuturAI. This space is public: do not use it to share API keys, personal data or confidential documents, or to make a private request about your data.