Update Check & Privacy

TokenAnalytics sends no usage telemetry. The only optional outbound call is the GitHub update check — here's exactly what it does and how to turn it off.

TokenAnalytics is 100% local by design. Your agent logs, session transcripts, token counts, and costs never leave your machine. Two narrow outbound features exist and can be disabled independently.

Update check

About once an hour, the dashboard fetches the latest version number and curated release notes from GitHub. This lets you see an in-app banner when a new version is available.

What is sent: A single HTTPS GET to GitHub containing no usage data — just a version request. Like any web request, it exposes your IP address and a TokenAnalytics User-Agent to GitHub.

What is not sent: Your sessions, tokens, costs, project names, file paths, or any other usage data.

Disabling the update check

In the app: Settings → Updates & privacy → toggle off Check for updates.

Via environment variable: Set TT_NO_UPDATE_CHECK=1 before launching TokenAnalytics. The env var takes precedence over the in-app toggle, so you can enforce it for all users on a machine (e.g. in air-gapped or egress-monitored environments):

TT_NO_UPDATE_CHECK=1 tokentelemetry

Or add it to your shell profile:

export TT_NO_UPDATE_CHECK=1

No product telemetry

This build of TokenAnalytics sends no usage telemetry at all — the feature was removed from the code. Nothing about your sessions, the pages you open, or the features you use is ever transmitted. The update check above is the only outbound network call the app makes.

You may still see a Share anonymous usage data switch in Settings, and the TT_NO_TELEMETRY=1 / DO_NOT_TRACK=1 environment variables are still recognised — but they are vestigial no-ops. There is nothing to opt out of, because nothing is sent.

Summary

The update-check preference is stored in ~/.tokenanalytics/preferences.json.