ChatVault — Privacy Policy

ChatVault — Privacy Policy

Otto Tools

Last updated: 2 August 2026

The short version

ChatVault reads the conversations you ask it to export — and, on ChatGPT, the session token the site uses to authenticate you. Chrome classifies that as handling personal communications, authentication information and website content, and we disclose it rather than pretend otherwise.

None of it is transmitted to us. There is no ChatVault server. The only hosts contacted are claude.ai and chatgpt.com, which your browser already talks to, and the export is written straight to your own disk.

What the extension does with your data

When you click Export, ChatVault reads the conversation you are viewing on claude.ai or chatgpt.com using the session you are already signed in to, converts it to the format you chose, and passes the resulting file to Chrome's built-in downloader.

That conversion happens entirely inside your browser. The conversation content exists in the page's memory for the duration of the export and is then written to your own disk. It is never sent anywhere else.

Data we handle

Three categories, all processed locally and none transmitted to the developer:

· Category · Why · Where it goes · · Personal communications · Your chat messages are the thing being exported · Converted in the browser, written to your disk · · Authentication information · ChatGPT's own endpoint requires the session token the site already holds; it is read from your logged-in session and sent only back to chatgpt.com over HTTPS · Never stored, never sent anywhere else, discarded when the page closes · · Website content · Conversation titles, timestamps and attachments' extracted text · Same as above ·

We disclose these because Chrome Web Store policy requires disclosing how an extension handles user data even when that data never leaves your device.

There is still:

- No analytics, telemetry, crash reporting or usage statistics. - No accounts, sign-ups, licence keys or activation. - No advertising or tracking identifiers. - No transmission of conversation content to the developer or any third party.

Data stored on your device

ChatVault stores exactly three preferences using Chrome's local storage API:

· Key · Value · · format · The export format you last selected (md, html, json or txt) · · thinking · Whether the "include reasoning" checkbox is ticked · · tools · Whether the "include tool calls" checkbox is ticked ·

These stay on your computer, are never transmitted, and are removed when you uninstall the extension.

Network activity

ChatVault makes network requests to two origins only:

- https://claude.ai — to read your own Claude conversations - https://chatgpt.com — to read your own ChatGPT conversations

These are the same endpoints the websites themselves use, called with your existing browser session. The extension makes no requests to any other domain. It contains no third-party libraries, no remote code, no external fonts, and no external images.

Permissions

· Permission · Why it is needed · · activeTab · Temporary access to the tab you clicked on, for that interaction only. ChatVault requests no standing access to any site. · · scripting · To run the export routine in that tab after your click. Nothing is registered to run in the background. · · downloads · To save the exported file to your Downloads folder. · · storage · To remember the three preferences listed above. ·

Third parties

There are none. No data is shared with, sold to, or processed by any third party, because no data ever leaves your device.

Children

ChatVault is a general-purpose utility and is not directed at children.

Changes

If this policy ever changes, the updated version will be published at this URL with a new "last updated" date. Since the extension collects nothing, any change would be a clarification rather than a new use of data.

Contact

Questions about this policy can be raised as an issue on the project's public repository.

Report Page