Privacy

The claudeusage-sync CLI reads your local Claude Code logs in ~/.claude/projects/, sums them locally, and uploads usage totals and the metadata needed to merge them:

• API-equivalent cost in USD
• active hours and session counts
• input, output, and cache token totals
• per-model usage mix
• daily activity for your contribution grid and hourly aggregates for your own dashboard
• model identifiers, CLI version, and a hashed machine identifier

The CLI is open source (MIT), so you can read every line of what it sends: claudeusage-sync.

• prompts and responses
• your code and file contents
• raw Claude Code JSONL files
• project names as separate upload fields
• individual message and request IDs (only counts are sent)

Model identifiers can contain paths when a local provider reports them that way. CLI 0.4.2 adds sanitization before upload; public views replace path-shaped identifiers with local-model. Older uploads may still contain them in private aggregate history. To merge usage across your devices, the CLI uploads a one-way hash of your machine name (SHA-256 of hostname + OS username). Your raw hostname and username never leave your machine.

Every public response is filtered through a server-side allow-list, so these are never visible on a profile or the leaderboard:

• your email address and sign-in provider
• machine identifiers and hashes
• sync tokens
• exact timestamps — public profiles are day-level only

We store a coarse, nation-level country code (for example, us) derived once at sign-up from your connection’s region. We never store your IP address and never derive a precise location. If your region is unknown, your country is simply left blank.

You sign in with Google or GitHub. Your email and provider stay private. You can choose a public display name or stay anonymous (shown as anonymous-…), and you can switch between the two at any time.

Members can add social and profile links — for example GitHub, X, LinkedIn, YouTube, Twitch, Instagram, or a personal website — to their public profile. Adding links is entirely optional: you choose which, if any, to add. Because your profile is public, any link you add is displayed publicly and is visible to anyone who views your profile. Only https links are accepted, and you can edit or remove them at any time from your dashboard.

Paid founder plans are processed by Stripe. claudeusage stores only the Stripe customer/subscription identifiers needed to keep your subscription status in sync, plus public-safe founder badge status after a paid period starts. We do not store card numbers or payment methods.

claudeusage uses Google Analytics to understand aggregate site traffic — which pages are visited and how visitors find the site. Google Analytics sets its own cookies and receives standard request data such as IP address and browser details; we do not send it your account data, and we do not sell your data. We do not run ad networks or cross-site tracking pixels. Beyond analytics, the site uses only essential first-party cookies — mainly a sign-in session cookie so you stay logged in.

The outside services that process data on our behalf are limited to the ones that make the product work: Firebase Authentication verifies your Google or GitHub identity, Firestore stores your aggregate usage numbers and profile, Stripe processes payments for founder plans, and Google Analytics and Cloudflare Web Analytics measure site traffic. Stripe handles card details directly and may set its own cookies on payment pages to process the payment and prevent fraud; as noted above, no card data is stored on our servers.

We use Cloudflare Web Analytics to measure page views, visits, and page performance. Its beacon does not use analytics cookies or local storage to identify visitors. Aggregate visits and page views may be displayed publicly with their measurement period. A visit is not a unique person, and blockers can reduce measured traffic.

Cloudflare processes browser request and performance information for this service. See Cloudflare Web Analytics for its collection policy. We do not send Claude prompts, account credentials, or uploaded usage payloads to this beacon.

You can delete your account from the dashboard. Deletion removes your public profile and revokes all sync tokens. Aggregated, fully anonymized counts that cannot be tied back to you may be retained.

claudeusage is an independent project and is not affiliated with, endorsed by, or sponsored by Anthropic. “Claude” is used descriptively to refer to Anthropic’s Claude models.