Never collected or transmitted
WaitPerk never opens or reads Claude transcript files. It never stores or transmits prompts, responses, source code, file contents, filenames, working-directory paths, repository names, terminal history, or project structure.
Used only on your computer
Claude provides a broad status-line JSON object. The WaitPerk client immediately selects only the model display name, context percentage, session identifier, optional prompt identifier, and terminal width. Model and context are displayed locally. The identifiers are transformed with a device secret before any receipt leaves your computer.
Exact outbound event schema
A random, revocable credential used to authenticate the installed client.
An opaque identifier for the specific sponsor placement.
An HMAC generated locally from Claude’s session or prompt identifier. The raw identifier is not transmitted.
Used to diagnose compatibility and safely retire outdated clients.
When a qualified render receipt reached WaitPerk.
Network and retention
The hosting provider necessarily receives an IP address when the client connects. WaitPerk does not create a standalone raw-IP database field. Campaign, install, and ledger records are retained to validate deduplication and support accurate reporting to developers and advertisers.
Pause, uninstall, and deletion
Run python3 ~/.waitperk/waitperk.py pause to stop sponsor lines, or run python3 ~/.waitperk/waitperk.py uninstall to remove the status line, spinner verbs, and hooks WaitPerk added, leaving the rest of your Claude settings untouched. (Installs made before client 0.8.0 also carried an optional VS Code panel ad; updated clients and uninstall both remove that patch and restore the extension from its backup.) Data deletion requests are handled manually until self-serve account tooling ships.