TokenSpend measures AI coding spend by reconciling Claude Code usage against your GitHub activity. We are built metadata-first: the capture hook parses usage metadata only, and none of your code or conversation content leaves your machine.
What we collect
- Usage metadata: model, token counts, and computed cost per session.
- Git metadata: repository name, branch, and commit SHA used to attribute spend to pull requests.
- Identity: your email and GitHub login, to associate usage with the right engineer and workspace.
- Router metadata: model, token counts, cost, latency, and status for each request. Never prompts or responses.
What capture never collects
The fleet capture hook never sends your prompts, the model’s responses, your source code, or your diffs. It is metadata-only by design, and Claude Code content telemetry stays off.
Token Router content
TokenSpend does not store Router prompts or responses. Requests pass through in memory only to forward them and return the reply. Request logging is no longer available, and history stored under earlier versions of this notice was deleted on October 2, 2026.
How we use it
We use workspace data to operate and improve TokenSpend, meter Router requests, attribute spend to work, keep the service secure, and support customers. We do not sell personal data.
Downstream model providers
Router requests are sent to the selected model provider or a contracted inference processor. Downstream handling follows the applicable provider account, configuration, policy, and contract. The Trust center describes the boundary for BYOK and managed routes.
TokenSpend does not currently offer provider ZDR. Any existing downstream handling requirement remains enforced even though its dashboard control is hidden. Unsatisfied requirements block forwarding, including on retries and fallback. TokenSpend storing no content is not itself provider ZDR. Metadata records policy changes and each strict attempt's eligibility decision.
Retention and deletion
- Request and response bodies are never stored.
- Metering receipts remain metadata-only so usage and cost stay auditable.
- Account, workspace, capture, and receipt metadata is kept while needed to operate the service, meet legal obligations, and resolve disputes.
Access and security
TokenSpend holds no Router prompt or response content, so none can be viewed, exported, or disclosed. TokenSpend does not provide a general admin browser across customer workspaces. Contact us to request access, correction, export, or deletion of account and metadata records.
Changes
Version 1.4, October 2, 2026: TokenSpend no longer stores Router prompts or responses. Request logging was removed and previously stored history was deleted. Current and archived versions are listed in the legal version history.
Privacy, deletion, DPA, and processor-list requests: privacy@tokenspend.dev.