Privacy
This page describes what data the Mixen services — the public API, the web account and the bot — process, which parts of it are stored, and what you control.
What data is processed
Section titled “What data is processed”To fulfill a request, the service processes its contents: message texts, attachments (base64 images and files, from which text is extracted) and generation parameters. The result is returned in the API response: images as base64 in the body, video and music as a file link once the async job completes.
What is stored
Section titled “What is stored”Public API requests. Each request stores metadata: the model, tokens (input, output, cache), duration, status and the charge — needed for billing and the history in your account. The message texts of API requests are not stored: server-side history is disabled for /v1.
Async jobs. For video and music (/v1/videos, /v1/audio/music) the prompt and job parameters are stored — without them the status could not be shown and the result delivered. The finished file sits in Mixen storage and is accessible only to the key’s owner.
The bot and the web account. Here history is part of the product: chats (threads and messages), attachments and generation history with prompts are stored so everything is in place on your next visit. A limited number of recent generations is kept — older records and files are removed automatically.
API keys. The full key is neither stored nor recoverable: only a sha256 hash, the prefix and the last characters for display in the account.
Where requests are forwarded
Section titled “Where requests are forwarded”Generations are executed by external model providers: the request, along with its context and attachments, goes to the provider of the chosen model, and the answer comes back from it. Which provider serves a given model depends on the model itself.
Logs carry technical events: the model, duration, data volumes, identifiers. API keys and request contents never appear in them.
What you can delete yourself
Section titled “What you can delete yourself”- an entire chat, with its messages and attachments; a single attachment can be deleted on its own;
- image, video and music generation history — one record at a time or all at once, with the files removed together with the record;
- uploaded reference images for generations;
- an API key — deleting it revokes access instantly.
All of this lives in the matching sections of your account.