Privacy Policy

Claude Usage Companion

Effective: October 13, 2026  ·  Applies to: the browser extension and its optional local daemon  ·  Version: extension 0.3.2, daemon 0.3.2

In short: nothing you do in this extension leaves your computer. There is no account, no server, no analytics, and no copy of your conversations anywhere but your own machine's browser storage.

Everything below explains exactly what the extension reads, where it's kept, and why each browser permission exists — in enough detail that you don't have to take the summary on faith.

01 What this extension is

Claude Usage Companion reads your Claude usage limits — the same session and weekly numbers claude.ai already shows you on its own Settings → Usage page — and displays them as bars, history, and a burn-rate forecast without you needing to visit that page. An optional local companion program (the "daemon") can additionally show usage from the Claude Code command-line tool, if you choose to install it.

This is an independent, unofficial project. It is not made by, affiliated with, or endorsed by Anthropic.

02 What the extension reads

The extension's page scripts only run on claude.ai pages. While you're there, it picks a few things out of the page's own network traffic — it never touches Claude Code's local files itself. Separately, every few minutes its background worker asks claude.ai for the same usage numbers directly, using your existing signed-in session, so the bars stay current even when no claude.ai tab is open:

Usage snapshots
Your account's session/weekly limit percentages and reset times, from the same endpoint claude.ai's own Settings page calls.
Live limit updates
The same numbers, refreshed in real time while you're actively chatting, between the periodic checks.
Claude Code on the web limit events
On claude.ai/code, only the rate-limit entries from a session's event stream. Every other entry in that stream can carry conversation content, so it is filtered out inside the page itself, before anything reaches the extension.
Usage credits
The figures claude.ai's own "Usage credits" panel shows: this month's pay-as-you-go spend against your limit.

It looks only for usage-limit information in those responses. Anything else they contain, including message content, is discarded inside the page and is never stored, logged, or transmitted. It does not read your conversation history, and it does not modify anything claude.ai sends to or receives from your browser.

03 The optional local daemon

If you separately install the daemon (a manual, opt-in step — it never installs itself), it reads Claude Code's session logs directly from your own disk (~/.claude/projects/**/*.jsonl) to show CLI token usage (including, for a session you expand, which subagents ran inside it and their own token totals), and to let you search and export your own past sessions. This reading is read-only — nothing about any of your projects is ever changed.

This program:

  • Runs only on your machine, listening only on 127.0.0.1 — never reachable from the internet or any other device.
  • Makes no network request of its own, with no exceptions.
  • Writes only to its own local config directory (an access token and a one-time pairing marker) — never to any project directory.
  • Requires a randomly generated access token before the extension can talk to it at all.

You can remove it at any time; instructions are in the project's README.

04 What is never collected

  • No account or sign-up of any kind — there is nothing to register for.
  • No analytics, telemetry, or crash reporting of any kind.
  • No conversation content, prompts, or Claude responses are ever logged, transmitted, or stored by this project — only usage numbers, counts, and timestamps.
  • No data is sent to any server this project controls, because no such server exists.
  • No data is sold, shared, or shown to any third party, because it never leaves your device in the first place.

05 Where data lives, and for how long

Usage history is stored in your browser's own local storage (IndexedDB), scoped to the extension the same way any browser stores site data — it is private to your browser profile on your device and is never synced anywhere by this project.

Default retention
90 days of usage history, configurable in the extension's settings (minimum 1 day).
To delete everything
Uninstall the extension, or clear its site data from your browser's settings — both remove all stored history immediately.

For debugging, the extension also keeps your 50 most recent raw usage responses from claude.ai (numbers and timestamps only, no conversation content), which you can export from a collapsed section of the options page. They are never sent anywhere.

You can back up this locally-stored history to a file at any time (Settings → Download backup), and restore it later (Settings → Restore from file). Both are ordinary browser file downloads/uploads you trigger yourself — the file only ever goes where you choose to save or open it, never anywhere this project controls. A restore only ever adds history you don't already have; it never overwrites the local daemon connection this browser is already paired with.

06 Every permission, explained

The extension requests the smallest set of browser permissions that its features actually need. Here is what each one is for, with nothing left unexplained:

PermissionWhat it's for
host: claude.aiRead usage data from claude.ai's own responses while you're on the site — the entire basis of the extension.
host: 127.0.0.1Talk to the optional local daemon on your own machine, if you've installed it — for usage/CLI/subagent data, described above. Nothing outside your device.
alarmsSchedule the periodic usage check (every few minutes) and the pairing check for the local daemon.
notificationsShow a local system notification when a usage bar crosses a threshold you've configured — defaults to 80%/95%, adjustable in Settings, or can be turned off entirely by clearing the thresholds there. One other optional notification, generated on your device from data already stored locally: a warning, off by default, that you are on pace to run out before a limit resets.

07 Security

The local daemon binds only to 127.0.0.1, requires a bearer token on every request (apart from a bare health check and the one-time pairing handshake that hands the extension its token), and rejects any request coming from a regular web page — so a malicious website cannot reach it. Every piece of data the extension receives, from claude.ai or from the daemon, is validated against a schema before it's trusted; anything unexpected is discarded rather than acted on. The daemon itself writes only to its own local config directory — never to any project directory.

08 Children's privacy

This extension is a utility for people who already use Claude and is not directed at, or knowingly used to collect information from, children. Since the project collects no personal information from anyone, there is no children's data to describe.

09 Changes to this policy

If this policy changes, the "Effective" date at the top of this page will change with it, and the current version will always be the one published at this URL and mirrored in the project's repository. There is no mailing list or account to notify, since none exists.

10 Contact

This is an open-source project. The full source, including everything this policy describes, is public — read it yourself or open an issue at github.com/RehberOdhano/headroom.