Local files contain more than the upload

Claude Code session files can contain conversation content. The sync CLI reads usage fields from those records and creates date-and-model aggregates. Reading a file locally is different from uploading the whole file.

The upload includes numeric token counts, message and session counts, estimated active time, model names, and sync metadata. It does not include prompts, responses, source code, or project names as separate fields. CLI version 0.4.2 adds sanitization for path-shaped model identifiers before upload. The website also replaces them with local-model in public views.

Private sync metadata

The server needs a machine identifier, a sync window, and credentials to associate an upload with your account and avoid replaying an accepted batch. This metadata is private. It is not part of the public leaderboard.

A browser sign-in session and a CLI sync token are separate credentials. Signing out of the website does not unlink the CLI. Revoke a token in settings when it should stop uploading.

Public profile information

Your chosen username, public display name, optional country, and public usage totals can appear on the leaderboard. A linked profile can show aggregate analytics to viewers with access. Optional social links are public by design.

If you prefer not to publish your name, choose the anonymous identity option. Anonymity does not make the usage totals private. Avoid a display name or social link that identifies you if that matters to you.

Inspect before trusting

Read the parser and payload builder in the public CLI repository. Run a dry run and inspect the fields. Compare those fields with the privacy page rather than relying on a badge or a slogan.

Website traffic analytics are separate from uploaded Claude usage. Public visitor statistics are aggregate measurements with a named source and date range. They do not expose individual browsing histories or identify which visitor belongs to a Claude profile.

npx claudeusage-sync --dry-run