Privacy Notice
Last updated: November 22, 2026 · Applies to Aspen
This notice explains what this site stores, why, and what we do not do with it. It is meant to be read together with the Terms of Use.
1. What we collect
- Your messages: the prompts you send and the answers you receive.
- Files you upload: images and documents, plus the text we extract from documents so the model can read them.
- Technical data: IP address, browser user-agent, timestamps, and request counts used for rate limiting.
- Cookies: a session cookie, a CSRF cookie, and — if you use the preview without signing up — a long-lived preview cookie that acts as your account identifier. They are not used for advertising.
- Credits: your credit balance, check-in days, and the ledger of grants and spends (amount, reason, timestamp, expiry).
- Support messages: the text you send through the support window, the topic you pick, the page you were on, the email address you leave (if any), and our replies.
- Preferences: interface language and theme, stored in your browser.
- Usage records: which model was used, token counts, latency, and whether the request succeeded.
2. Why we use it
- to generate answers and show your chat history;
- to enforce daily and per-minute limits and stop abuse;
- to keep the service secure and debug failures;
- to understand overall load (aggregate counts only).
3. What we do not do
- We do not use your prompts or outputs to train or fine-tune models.
- We do not sell your data or share it with advertisers.
- We do not ask for your real name, phone number, or payment details during the preview.
To produce an answer, your prompt is sent to a third-party model provider. That provider processes it under its own terms and privacy policy. We cannot control what that provider does, and you should not send it secrets or sensitive personal data.
4. Retention
Retention is not guaranteed. We may delete chats, logs, uploads, generated images, and preview sessions at any time, for example during maintenance or a cleanup job. Preview accounts are deleted after roughly seven days of inactivity. Files attached to a chat are deleted with that chat; uploads that are never sent are removed after about 24 hours, and generated images after about 30 days. Credits expire seven days after they are granted, and the ledger rows are kept only for bookkeeping. Support tickets that are closed are removed after about 180 days; open tickets, and any ticket, may be deleted sooner. We do not promise backups. In general we keep usage logs for up to about 180 days and email records for up to about 30 days, but this can change and data may disappear sooner. Do not rely on this service as storage.
5. Who can see it
The operator of this deployment and whoever they authorise may access stored data for security, abuse prevention, debugging, or legal compliance. Hosting and infrastructure providers process data on our behalf. To generate an answer, your prompt and any document text we extracted may be sent to a third-party model provider under its own terms. We may disclose data if required by law or to protect the service and its users.
6. Security
Passwords and keys are hashed or encrypted, sessions are HttpOnly, and access to the server is restricted. Still, no system is perfectly secure. We cannot guarantee that a breach will never happen, and to the maximum extent permitted by law we are not liable for unauthorised access to data you chose to send.
7. Children
The service is not directed to children under 13 (or under 16 in the EEA/UK). If you believe a child has sent us personal data, contact the operator so it can be removed.
8. Your choices
You can clear cookies in your browser at any time; that ends your preview session. You can ask the operator to delete data associated with you, but because retention is not guaranteed we may not be able to recover or identify old records.
9. Changes
We may update this notice. The “last updated” date above will change. Continued use after an update means you accept the revised notice.
10. Contact
For privacy questions or deletion requests, use the contact details published by the operator of this site.