Privacy Notice.
1. What this notice covers
This notice explains how TokenSpend AI, meaning the desktop application, the VS Code extension and the website at tokenspendai.com, handles information. It goes with the Terms of Use and Software License.
In short: the application runs on your computer and does not send your usage data to the Provider. The website has no cookies, no analytics and no forms. Optional features that contact other services are listed in section 5.
2. The application and the extension
TokenSpend AI runs on your computer. It has no account, no telemetry and no TokenSpend AI server. The Provider does not receive your usage data, and the application does not send it to the Provider.
3. What it reads on your computer
- Usage logs written by the AI coding tools you use: GitHub Copilot (VS Code debug logs, Agent Host usage files and Copilot CLI session logs), Claude Code, Codex, Qwen Code and Continue.
- Git information for projects you work in: the remote URL, and your own commits' hashes, times and subjects.
- Folder names, to find your projects: the parent folders of known projects, common code folders under your home folder, and any folders you add in the settings. Only names and whether a folder contains a .git folder are read. Network paths are never opened.
Some of these logs contain your prompts and replies. TokenSpend AI reads them on your computer, keeps only the usage fields, and never stores prompt text, replies, file contents or tool output.
4. What it stores
TokenSpend AI keeps the following in a folder named .tokenscope in your home folder, or in the folder you choose:
- For each request: time, project, model, token counts, duration and status. For Copilot CLI calls it also keeps GitHub's per-call charge in nano AI credits, a number and nothing else.
- Your settings, price tables, task entries and GitHub billing totals.
- A random key file that the dashboard and the extension use to talk to the local collector. It never leaves your computer.
In the VS Code extension only, the version and time at which you accepted the Terms of Use are kept in VS Code's own extension storage on your computer. They are never sent anywhere.
Local storage is not a guarantee against access by other software, device administrators, malware, or anyone with access to your device.
5. What it sends, and only when you turn it on
- GitHub billing: if you connect it, the application sends your fine-grained GitHub token to api.github.com to read your billing usage. Your usage data is not sent.
- Price refresh: the application fetches public price tables from GitHub Docs and AI vendors' pages with plain requests that contain no usage data. Like any web request, they disclose ordinary connection information, such as your IP address and request headers, to the site you contact.
- Updates: only builds installed from a downloaded file check GitHub releases for new versions. The Marketplace build has no updater.
GitHub and the other services have their own terms and privacy practices.
6. The dashboard on your computer
The dashboard server listens on your computer's loopback address (127.0.0.1) only. It rejects requests from other addresses and sites, and every request except a health check needs the key stored in your data folder, so other programs and web pages on your computer cannot read your usage or change your settings.
7. Credentials
The GitHub token you enter is kept in VS Code's secret storage when you use the extension. The standalone app keeps it in a file in your data folder with owner-only permissions, or reads it from an environment variable. Disconnecting GitHub billing deletes it. Use only the permissions a connection needs, and never send a token in a support message.
8. This website
The website is made of static pages hosted by Cloudflare. It sets no cookies, runs no analytics or advertising, has no forms or accounts, and loads no scripts, fonts or images from other sites. Your light or dark theme choice is saved in your browser's local storage on your device and is not sent anywhere.
Like any web host, Cloudflare processes technical request information, such as your IP address, browser type, the page requested and the time, to deliver and protect the site, and may keep logs under its own privacy policy. The Provider does not run analytics on the site.
9. When you email the Provider
If you write to the address above, the Provider uses what you send to reply and to keep a record of the conversation, and does not sell it or share it for other purposes. Your email provider and the Provider's email provider also handle the message. Please do not include tokens, logs or other sensitive information.
10. Your choices and removing your data
- To remove everything the application stores, uninstall the extension and delete the .tokenscope folder in your home folder.
- To remove GitHub access, run Disconnect GitHub Billing and revoke the token on GitHub.
- The Provider holds no copy of your usage data, so there is nothing for the Provider to delete. To have an email conversation removed, write to the address above.
- To the extent privacy law applies to information the Provider holds about you, such as email correspondence, you may ask to see, correct or delete it, or object to its use.
11. Changes to this notice
A new version will state its version number and effective date. Material changes to data practices will be disclosed before they take effect, with any consent that applicable law requires.
12. Questions and complaints
Write to the address above with questions or concerns. You may also complain to the data protection authority in your country. Nothing in this notice limits rights that applicable law gives you.