Skip to content
FluxCDNFluxCDN
esc

Legal

Privacy Policy

Last updated 15 August 2026

What we collect, what we deliberately do not collect, and what leaves our systems when a request is routed.

Placeholder document. This is a structural draft written alongside the product, not reviewed legal text. It must not be published or shown to a customer until counsel has replaced the body.

What we do not store by default

Prompt and completion bodies are not persisted. They pass through the gateway in memory, are forwarded to the selected provider, and are discarded. Logging of message content is off unless you explicitly enable it on a project. There are two exceptions. In FluxCDN Chat (ai.fluxcdn.cloud/chat) your conversations (what you write, the answers, and the images and PDFs you send or create) are saved, encrypted, so you can come back to them. Only you see them, in the workspace they belong to. You can delete any chat, or all of them, at any time; a deleted chat is erased for good within a day. In FluxCDN Studio (ai.fluxcdn.cloud/studio) your projects (the pictures, clips and films you upload or make there, and their prompts) are saved the same way, encrypted and seen only by you; you can delete any of them at any time, and a project left untouched for 90 days is erased, after an e-mail a week before. Prompts you save under “My prompts” in the prompt library are kept the same way, encrypted, until you delete them. If you write custom instructions or turn on Memory in FluxCDN Chat (it stays off unless you turn it on), those instructions and the short facts Chat remembers about you are kept the same way, encrypted and for you alone; they are used in all your workspaces and sent to the model with your chat messages, and you can see and delete any or all of them at any time in the chat's settings. A temporary chat is not kept in your history, does not use or add to memory, and is erased within a day. Requests sent with an API key or from the console's playground are never saved.

What we do store

Per request we retain the metadata needed for billing, routing and support: requested and resolved model, provider, account and region; token counts by category, cost and margin; time to first token, total latency and the attempt chain; response status and normalized error code; and the routing and pricing snapshot applied.

Account data

Name, email, organization membership, and payment metadata held by our payment processor. We do not store full card numbers.

What reaches an upstream provider

The content of your request reaches whichever provider serves it, under that provider's own data terms. Provider retention posture is published per provider, and organizations can exclude providers that train on inputs or pin traffic to a region.

Retention

Request metadata is retained for the period configured on your organization, then aggregated and the detail dropped. Audit logs follow their own retention. FluxCDN Chat conversations are kept until you delete them, or until your account or workspace is deleted. FluxCDN Chat custom instructions and memories are kept until you delete them or your account is deleted (turning memory off does not delete them). FluxCDN Studio projects are kept until you delete them, or at most 90 days after their last use (with an e-mail a week before they are erased).

Your rights

Access, correction, export and deletion requests are handled through support. Deleting an organization removes account data and request detail; aggregate financial records are retained where law requires it.

Contact

Privacy questions and data subject requests go to info@fluxcdn.cloud.