Legal

Privacy Policy

Last updated: July 18, 2026

TokenBeaver is built local-first: your prompts, your code, your file paths, and your tool outputs never leave your machine — optimization happens locally. What does leave your machine is a small, pseudonymous usage ping, and this page describes it completely.

1. The local-first boundary

TokenBeaver is a CLI gateway and VS Code extension that sits between your AI coding agent and your model provider. Optimization happens in-process on your own device. We never receive, store, or transmit:

—Your source code or file paths
—Your prompts or tool outputs
—Your API keys
—AI responses returned by the model

Requests go directly from your machine to your chosen model provider using your own key — we are never in the path of your billing relationship with that provider.

2. Pseudonymous usage telemetry

TokenBeaver sends a daily usage ping, on by default, tied to a hashed device fingerprint. That identifier is pseudonymous — not anonymous: the same install can be recognized over time, but we cannot tie it to your name or email, because we don't have them. Here is everything a ping can contain, in plain words:

What
Examples
Aggregate counters
Tokens saved, feature-use counts, limit-hits avoided, upgrade-prompt interactions, refund requests
Coarse category labels
Plan tier, agent/provider type, install type, a bucketed value range
Never
Code, prompts, file paths, or any per-request content — counters and labels only

3. Lifecycle state

We record which stage an install is in — installed, active, pro, or churned — against the same hashed fingerprint, so we can understand how the product is doing in aggregate. These records are kept for 90 days since the install was last seen, then deleted.

4. Nothing before consent

Zero telemetry is sent until you accept the Terms on first run. Before that, TokenBeaver makes no analytics calls at all.

5. Opting out

Any of these turns the telemetry off entirely — opt-out means zero telemetry network calls:

—The toggle on the dashboard's Settings page
—TOKENBEAVER_TELEMETRY_DISABLED=1 in your environment
—In the extension, VS Code's global telemetry setting is honored too

Calls you explicitly trigger — activating a license, opening checkout, requesting an email code — are part of the service, not telemetry, and still work.

6. The refund snapshot

Requesting a savings-guarantee refund sends an aggregates-only summary of that billing period — totals and counts, never event-level data — so we can apply the refund without asking you to prove anything.

7. Payments & email

Stripe processes all payment data; we never see full card numbers. If you go Pro, your email is used for receipts and license recovery — nothing else.

8. Lawful basis, retention & your rights

We process the pseudonymous telemetry under legitimate interest, and billing/licensing data under contract. Fingerprint-keyed records expire 90 days after the install was last seen; billing records are kept as long as legally required. You can request deletion of your device records at any time by emailing [email protected].

9. Changes & contact

We may update this policy as the product evolves; material changes will be reflected by the date above and, where required, by a fresh in-product consent. Questions? Email [email protected].