Claude Downloader Home

Privacy Policy

Last updated: July 22, 2026

Claude Downloader does not collect, transmit, or sell any personal data, and it does not operate any server of its own. Everything the extension does happens inside your browser.

What the extension accesses

The extension reads your conversations, projects, and project files from claude.ai using your existing browser session (cookies), only when you take an action that requires it — opening the popup, clicking an export button, or opening the browse page.

Where that data goes

Into a file on your computer, and nowhere else. The only host the extension makes network requests to is https://claude.ai — every conversation, project, and file fetch goes there and only there. There is no analytics, no telemetry, and no remote server operated by this project.

What is stored locally, and why

The extension uses Chrome's built-in chrome.storage API to remember things between visits, so it doesn't have to re-fetch or re-ask on every use:

• Your organization ID (chrome.storage.sync) — a UUID identifying your Claude workspace, saved from the Options page or auto-detected, so exports know which API endpoint to call.
• Export timestamps and cached model snapshots (chrome.storage.local) — per conversation, so the browse view can show when a conversation was last exported and which model actually generated it, even if Claude has since changed the conversation's reported model.
• Display preferences (chrome.storage.local) — your chosen date format, time format, and which model name (original vs. current) to display.
• A local error log (chrome.storage.local) — the last 50 unhandled errors observed on the page, kept only to help diagnose bugs. This includes errors thrown by the extension's own code, but because the listener is attached to the page itself (so it can catch errors from the extension's content script), it may also capture uncaught errors thrown by claude.ai's own page scripts, unrelated to the extension. Any UUID-shaped text (conversation, project, or organization IDs) is stripped out and replaced with <id> before an entry is written — this is the only redaction applied; error messages and stack traces are otherwise stored as reported. This log stays on your device unless you explicitly generate and share a diagnostics file (see below).

Separately, the extension also uses the browser's own localStorage API — a different mechanism from chrome.storage — to remember one thing: your theme preference. A single key, theme, holds the string dark or light, and is read and written by the browse page and popup so they open in whichever theme you last chose.

Everything above, through either mechanism, stays on your device. Because chrome.storage.sync is a Chrome platform feature, your organization ID may sync to your other Chrome browsers if you have Chrome Sync turned on in your Google account — that sync channel belongs to Google, not to this project; the extension itself never transmits it anywhere. The localStorage theme key does not go through Chrome Sync at all — it stays on this browser profile only and is never transmitted anywhere either.

Features that create a file, only when you ask for one

• Export — writes a Markdown, text, JSON, or ZIP file of the conversation(s) or project you requested, to your Downloads folder.
• Backup / restore (Options page) — writes or reads a JSON file containing everything listed above, so you can move your settings to another browser or restore them after reinstalling. This file is created locally and only touched by you.
• Diagnostics (Options page) — writes a JSON file containing the sanitized error log, your preferences, and basic environment info (browser user agent, platform, language). No conversation content and no unredacted IDs are included. Nothing is sent automatically; the file is only attached if you choose to attach it to an issue you file yourself.

Permissions

• activeTab, tabs — to find the claude.ai tab you're viewing so the extension knows what to export.
• scripting — to run the extension's export code in that tab, using your existing claude.ai session (a background request without the page's session would not be authenticated).
• storage — to remember the settings described above.
• Host access to https://claude.ai/* — the only site the extension talks to.

Contact

Email support@claudedownloader.com, or see the support page.