> Privacy
Last updated 7 November 2026
TokenTrust shows how many AI tokens developers use. This page says what we keep to do that.
What we store
- Your sign-in account. When you sign in with GitHub or X we keep the account's id, username, display name and profile picture. Sign-in runs through Supabase Auth, which also holds the email address GitHub or X shares with us. We use it only to sign you in and to recognise the same person across GitHub and X.
- Token usage. The tokentrust CLI uploads, per model response: the agent (Claude Code or Codex), the model, the time, the token counts, and the provider's response ids. Session ids and git remotes are hashed on your computer first. Your prompts, code, file names and outputs are never uploaded.
- Connected computers. A label for each computer you link, and a one-way hash of its token.
- API keys you add. Anthropic keys are encrypted at rest and used only to read your usage reports. We show the last few characters so you can tell keys apart.
What is public
Your handle, display name, profile picture, linked GitHub and X profiles (you can hide GitHub in settings), and your token usage: totals, daily and monthly figures, and models used. Everything else stays private.
Who we share it with
Nobody, apart from the services that run the site: Supabase for sign-in, our database and hosting providers, and unavatar.io, which we ask once for the picture of an X username you type in. We don't sell data or show ads.
Deleting your data
Delete your account from settings. That removes your profile, usage, connected computers and API keys, and your Supabase sign-in account. You can also disconnect a single computer or API key there.