Continuity for Claude.ai

Effective 2026-09-17 Version 0.1.0 Not affiliated with Anthropic

In plain terms

Everything this extension stores lives in your own browser's local storage — nothing is sent to a server we operate, because we don't operate one.
The only network request it makes on its own is a direct, same-origin call to Claude.ai's own usage endpoint, using your existing logged-in session.
Conversation text is read only from the claude.ai tab you're on, only to build an export, a fork, or a continuity brief you asked for — and only when you click a button.
Clipboard writes and file downloads happen only when you click the specific button that does them.

§1

What this extension is

Continuity is a browser extension that adds usage tracking, conversation export, conversation forking, a prompt library, and a cross-AI continuity panel to claude.ai. It is built and maintained independently and has no relationship with Anthropic, PBC beyond running inside a browser tab pointed at their product.

§2

Data we store, and where

All extension data — your saved prompts, export/fork history metadata, and feature settings — is written to chrome.storage.local, a storage area Chrome keeps on your own device, scoped to this extension. It is never transmitted anywhere by us, because the extension has no backend server of any kind.

What's kept, specifically

Saved prompt text you add yourself; lightweight metadata about past exports and forks (title, format, timestamp — not the full conversation text); your feature on/off toggles; and the last usage percentage the extension observed. Full conversation content is read at the moment you use export, fork, or continuity, and handed directly to your download or clipboard — it is not retained afterward.

§3

The one network request we make

To show your Claude usage percentage, the extension calls /api/organizations/{orgId}/usage — an endpoint that belongs to Claude.ai itself, not to us. Because the request is same-origin, your browser attaches your existing claude.ai session cookies automatically; the extension never sees, stores, or handles any password, token, or credential. This is the only outbound request the extension initiates on its own, and its response (a usage percentage and reset time) is used only to render the on-page badge.

§4

Permissions, and why each is needed

As declared in the extension's manifest
Permission	Why it's requested
`storage`	Save your prompts, settings, and history metadata locally, as described in §2.
`downloads`	Save an export or continuity brief as a file on your device when you click Download.
`host_permissions`: claude.ai	Read the visible conversation and composer on claude.ai to power export, forking, the prompt library, and the token counter — and to make the same-origin usage request in §3.

§5

What we don't do

We don't run analytics, telemetry, or crash reporting of any kind.
We don't sell, rent, or share your data — there is no data on any server of ours to share.
We don't read or act on any page other than claude.ai.
We don't auto-send anything to ChatGPT, Gemini, or any other destination — continuity briefs are copied to your clipboard and a blank tab is opened for you to paste into yourself.
We don't inject ads or modify the content Claude.ai serves you, beyond adding our own UI elements.

§6

Changes to this policy

If what the extension collects or requests changes in a future version, this page will be updated and the version number above will change accordingly.