Privacy

Privacy & Cookies

CocoAI is built so your conversations stay yours. This page lists exactly what stays in your browser, what leaves it to produce an answer, and the controls you have.

Updated 24 October 2026

Chat history is encrypted on your device
The server keeps no conversation history
Only first-party cookies for security and preferences — no analytics or ads
Abuse limits use short-lived counters

What stays on your device

Conversations live in IndexedDB (cocoai-chat-history), encrypted with AES-GCM. The key is created on this device and cannot be exported. Up to 30 conversations are kept, with the most recent 150 messages in each. Older entries are removed.
The Image Studio gallery (up to 40 images) and Deep Research run records (up to 20) use the same encrypted store. Run records power the “Changed since” source diff.
Theme, language, composer mode/model and the active conversation id sit in localStorage. They never contain prompts or answers.
Deleting a chat, clearing all history or clearing the gallery in the workspace removes the matching records. Clearing site data in your browser removes everything.

Cookies and local storage

coco-session: Essential. Ties a request to this browser session. HttpOnly, SameSite=Strict, Secure on HTTPS. Expires after 24 hours.
coco-theme: Remembers light or dark. Lasts 1 year and is mirrored in localStorage so the first paint matches your choice.
coco-locale: Remembers English or Thai. Lasts 1 year.
localStorage: The active conversation id and composer mode/model. No prompts, answers, keys or gallery data.
No tracking: No analytics, advertising or cross-site tracking cookies are set.

What the server processes

The prompt and the recent turns you choose to send are processed to produce the answer. Chat is stateless: no conversation database and no file cache. Server logs exclude prompts, message bodies, tickets, entropy and session tokens.
Research modes send the question to retrieval services and the selected model to build a cited answer. Image mode sends the prompt, plus an attached image if you add one, to the image service. Returned images are served through random links bound to your session, never the original provider URL.
A proof-of-work handshake issues a one-time ticket that expires in about 25 seconds and is burned on first use. Rate limits and guest quotas use counters keyed by session and IP; daily counters reset at 00:00 UTC and a shared budget protects the demo.
Connections use HTTPS, and security headers restrict scripts, framing and referrers.

Third parties

Model, research and image providers process the prompt or attachment only to return the result. We never send your stored history, account credentials, provider tokens or cookies.
The hosting platform and its managed data store process standard request data — IP address, user agent and timestamps — to deliver responses, keep shared limits and block abuse.

Retention

History, gallery, runs: On your device until you delete them or clear site data.
Session cookie: 24 hours.
Theme and language: 1 year, or until you clear cookies.
Challenges and tickets: About 25 seconds.
Rate-limit buckets: Minutes, per window.
Daily guest counters: Until 00:00 UTC.
Downloaded evidence packs: Files on your device, kept wherever you save them.

Your controls

Delete individual chats or clear all history from the sidebar; clearing all also removes Deep Research run records.
Delete generated images from Image Studio.
Evidence packs are files you download; they contain the answer, sources and a signature. Share them deliberately.
Clearing cookies and site data in your browser removes the session and preferences and starts a fresh workspace.

Questions about this page?

Ask about data, deletion or security — email is the fastest route.

mienetic.dev@gmail.com