this page explains what data cirus collects, why, how long it is kept, and your rights. cirus is operated by an independent individual, not a company.
| data | why | retention |
|---|---|---|
| session id (random uuid in cookie) | identify your browser across requests, link your conversations | up to 1 year, or until you clear cookies |
| ip address | rate limiting, abuse prevention, security | indefinite (tied to session) |
| messages you send | generate ai responses, maintain conversation context | indefinite, unless you request deletion |
| ai responses | display to you, allow conversation history | indefinite, unless you request deletion |
| archived conversations from locked sessions | evidence retention, abuse investigation, legal compliance | indefinite |
| timestamps | rate limiting, debugging | indefinite |
| basic server logs (nginx) | security, debugging | up to 30 days |
cirus sets a single first-party cookie named cirus_sid. it stores a random session identifier, is httpOnly and secure, and expires after one year. clearing your browser cookies removes it. cirus uses no third-party cookies.
all data (conversations, sessions, usage counters) is stored in a sqlite database on a virtual private server operated by the cirus team. ai inference happens on the same server or a paired secondary server (also operated by the cirus team). nothing is sent to openai, anthropic, google, or any other third-party ai provider.
only the operator of cirus has access to the database. data is not sold, shared, rented, or disclosed to third parties, except:
cirus runs language models locally on its own infrastructure. your messages are not transmitted to any external ai api. the underlying open-weight models (currently llama 3.2 and qwen 2.5) were trained by meta and alibaba respectively, but the operators of those companies have no access to your conversations.
cirus is not directed at children under 13. if you are under 13, do not use the service. if a parent or guardian believes their child has used cirus and wants the data deleted, contact the operator (see section 11).
cirus uses tls (https) for all traffic. inference servers communicate over an authenticated channel. the database is access-controlled at the operating-system level. however, no system is perfectly secure. do not submit secrets, passwords, government identifiers, financial details, medical records, or anything you would be unwilling to see leaked.
depending on your jurisdiction (eu/uk gdpr, california ccpa, etc.) you may have the right to:
to exercise these rights, contact the operator using your session id (visible in the cirus_sid cookie in your browser dev tools).
active conversation data is kept for as long as the service operates. you can drop your local session at any time by clearing your cookies for cirus.onl, but conversations remain in the database under the old session id until you contact the operator for deletion.
locked sessions are exempt from deletion requests. when a session is locked due to policy violations, all conversations from that session — including the full message content, ip address, timestamps, and severity scores — are archived to a secure location on cirus servers and retained indefinitely. this data may be used as evidence, shared with law enforcement under valid legal process, or referenced in moderation appeals. deletion requests for locked-session data will not be honored unless required by applicable law.
if cirus is shut down, active conversation data will be deleted within 30 days. archived locked-session data may be retained beyond shutdown for legal compliance.
privacy questions, deletion requests, or data access requests: contact the operator on discord (user id 1411411326344892476) or by email at the address listed in dns whois records for cirus.onl. include your cirus_sid cookie value so the request can be matched.
this policy may be updated at any time. material changes will be flagged on the homepage for at least 7 days.