Mr. Usage privacy and optional leaderboard sharing

Local tracking and provider requests

Mr. Usage reads supported local AI-tool records to count tokens and uses existing provider credentials to request account limits and supported account history. Local tracking does not require joining the community leaderboard. Reusing an existing login does not mean usage collection is entirely offline: live account information requires requests to the provider.

The app accesses Claude Code credentials through macOS Keychain and supported Codex or OpenCode credentials from their local stores. Provider tokens are not refreshed by Mr. Usage; the original tools manage their logins. The app is open source so its readers, polling behavior and sharing implementation can be inspected.

Leaderboard sharing is off by default

To participate, open the app’s Settings, choose a display name and enable Share on leaderboard. The first sync shares the most recent 30 UTC days. Subsequent snapshots replace existing totals rather than adding another copy. Sharing runs periodically after opt-in, including while the menu bar panel is closed.

The current app shares supported Claude and OpenAI usage together. OpenAI account days replace overlapping local activity; local logs supply unreported days. Website estimates may use different versioned prices from the native app. Display names and submitted usage summaries become public, and share links expose those results to anyone with the link.

What is uploaded, and what is not

Uploads contain your chosen display name and daily aggregated rows: UTC date, provider, model identifier, billing category, disjoint token counts and an account-estimate flag. Requests also carry a dedicated leaderboard credential, data-format version and sharing consent. As with other web services, the server can see the connecting IP address.

Provider API keys and OAuth credentials are not uploaded to the leaderboard. Neither are prompts, conversations, source code, project paths, session identifiers, plan limits, credit balances or payment details. The dedicated leaderboard token is separate from provider credentials.

The website can include synthetic profiles with internally recorded provenance. Rankings and participant counts should not be interpreted as verified real-user adoption, invoices or productivity. The explicitly labeled demo board is a separate frontend preview.

Website analytics are separate from app sharing

This website uses PostHog US Cloud for page and interaction analytics. Requests pass through a same-origin proxy before reaching PostHog. Analytics can include visited URLs, clicked elements, browser or device information and the connecting IP address. These website events are separate from the native app’s optional usage uploads.

The website respects Do Not Track and Global Privacy Control signals, and preserves PostHog’s saved opt-out setting. Session recording follows the project’s PostHog settings; when enabled, recordings can include page interactions. Local development previews do not send analytics. The proxy does not forward site cookies or Authorization headers to PostHog. A proxy improves delivery reliability; it does not make analytics anonymous or eliminate applicable consent requirements.

Remove your public profile

Turn sharing off in the app to request deletion of your public profile and its submitted usage. Pending uploads finish before removal. Offline removal requests are retained and retried after reconnection or restart. Sharing again requires opting in again.

After deletion, the live website should no longer return that profile. Other people can still retain screenshots or exported share images made while the profile was public; deleting server data cannot recall copies already saved elsewhere. Contact the project through the website footer if you need help with a removal.