Your data stays on your machine.
TokenCore has no account and no analytics. It reads what it needs on your computer, talks only to the services you connect, and keeps its history locally.
Last updated September 29, 2026
The short version
- No TokenCore account, no tracking, no analytics, and no automatic crash reports.
- A provider's sign-in is read only after you allow it, one provider at a time.
- That sign-in is only ever sent to the company that issued it.
- Quota snapshots and spend history are stored on your computer and nowhere else.
- Payments are handled by Lemon Squeezy; we never see your card.
What the app reads on your computer
System telemetry. CPU, GPU, memory, disk and network use, and the list of running processes with their resource use. This is read from the operating system and shown to you; none of it leaves your computer.
AI tool sign-ins and logs. To show a provider's quota, TokenCore reads the sign-in that provider's own tool already saved (for example Claude Code, the Codex CLI, Cursor, the GitHub CLI or the Grok CLI). To estimate spend, it reads those tools' local usage logs. Before it reads anything for a provider, it asks you, and it shows exactly which file or credential store it will read and which company it will contact.
Sign-in renewal. Off by default. If you turn it on for Claude Code, Codex or the Grok CLI, TokenCore renews an expired sign-in with that company and writes the new one back to the tool's own file, keeping a backup until the write is verified.
Wi-Fi network name. In the Mac app, showing the network name will need Location permission. TokenCore will ask only if you open the Wi-Fi details.
What the app stores
Credentials stay where the tools keep them, or in your system's Keychain or Credential Manager. TokenCore's own database holds quota snapshots, spend history for 90 days, and your settings. On Windows it lives in %LOCALAPPDATA%\TokenCore. Crash details, if any, are written to a log file in the same folder and stay there.
Disconnecting a provider in Settings forgets its consent, its cached snapshot and its saved spend. Uninstalling TokenCore and deleting that folder removes everything the app stored.
Where the app connects
- Each provider you connect, at that company's own addresses, using your sign-in, to fetch your usage.
- Price catalogs: LiteLLM's price list on
raw.githubusercontent.comandmodels.dev, to price models released after your version of TokenCore. TokenCore fetches them at most once a day, and only after you connect a provider with spend. These requests carry no information about you. - Lemon Squeezy, when you activate or check your license: your license key and a name for this computer, so the license can be verified.
Nothing else. There is no telemetry endpoint to turn off, because there isn't one. On Windows, updates come through the Microsoft Store, so TokenCore doesn't check for them itself.
Buying TokenCore
Lemon Squeezy sells TokenCore as the merchant of record. It handles your payment details, billing address and tax under its own privacy policy. We receive the order details we need to support you and your license, such as your name, email address, country and what you bought. We use them only for that, and for telling you about your license or a serious problem with the app.
This website
tokencore.app has no analytics, no advertising and no cookies. Its fonts are served from the site itself, so visiting it doesn't contact Google. It is served by Cloudflare, which processes standard request data, such as IP addresses and requested pages, to deliver and protect the site.
Changes and contact
If this policy changes, the new version will be posted here with a new date. Questions or requests about your data: hello@tokencore.app.