Privacy Policy

The controller responsible for data processing under the GDPR is the operator named in the Legal notice. The contact details provided there also apply to all privacy-related enquiries.

We process personal data only where necessary to provide the application (Article 6(1)(b) GDPR) or where we have a legitimate interest in secure and functional operation (Article 6(1)(f) GDPR). Content you enter is not used to train models and is not sold.

The application runs on infrastructure of Scaleway SAS (Paris, France) in the Paris region (fr-par). When you access it, technically necessary connection data, including IP address, time, requested resource and user agent, is processed to deliver the application and maintain its security.

Selecting an EU region does not replace a data processing agreement or a review of subprocessors; the processing described on this page is EU-region processing by the named subprocessors, under the operator's agreements with them.

A core function of Flocta is chat with open-weight language models. Your inputs, including chat messages and the text of documents you attach to a request, are sent to the model provider to generate a response. Attached documents are converted to text for the duration of the request and are not stored.

Open-weight models: Scaleway Generative APIs — processing in the EU (Paris, France). Processing takes place within the EU. Flocta chooses the model for each request from the models available to your workspace; that choice is made without sending your content anywhere.

Models you connect yourself: if you connect your own credentials for a third-party model provider under Connections, requests routed to that provider are sent to it under your own agreement with that provider. Depending on the provider, this may involve a transfer to a third country (for example the United States), which may include personal data contained in your inputs. Your credentials are stored encrypted and are referenced everywhere else only by an opaque identifier.

Your workspace, account and connection data, and a usage ledger, are stored in a database operated by Scaleway (Managed Database for PostgreSQL, Paris). The ledger records one entry per model call: which model answered, the tokens used, the cost and the time — never the prompt or the answer.

Whether conversation text is kept on the server is a setting of your workspace (Settings, “Chat history”). By default (“This browser only”) the server keeps only a conversation's metadata — when it was created and last used, how many turns it has and which model answered last — and the messages themselves stay in your browser (see Local browser storage). If the workspace chooses “Keep on the server”, conversation titles and messages are stored so a conversation opens on any device. Turning the switch off does not delete what was stored while it was on; you can delete a conversation at any time, which removes it from the server.

Technical error reports are sent to Sentry (EU data region) and request traces to Langfuse (EU cloud) and the operator's own telemetry. By default (Settings, “Retention”: “Metadata only”) these carry which model answered, the tokens, the cost and timing — never a prompt or an answer. Only if the workspace opts into “Content may appear in logs and traces” may prompts and answers appear there, for debugging and evaluation. Credentials are redacted before an error report leaves the application.

Registration and sign-in are handled by Zitadel (Zitadel Cloud, EU region) as identity provider. When you register or sign in, Zitadel sends us the data authorised for sign-in, generally your email address and name. Passwords are entered on the identity provider's pages only and are never sent to Flocta. Zitadel acts as an independent controller for its own processing.

After sign-in, Flocta sets an encrypted session cookie in your browser. It is strictly necessary to keep you signed in, is not used for any other purpose and is removed when you sign out or when it expires.

Flocta stores certain settings and, by default, your conversation text locally in your browser, in localStorage. These are functional values only: your selected colour scheme (flocta.theme), the sidebar state (flocta.sidebar.collapsed), whether the introduction has already been viewed (flocta.intro.seen), and — while your workspace keeps chat history in the browser only — the messages of your conversations (flocta.chat.bodies.*) so they persist between sessions on this device.

This storage is strictly necessary for the operation of the application that you expressly requested. No cookies or identifiers are set for analytics, tracking or advertising, and none of this data is shared with third parties. Under Section 25(2)(2) TDDDG, no consent is therefore required; for this reason, Flocta does not display a cookie banner. You can delete this local data at any time through your browser settings.

Subject to the statutory requirements, you have the right of access (Article 15), rectification (Article 16), erasure (Article 17), restriction of processing (Article 18), data portability (Article 20) and objection (Article 21 GDPR). To exercise these rights, contact the party named in the Legal notice.

You also have the right to lodge a complaint with a data-protection supervisory authority (Article 77 GDPR).

Because the range of functions and services may change, we update this policy where necessary. The services listed in this version reflect the current technical operating state.