Privacy Policy

What data Mixer AI processes, why it is needed, and how to contact us about your data.

1. General provisions

This Policy applies when you use the Mixer AI website, the web application, the Telegram bot, the official Mixer AI Chrome extension, and the connection of Mixer AI to assistant applications via the MCP protocol. By continuing to use the Service, the user confirms that they have read the Policy. If processing is necessary for a requested feature to work, declining to provide the data may make that feature unavailable.

2. What data is processed

• account identifier, username, display name, language and authorization details;
• email address and the identifier of an external account, if the user has chosen the corresponding sign-in method;
• prompts, uploaded files, generation results, Canvas projects and activity history;
• payment data: amount, status and transaction identifier; the Service does not receive full bank card details;
• IP address, browser and device type, date and time of the request, diagnostic information and security events;
• the content of support requests and information voluntarily provided by the user.

The Service does not request special categories of personal data. Sensitive data should not be included in prompts unless it is needed for the chosen feature.

3. Purposes and grounds of processing

Data is used to fulfil the user's request, provide sign-in and a shared balance across the website and the bot, save projects and history, process payments, return coins in the event of a confirmed error, respond to support requests, prevent abuse and maintain the security of the Service.

Grounds of processing: performance of the public offer accepted by the user and of the actions requested, compliance with legal obligations, security, and the user's consent where it is required, in particular for optional analytics.

Mailings. By registering or signing in to the Service with an email address or Google, the user agrees to receive emails at that address about new features, educational live sessions, promotions and offers from Mixer AI. Consent can be withdrawn at any time via the “Unsubscribe” link in any such email or through Telegram support. Opting out of mailings does not affect service emails: sign-in codes, security notifications and payment notifications.

4. Automated processing and contractors

To perform generations, request data is processed automatically. For certain features the Service may engage technical contractors, including for infrastructure, authorization, payments, message delivery, analytics and content processing. They receive only the information necessary for the relevant operation.

The Service does not take decisions on the basis of a generation that in themselves create legal consequences for the user. The user independently checks the automatically created result.

5. Retention periods

• ordinary uploaded and generated media files: up to 10 days;
• media files saved in Canvas projects: up to 50 days; the project structure and its settings may be kept until the project is deleted or the user requests deletion;
• temporary text context of certain features: up to 3 days;
• content of prompts and results for which automatic cleanup is enabled: as a rule, up to 30 days; individual records may be kept longer for the history of the operation, security, dispute resolution, or while the cleanup mechanism is running in verification mode;
• raw analytics events: up to 90 days; technical request records: up to 30 days; visitor identifiers: up to 180 days;
• account, balance, payment and support-request data: for as long as they are needed to operate the Service, resolve disputes and comply with mandatory requirements.

Retention periods when working through ChatGPT, Claude, Cursor and other MCP clients are set out in section 8.

The period runs from the creation or last update of the relevant record. Backups and records that must be kept for accounting purposes may be deleted later, within the technically and legally necessary period.

6. Cookies and analytics

Necessary cookies and local storage are used for sign-in, security, language, the interface and saving selected settings. They work without separate consent because some features are unavailable without them.

Optional analytics is enabled only after the user clicks “Accept” in the banner. The browser stores the selected option and the time of the choice. If the user selects “Necessary only”, external analytics tools are not loaded. External fonts and other presentation resources may be loaded regardless of the analytics choice.

7. The Mixer AI Chrome extension

To sign in, the extension opens a secure MixerAI page where the user chooses Telegram, email or Google and separately confirms the connection. The extension receives from the MixerAI backend a short-lived access token and a refresh token. The access token is stored in Chrome session storage, and the refresh token in the extension's private local storage. On sign-out, the tokens, the user's draft and the local history cache are deleted.

The extension sends to the MixerAI backend only the data necessary for the selected feature: account and balance information, prompts, model parameters, uploaded photos, video and audio, request status and results. To perform a generation, the backend may pass the prompt and input files to the relevant generation provider, as described in section 4. Payment is made on the MixerAI website, not inside the extension.

Locally, the extension may store the language, theme, selected model, parameters, the prompt draft and the metadata of the three most recent results. Raw selected files are not stored locally. The extension does not request or collect the URLs of open tabs, browser history, the content of third-party sites or the cookies of other sites; content scripts are not used.

8. Use through ChatGPT, Claude, Cursor and other MCP clients

The user may connect their Mixer AI account to a third-party assistant application that supports the Model Context Protocol (MCP), in particular ChatGPT, Claude or Cursor. The connection is made through the Mixer AI authorization page using the OAuth protocol. The application receives access limited in scope and authorized by the user; it must not receive the password for the Mixer AI account or full bank card details.

What data is processed. When connecting and when calling MCP tools, Mixer AI processes the identifiers of the user and the linked account, the identifier of the connected application, the list of granted access scopes, information on the granting and revocation of access, and technical security and request-execution records. Access may permit reading the profile and the model catalog, viewing the user's own generations and media, uploading media and submitting jobs within the selected scopes. The connection itself does not constitute consent to paid generation.

The Mixer AI server receives the data that the MCP client sends for the specific requested action: the text of the task or the fragment of it relevant to the operation, the parameters of the selected model, the names and technical characteristics of files, source photos, video or audio if they have actually been transferred in an authorized way, and the identifiers of projects, jobs and results. The presence of an attachment in a chat does not guarantee that its original bytes are transferred to the Mixer AI server; transfer depends on the capabilities of the client and the user's permission. Mixer AI does not automatically receive the entire conversation in the third-party application. However, the MCP client itself may include in a tool call the context needed for the action, so the user should take into account the privacy rules of the application they use.

Purposes of processing. This data is processed to verify authority, select available features, upload input materials, calculate and confirm the cost, perform generation, store results available to the user, operate Canvas and history, prevent abuse, resolve errors and handle support requests. The response to the client may contain data on permitted features, the price in coins, the status of the job, projects belonging to the user, as well as results or temporary links to them. Secret access keys must not be output in ordinary tool responses.

Technical contractors. To the extent necessary for the requested feature, data may be processed by technical contractors in the following categories: hosting and infrastructure, secure storage and delivery of files, processing of images, video, audio and text, security and moderation, authorization, diagnostics and, where coins are purchased on the website, payment infrastructure. Contractors receive only the data necessary for the relevant action. Some operations may involve the transfer of data across national borders.

ChatGPT, Claude, Cursor and other applications may independently process the conversation itself, their own diagnostic data and attachments in accordance with their own documents. Their processing outside an MCP call is not governed by this Policy.

Retention periods when working through MCP clients.

• uploaded input photos, video and audio not attached to Canvas: up to 1 day; the limits of a particular model may be stricter;
• media files created in ordinary MCP mode and available for download or repeated viewing: up to 10 days;
• media files attached to a Canvas project: up to 50 days; the project graph, its titles and settings may be kept until the project is deleted or the user makes a request, unless a different period applies to them;
• request metadata, generation history, balance and coin transactions, authorization records, service logs and information required by law are kept for the periods stated in section 5 and in accordance with the obligations in force. The expiry of a media file does not in itself mean that the record of the generation or payment is deleted at the same time.

The periods are counted for the relevant files and the links to them. Physical deletion may take into account other valid references to the same file, backups, technical delays and mandatory statutory retention periods.

Revocation of access and user requests. The user has the right to disconnect the integration in the settings of the third-party MCP client and, separately, to revoke the granted OAuth access in the Mixer AI profile, under “Connected Apps”. Revocation ends the use of the permission for new requests, but does not cancel operations already performed and does not in itself erase the history and results already stored. Revoking OAuth access is not the same as deleting the Mixer AI account and does not manage the chat history kept by the third-party application.

To request access to their data, correction, an available export, deletion or clarification of a retention period, the user may contact Telegram support. Confirmation of identity may be required to protect the account. Deletion is carried out subject to technical periods and statutory obligations.

Coins. Coins are purchased on the Mixer AI website. MCP tools may show information about the balance and charges, but must not collect the user's bank details or complete the purchase of new coins inside the assistant. A separate confirmation of the exact cost is required before existing coins are spent.

9. User rights

The user may request information about their data, its correction, an export in an available, technically usable format, or deletion. The request is sent through Telegram support. To protect the account, the Service has the right to request confirmation of identity.

A request may be fulfilled only in part if retention is necessary for payment accounting, security, compliance with the law, dispute resolution or the protection of rights. Deleting data that is necessary for the account to function may result in loss of access to the corresponding features.

10. Protection and changes

The Service applies reasonable technical and organizational protection measures, including access restriction and secure data transmission. No method of storage eliminates risk completely; if a problem is discovered, the Service takes measures proportionate to its nature.

The current version is published on this page and takes effect from the date of publication. Material changes apply to further use of the Service.

This is an English translation of the Russian original. If the two differ, the Russian version prevails.

Version of October 29, 2026.