Blog › Privacy & Architecture

How ChatShell handles conversation data

ChatShell converts the conversation you select into a file in your browser. The conversation content is not uploaded to ChatShell servers.

Where the file is created

ChatShell reads the selected ChatGPT conversation and generates the export in the browser. You then save the resulting file. This describes the export process; it does not change how ChatGPT stores the original conversation.

Why network requests can still appear

The extension may fetch conversations and images from ChatGPT and download fonts for PDF output. Paid-license checks send the license key and device identifier to the licensing service and Creem. Those checks are separate from the conversation content.

Local file generation therefore does not mean every feature works without a connection. A font download or license check is also not, by itself, evidence that a conversation was uploaded.

What happens after saving

The exported file can contain the same personal or confidential information as the chat. Saving it in a synced folder, emailing it, or uploading it to another app puts it under that service’s storage and access settings. Check the destination before sharing.

How to inspect an export

If you want to examine the network activity, use the browser’s developer tools while exporting a short test conversation. Inspect the destination and payload of requests, rather than judging only by their number or whether they use POST. A single test describes that run; it does not prove the behavior of every feature or future version.

More from the ChatShell blog

Try ChatShell

Export ChatGPT conversations to PDF, Markdown, DOCX, or JSON — locally, in the browser, without uploading your data.