Format processing locations
| Format | Processing location |
|---|---|
| Markdown | Local (in your browser) |
| HTML | Local (in your browser) |
| TXT | Local (in your browser) |
| JSON | Local (in your browser) |
| CSV | Local (in your browser) |
| PNG | Local (in your browser) |
Secure cloud API (api.getchatcache.com); content not stored |
What is stored locally
ChatCache uses the Chromestorage API to persist two things on your device:
- Export preferences — your selected format, copy-to-clipboard toggle, file name prefix, and similar settings
- Anonymous install ID — a stable identifier used for quota enforcement and abuse prevention
What is sent to the server (PDF only)
When you export to PDF, your conversation content is sent toapi.getchatcache.com for server-side rendering. The rendered PDF is returned to your browser for download. Conversation content is not persisted on the server after the PDF is generated and returned.
The PDF rendering backend retains limited data for security and quota enforcement:
- The anonymous install ID (to enforce per-install usage quotas)
- Hashed, IP-derived rate-limit and abuse-prevention records
- Token usage and security-event logs
No tracking
ChatCache does not use any third-party analytics, advertising, or tracking tools. PDF rendering is handled by ChatCache’s own infrastructure. Your conversations are never shared with advertisers or external data processors. For a full breakdown of the browser permissions ChatCache requests and why, see Chrome permissions.ChatCache includes an optional feedback form. If you choose to submit feedback, you may provide an email address and a message. This submission may be processed by third-party form infrastructure. Submitting feedback is entirely optional and unrelated to how your conversations are handled during export.