How ChatCache handles your data
ChatCache is a browser extension that reads the ChatGPT conversation currently displayed in your browser tab. It does not connect to the OpenAI API, does not access your account, and has no visibility into conversations you have not opened.
The processing model differs by export format:
| Format | Where processed | Data leaves device? |
|---|---|---|
| Markdown | Local (browser) | No |
| TXT | Local (browser) | No |
| HTML | Local (browser) | No |
| JSON | Local (browser) | No |
| CSV | Local (browser) | No |
| PNG | Local (browser) | No |
| Server-side render | Yes - not stored after delivery |
The PDF export exception
PDF generation requires server-side rendering because browsers cannot natively produce paginated PDF files with correct typography and code formatting. ChatCache routes PDF exports through a secure rendering API:
- The conversation is sent to the rendering API to generate the PDF
- The PDF file is returned to your browser immediately
- No conversation data is logged or retained after delivery
If your conversation contains sensitive personal or business data and you are concerned about any server transmission, use Markdown or HTML instead - both preserve full formatting and run entirely locally.
What ChatCache does not access
- Your OpenAI account credentials - ChatCache never touches your login or password
- Other open browser tabs - the extension only reads the active chatgpt.com page
- Conversations you haven't opened - ChatCache only sees what is rendered on screen
- Your device files - ChatCache cannot read files outside the browser
ChatCache uses no analytics trackers and collects no usage data from your conversations.
Privacy first. Six formats export with zero data leaving your browser - your conversations stay on your device.
Add to Chrome, FreeThe threat model: who could see exported files
Privacy risk with exported files comes from two places: what happens during the export itself, and what happens to the file afterward.
During export:For local formats (Markdown, HTML, TXT, JSON, CSV, PNG), the conversation is processed inside your browser tab and written directly to your downloads folder. No network request is made. The only parties who could see the data during this step are you and your operating system. For PDF, the conversation is transmitted to ChatCache's rendering API over HTTPS. The file is returned and no data is retained. The exposure window is the duration of the HTTPS request.
After export: The file sits wherever you saved it - your downloads folder by default. If you share it via email, Slack, or a cloud drive, those platforms now have access to it. If you send a sensitive conversation to a colleague over unencrypted email as a PDF, the risk is the email transit, not the export format. Treat the exported file with the same caution you would apply to the conversation itself.
What Chrome permissions ChatCache requests and why
ChatCache requests host permission for chatgpt.com. This allows the extension to read the DOM of the ChatGPT page - specifically, the message bubbles rendered in the conversation - so it can extract the text and structure needed for export.
It does not request:
- Access to all websites (broad host permissions)
- Access to your browsing history
- Access to cookies or storage on other domains
- Access to your filesystem beyond writing the downloaded file
A narrow permission scope is a meaningful signal. Extensions that request access to all sites can read any page you visit. ChatCache's permissions are limited to the one site where it operates.
Recommendation for sensitive conversations
If a conversation contains personal data, confidential business information, credentials, or any content you would not want transmitted over a network even briefly, use Markdown, HTML, or TXT. All three are fully local, preserve conversation formatting, and produce files you can open and search in any text editor or browser. For EU users with GDPR obligations, local formats eliminate the data-transfer question entirely. For a deeper look at handling sensitive exports end-to-end, see the guide on exporting your ChatGPT history and data safely.
If you need a paginated document and the conversation is not highly sensitive, PDF is straightforward. ChatCache's PDF API does not log or retain conversation content after delivering the file.
OpenAI's own data handling
The privacy of the export tool is separate from ChatGPT's own data practices. ChatGPT may use your conversations for model training depending on your account settings and plan. ChatCache does not change ChatGPT's data handling - it only gives you a way to save a copy of conversations that have already been processed by OpenAI. For a direct comparison of OpenAI's export, browser print, and ChatCache across privacy, speed, and format support, see the dedicated comparison guide.
Frequently asked questions
Does ChatCache upload my conversations to a server?
For six of the seven export formats - Markdown, TXT, HTML, JSON, CSV, and PNG - the export runs entirely in your browser. No conversation data leaves your device. PDF export uses a server-side rendering step to produce the PDF file, but no data is stored after the file is returned.
Is it safe to export conversations that contain sensitive information?
For local formats (Markdown, TXT, HTML, JSON, CSV, PNG), yes - the data stays in your browser. For PDF, the conversation is sent to ChatCache's rendering API. If your conversation contains highly sensitive personal or business data, use a local format instead of PDF.
Does ChatCache have access to my OpenAI account?
No. ChatCache is a browser extension that reads the conversation visible on the chatgpt.com page. It does not connect to the OpenAI API, does not access your account credentials, and does not have any access to conversations you haven't opened.
What happens to conversation data after a PDF export?
The conversation data is sent to ChatCache's rendering API to generate the PDF, and the file is returned immediately. No conversation data is logged, stored, or retained after the PDF is delivered.
Does exporting a ChatGPT conversation violate OpenAI's terms of service?
OpenAI's terms permit personal use of conversation content. Exporting your own conversations for personal archiving, reference, or sharing is consistent with standard personal use. ChatCache does not modify ChatGPT's behavior or bypass any OpenAI security measures.
What Chrome permissions does ChatCache request and why?
ChatCache requests host permission for chatgpt.com so it can read the conversation rendered in that tab. It does not request access to all sites, your browsing history, or other tabs. The narrow permission scope is intentional - the extension only needs to see the ChatGPT page you have open.
Are there GDPR considerations for EU users exporting ChatGPT conversations?
For the six local export formats, no personal data leaves your device, so no data transfer or processor relationship is created by the export itself. PDF export sends conversation content to ChatCache's rendering API; if the conversation contains personal data of EU residents, this constitutes a transfer to a data processor. ChatCache retains no data after delivery. For regulated or professional use cases involving personal data, use a local format to keep all processing within your own device.