Skip to content
Sheet 1/3Privacy promise

Your code stays home.

Tokenbreak draws ads next to your prompt. It doesn't read what you're working on, and ads never go into Claude's context, so they cost zero tokens. Below is the complete list of what leaves your machine. That promise is in our terms as permanent.
Sheet 2/3What is sent

Every field, and what it's for.

The mod sends four kinds of request: one asking for ads, one when you send a prompt, impression reports, and reports or hides when you ask for them. See a real example of each.
FieldWhat it isExample
AuthorizationYour sign-in token from /ads login, which credits impressions to your GitHub accountBearer …
deviceIdA random id made on install, so your machines count separately1111…5555
modVersionWhich version of the mod is running0.6.0
surfaceWhere ads are drawn: a terminal, or the desktop app's Code tabterminal
turnId, turnTokenOur server's id and signed token for a turn, asked for when you send a prompt. They say a turn began, nothing about what you askedv1.…
adIdWhich ad was on screen00000000-…
formatbanner or theaterbanner
atWhen, in milliseconds1791063354000
shownMsThe longest stretch the ad stayed on screen, in milliseconds12400
serveTokenPaid ads only: our server's signed receipt for the ad, handed back unchanged. Our own ids and an expiry, nothing from your machinev1.…
reason, noteOnly when you report an ad or press ✕ on it: the reason you picked, and a note if you wrote onemisleading

Our server also sees your IP address, as any website would. We never store it as is: we keep a keyed hash of it on your device and turn records for 90 days, to spot one network running many accounts, then delete it. Clicking an ad goes through our redirect, which counts the click and sets no cookie. A paid ad's link names only its serve, and the advertiser gets UTM tags, never anything about you.

Sheet 3/3What is never sent

Never read, never sent.

  • Your code or any file on disk
  • Your prompts
  • Claude's replies
  • Tool calls: file reads, edits, shell commands
  • File names, repo names, branch names
  • Environment variables and secrets
  • Your terminal history
  • Your keystrokes

You can check all of this: the mod is open source, and its test suite fails if it ever hooks the prompt, the conversation or tool calls. Read the source. The legal version is the privacy policy.

what our server receives
> refactor the billing webhook to be idempotent
⏺ Read(app/api/webhooks/stripe/route.ts)
⏺ Update(app/api/webhooks/stripe/route.ts)
⏺ Bash(npm test -- webhooks)
⏺ Done. Webhook dedupes on event id now.
{"adId":"00000000-…","format":"banner","shownMs":12400}