Privacy

Operator and contact

Include your account email and describe your question. Do not send a password, MCP token, or other secret.

Account and sign-in

Registration processes email, password, and consent. An account has an identifier, normalized address, password hash, role, restriction state, and timestamps. Sign-in uses a protected session cookie; the server checks it for the account page and administrative actions. Signing out ends the session.

Personal MCP tokens

The full token value is shown once at issuance. The service stores its hash and connection metadata: owner, name, short prefix, dates, and revocation status. The client sends the token in an authorization header. Do not include it in a task, URL, or support message.

Tasks, models, and knowledge

Data sent to tools may enter your selected model’s context and be processed by its provider under that provider’s terms. Remove passwords, keys, customer data, and unnecessary personal information. Connected accounts can read the published shared library. Tasks and history are isolated and are not published to the shared library. Only validated knowledge from public sources may be added to the permanent shared library, through separately authorized research or an operator-reviewed transfer. New knowledge added to the shared library is not automatically deleted when a task ends. The full account beta provides 13 MCP tools, including ranked preparation of saved knowledge and the research caller workflow. Every new research task requires separate explicit consent to its gap, benefit, and duration; a new task over 600 seconds requires separate approval of its total duration. Document import is unavailable in the account MCP. Keep personal and project documents in the AI host chat or workspace. Never put personal information, secrets, customer details, or private project content in public profile name, scope, or topics. Send only the minimum general technical question. Account jobs, caller actions, and KnowledgeSession state remain owner-isolated operational data. This policy does not delete existing history. The AI host controls its own conversation memory and retention; MCP cannot guarantee its isolation or deletion. Export and operator-managed knowledge changes require separate approval.

Website and games

A copy button writes selected text to the clipboard only after you select it; the site does not read the clipboard. A game loads into a separate isolated frame after you select its button. Account data and tokens are not passed to the game.

Access and requests

You can revoke a token and end a session from your account. Revocation blocks new checks with that token; a request already authorized may finish. It does not by itself delete an account, tasks, or saved knowledge. For an account or data request, email css1996@list.ru and say what action you are requesting. Do not send secrets.

Service analytics

To operate and improve the service, we record confirmed registrations, token issuance and revocation, plugin requests, responses with context, jobs, and data-source status. We also count requests to designated public HTML pages and store the selected signup-source category from a fixed low-confidence list. An event is linked to an account only when the server confirms that identity. Authorized administrators can view summary measures and limited operational records.

Analytics records do not contain email addresses, passwords, session cookies, MCP tokens, IP addresses, User-Agent strings, visitor identifiers or fingerprints, task or response text, prompts, full URLs, arbitrary error strings, request bodies, context hashes, knowledge IDs, arbitrary UTM tags, or referrer text. For public pages, only a predefined page category is counted; signup source is stored as one of a fixed set of values.

Raw analytics events are kept for up to 30 days. Account-linked daily summaries, milestones, and all copies of job and new-source analytics facts are deleted no later than 90 days after creation. The source retry queue is kept for up to 7 days, and ownerless deduplication receipts for up to 9 days. The current account category is kept until account deletion; its change history is kept for 90 days.

To request correction or deletion of account data, email css1996@list.ru and provide the account email and requested action. Do not send a password or token.

Correction and deletion requests

To request correction or deletion of data, email css1996@list.ru and provide the account email and the action you are requesting. Ending a task or revoking a token does not submit a deletion request. Do not send a password or token.