Any LLMOpen chat ↗

Privacy policy

This policy describes data processing when you use any-llm.online and chat.any-llm.online. For personal data questions, contact support@any-llm.online. Details of the data controller are listed on the contacts page.

What data is processed

For accounts: email address, username, Google identifier when signing in through Google, a secure password hash, and session data. For chat operation: message text, selected models, conversation history, and technical information about generations. For payments: payment information and the access period. The payment service processes card or cryptocurrency wallet details.

Abuse protection uses a signed guest cookie and a cryptographic code derived from the network address. Analytics records permitted events and information about the referral source without prompt text. Raw IP addresses are not stored for these statistics. Temporary limits on attempts and concurrent requests may be shared by guests on the same network.

Yandex Metrica runs in the main site window on public pages, New chat, conversations, and Antislop. Microsoft Clarity runs on public pages and chat pages on any-llm.online, excluding Antislop and the developer dashboard. Metrica Session Replay and Clarity record interface interactions, clicks, and scrolling. Conversation text, attachments, and input fields are marked for masking in Metrica. Submitted messages and model responses may be visible in Clarity recordings. Clarity masks input fields and dropdown lists. Masking does not guarantee that all confidential information is hidden. Sign-in, account settings, administration, and payment screens are excluded from recording. Analytics scripts run on the page and can observe its address and content. Explicit Metrica events use a normalized conversation path and a limited set of campaign fields. Public pages may also use Cloudflare Web Analytics and Google Analytics if enabled in the site settings. Google sign-in and payments use external services with their own data processing rules.

Why data is needed

Data is used for account sign-in, providing the service, saving chats, applying limits, confirming payments, support, security, and analysis of site operation. Prompts and the necessary context are sent to the connected model provider to obtain a response. If local processing is unavailable, limited context, including excerpts from attached documents and output from an executed script, may be sent through OpenRouter Free for search selection, image generation, generating a short chat title, fixing a script, or explaining its output. This can also happen when a local model is selected for the main response. For web searches, the search query formulated by the model is sent to Tavily, Exa, or DuckDuckGo. For reading and crawling a site, the specified address is sent to Firecrawl. Automated browser actions, including filling in forms, are currently unavailable. Payment information is sent to the selected payment service. Google sign-in uses the data needed to verify the account.

Storage and your requests

Access to data is limited to the purposes of the service. Sessions and one-time codes expire. Analytics events are deleted after 180 days and visitor aggregates after 30 days. The security log records administrator access and web tool operations without conversation text. Chats with generation history and payment records are retained to provide the service, account for transactions, and protect the parties’ rights. To request information about your data, corrections, or deletion within the limits of applicable law, email support@any-llm.online from your account’s email address.