Privacy Policy

We keep your random account hash, internal username, password or legacy PIN hashes, session records, hashed API keys, usage totals, account restrictions and support adjustments. New signups also record the policy version, acceptance time and 18+ confirmation time. We do not ask for your date of birth or identity documents at signup; the age confirmation is self-declared, not identity verification.

Our application does not persist IP addresses in account sessions or create browser fingerprints. IP addresses may be processed temporarily for rate limiting. New sessions do not retain browser user-agent metadata; older session records may contain it until those sessions are purged. Hosting and anti-bot services necessarily process connection information and may maintain their own security records.

Website chat stores conversations to display your history. Each chat expires 24 hours after creation; sending another message does not extend its lifetime. Expired chats are excluded from history and cannot be continued. Cleanup deletes the conversation, title and message rows from our active chat database every five minutes and when you request history. Scheduled cleanup can be delayed by service outages. Use Delete in chat history to remove a chat and its messages from the active database immediately; this cannot be undone. This action does not erase infrastructure backups or copies processed by external services; those follow their own retention periods. Usage, token counts and billing metadata may remain for accounting and disputes.

The API and official CLI do not write prompt or response bodies to our chat-history database. Requests still pass through our servers and model-serving services to produce an answer. This is not a promise that every external service, infrastructure log or backup retains nothing.

The CLI saves conversations and tool results locally on your computer for resume. Set UNJAILED_NO_HISTORY=1 to disable local conversation saving. Files, commands and data you authorize the CLI to use can become part of the model request. Avoid submitting secrets or information you are not allowed to share.

Daily usage aggregates are scheduled for removal after 90 days. Expired or revoked login sessions are eligible for cleanup after one additional day. Account, consent, payment and ledger records remain while needed to operate accounts, resolve disputes and meet legal obligations.

We retain payment references, amounts, statuses, wallet ledger entries and subscription records. Crypto transactions are generally recorded on public networks and can reveal transaction relationships. Payment processors may collect billing, identity or compliance information under their own policies. Signup without an email is not a guarantee of anonymous payment.

We do not store full card numbers or card security codes. Support information you send through Discord or Telegram is processed through those services as well as by us. Send the minimum needed to investigate your issue; never send passwords, API keys or illegal material.

We use records to authenticate accounts, answer requests, bill usage, apply safety controls, resolve support issues and prevent abuse. We do not use your chat content to train our own models or sell it for advertising. Model-serving, hosting, database, anti-bot and payment services receive the information needed for their functions.

Limited access by authorized operators may be needed for support or security. We may preserve or disclose relevant records when required by law or to address unlawful abuse. Service providers may process information in other countries. We do not claim complete anonymity, end-to-end encryption of model requests or perfect security.

We use first-party conversion measurements to understand signup flow: CTA clicks, registration visits, completed accounts, verified first top-ups and the first recorded successful API request. Browser events use a random session identifier and page placement, not prompts, API keys, card details or stored IP addresses. Signup attribution can be linked internally to the account; funding milestones are read from existing billing records. Successful API milestones retain only account ID, model ID and time, never prompt or response bodies. No third-party advertising tracker is loaded. A browser Do Not Track setting disables browser click and visit tracking; an API request with DNT: 1 also skips the API milestone. Private contact-form messages and an optional reply handle are stored for support, privacy, billing, abuse or business requests, accessible only to the owner.

We use an essential login cookie and local browser storage for interface preferences. The anti-bot service may use its own security mechanisms. You can log out, revoke API keys, cancel subscription renewal and disable local CLI history. Removing a browser cookie or a CLI file does not delete payment records.

Request account access, correction, closure or deletion through support. We will verify control of the account and consider rights that apply in your jurisdiction. Records required for billing integrity or legal obligations may need to remain. We cannot recover an account from a name or email that was never supplied.

The service is for adults aged 18 and over. Do not submit children's personal information unnecessarily or provide access to minors. Report suspected underage access or a privacy/security problem through Discord support · Telegram support.

We will update this page when our practices change and provide notice of material changes. Where a new use of data requires consent, we will obtain it.