PRIVACY · 2026-09-11

What the widget reads, and what it never does.

AI Limits is a desktop widget that shows how much of your AI subscription windows you have used. It runs entirely on your computer. There is no account to create, no server of ours in the middle, and nothing it learns about you ever leaves your machine except the requests described below, which go to the providers themselves.

What it reads

To show a limit, the widget needs to ask the provider the same way its own command-line tool does. So it reads the login those tools already keep on your machine, read-only:

• Claude — the Claude Code login in %USERPROFILE%\.claude\.credentials.json, and, if present, Claude Code's status-line snapshot file.
• OpenAI Codex — the Codex CLI login in %USERPROFILE%\.codex\auth.json.
• GitHub Copilot — the token the gh CLI prints for gh auth token.
• Google Antigravity — the Antigravity session in Windows Credential Manager, or the legacy Gemini CLI login in ~/.gemini/oauth_creds.json.

The widget never writes to those files, never refreshes or rotates a token, and never signs you in or out of anything. If a login is missing or expired, the row for that provider goes grey; nothing else happens.

Where it sends

Each token is sent only to the endpoint of the provider that issued it, over HTTPS, to fetch your usage: api.anthropic.com, chatgpt.com, api.github.com and daily-cloudcode-pa.googleapis.com. One request per enabled provider per update cycle, no more often than once a minute, and none at all while the computer is idle or locked. A provider you disable in the menu is never contacted.

The installer build also asks api.github.com whether a newer release exists, and downloads it only after checking the digest GitHub publishes for it. The Microsoft Store build does not do this; the Store updates it. That request carries the standard user agent ailimits/<version> and nothing about you.

There is no telemetry, no analytics, no crash reporting and no advertising. Nothing is sent to us, because there is no us to send it to: the project has no server.

What it stores

• Settings — in %APPDATA%\AiLimits\config.toml: layout, palette, which providers are on. It holds labels, never secrets.
• Optional keys and tokens you add yourself — an API key or a pasted usage token goes into Windows Credential Manager under the service ailimits, never into a file.
• The last readings — in provider-cache.json beside the settings, so the widget can show them, marked with their age, while a provider is unreachable.
• A log — only if you set AILIMITS_LOG yourself. Tokens are never written to it.

Removing it

The installer's uninstaller removes the settings, the cache and every Credential Manager entry the widget created. The Microsoft Store cannot run a step of ours at uninstall, so after removing the Store version any keys or tokens you added by hand stay in Credential Manager under ailimits until you delete them there. The CLI logins the widget only read are not ours and are never touched either way.

Who this is from

AI Limits is free software under the GPL-3.0, written and maintained by one person. The code that does everything described here is public at github.com/napxlexn/ailimits; the file docs/en/PROVIDERS.md lists each provider's exact source and endpoint. Questions go to the issue tracker. If this page ever changes, the date at the top changes with it.