Privacy Policy
The short version: TokenPincherprocesses your code and tool output locally on your machine. We don't see it, store it, or send it anywhere.
Local processing
Compression happens entirely on your machine. No code, tool output, or logs are sent to TokenPincherservers as part of compressing them. What the compressed output is used for after that is between you and whichever model or client you're using (Claude Code, Codex CLI, or another MCP client) — TokenPincherdoesn't sit in that data path.
Stats stored locally
Tokens-saved and dollars-saved stats are written to a local file in ~/.tokenpincher on your machine. These stats aren't uploaded anywhere by default.
The CLI never asks for or collects an email address. The only place an email exists is Stripe checkout when you buy Pro — Stripe uses it for your receipt and subscription management, and we can see it there for support purposes.
License validation
If you upgrade to a paid plan, your license key is validated against our licensing API. That call checks the key only — it doesn't transmit your code or tool output.
No analytics in the CLI
The TokenPincherCLI and MCP server don't phone home usage analytics. Our marketing site (tokenpincher.io) may use standard website analytics to understand traffic — that's separate from anything the CLI does on your machine.
Questions
Reach us at hi@tokenpincher.io. See also our Terms of Service.