Privacy by Construction: Zero Prompt Text or Code Retention
Last updated: September 18, 2026. Usage Radar is designed for software engineers, AI researchers, and teams who require total privacy while monitoring AI coding tool spend.
1. Prompts & Code Are Purged In-Memory
When you import local CLI session logs from Claude Code, OpenAI Codex, or Gemini CLI, our client-side parser immediately strips prompt text, completions, file paths, and git diffs before extracting token metadata.
2. No API Key Collection
Usage Radar does not request, store, or transmit your Anthropic, OpenAI, or Google Cloud API secret keys. Costs are calculated purely by analyzing local CLI log files against versioned rate catalogs.
3. Local-First Storage
By default, your historical usage metrics stay on your device — in your browser's local storage, and in the local connector's own files. We do not transmit telemetry to any ad trackers or third-party data brokers.
4. Total Data Deletion & Export
You can export your normalized AI spend records as JSON/CSV or wipe all local data at any time with a single click from the Data Controls settings page.
Optional website analytics
Google Analytics 4 is off until you choose Allow analytics. Before permission, we do not load Google's analytics tag, create analytics cookies, queue analytics events, or send analytics requests. Your browser's Do Not Track or Global Privacy Control signal keeps analytics off.
With permission, Google receives visits to a fixed list of product pages, basic device and browser information, the referring site's origin, and selected actions such as opening the sample or starting connector setup. Query strings, fragments, account pages and dynamic private URLs are excluded. We never send prompts, source code, repository names, provider keys, token counts, spend figures or account identifiers. Google Analytics uses first-party cookies to distinguish visits. Google signals and advertising personalization are disabled.
Use Privacy choices at the bottom of any page to withdraw permission. This removes this site's Google Analytics cookies and reloads the page to stop its runtime. Withdrawal stops future collection; it does not delete reports already collected. Your preference is saved in this browser and does not change your local AI usage records or optional workspace sync.
Google processes this data under its privacy policy. Contact abhijaypl@gmail.com for a privacy request.
Opt-in Cloud Sync
If you explicitly pair a machine to a workspace, only aggregate counters leave it — token totals per day, per model, per agent. Prompts, responses, file paths and raw session identifiers are never included. To be precise about what that protection is and is not: those counters travel over TLS and are encrypted at rest on the server, which holds the key. This is not end-to-end encryption, and we do not claim it is — an operator with database access could read your aggregate totals. Sync is off unless you turn it on.