Claudit — Privacy Policy

01 — What the Extension Does

Claudit observes your Claude activity and counts it.

Claudit observes your activity on claude.ai in the browser and counts messages, characters, and estimated tokens per conversation. It displays the totals in the extension popup and a dashboard page.

02 — What Data Is Processed

Metadata about your turns, not the content of them.

Message metadata. For each completed turn on claude.ai, the extension reads the role (user or assistant), the text length in characters, the conversation identifier from the URL, the conversation title, and the active model name shown in the Claude UI. It does not read or store the message content itself.
Adapter state. A small record of whether each site adapter is enabled and when its DOM selectors last validated.
Settings. Your retention window, refresh interval, theme preference, daily goal, and whether you've opted into plan-usage polling.
Plan-usage snapshot (opt-in only). If you enable Plan usage tracking in Settings, the extension fetches percentage-of-plan numbers from claude.ai/api/organizations/<id>/usage using your existing Claude session cookies. This is off by default, and the extension does not request cookie access until you turn it on.

03 — Where the Data Is Stored

Only on your device. Only in chrome.storage.local.

Everything above is stored in chrome.storage.local, which is a per-device key-value store provided by Chrome and never synced across devices. No data ever leaves your device.

04 — What the Extension Does Not Do

The negative space is where the privacy lives.

No telemetry. No analytics, no error reporting, no product metrics.
No third-party tracking. No fonts from Google, no CDN scripts, no pixel beacons.
No server. The developer operates no servers that this extension talks to. There are no accounts, no sign-up, no API keys.
No background network requests of any kind unless you enable Plan usage tracking — in which case the only request is to claude.ai/api/organizations/<id>/usage once per minute while the extension is active.

05 — Permissions and Why They're Needed

Each permission has one narrow purpose.

storage — to write your event log and settings to local storage.
alarms — to run the nightly retention sweep that purges old events per your settings, and to refresh the icon badge on a timer.
host_permissions: *://claude.ai/* — required to inject the content script that observes DOM changes on claude.ai.
optional_permissions: cookies — requested only if you enable Plan usage tracking in Settings. Used to read the lastActiveOrg cookie so the extension can construct the correct usage-endpoint URL.

06 — Exporting and Deleting Your Data

You own the data. Take it, replace it, or wipe it.

The Settings page includes:

Export all data — downloads a JSON file of every event, setting, and adapter state currently stored. Useful for backup or migration.
Import JSON — restores from a previous export. Replaces existing local data.
Wipe all data — deletes every event, setting, and adapter state from local storage.

Uninstalling the extension through Chrome's extension manager also wipes all local storage for the extension.

07 — Children's Privacy

Not directed at children. Also: doesn't collect anything from anyone.

The extension does not knowingly collect any information about children under 13. It does not collect any information from anyone.

08 — Changes to This Policy

Policy changes ship with version changes.

If the extension's data handling ever changes, this policy will be updated in lockstep. The version number on the extension will bump and the updated policy will be shipped with the release.

09 — Contact

Questions? We'll respond.

Email hello@burnwire.ai with "Claudit Privacy" in the subject line. You can also open an issue on the extension's repository once it's public, or email the developer listed on the Chrome Web Store listing.