BuilderPerks adds opt-in, clearly labeled devtool perks to AI builder workflows. The product is designed to avoid private prompts, source code, command output, file paths, secrets, and full page text.
Effective June 16, 2026.
The Chrome companion can read visible text on supported ChatGPT and Claude pages only after you enable BuilderPerks cards. It uses that text locally in your browser to choose a broad category such as database work, deployment work, observability work, browser automation, AI app work, or code review.
The extension does not send the page text, your prompts, generated answers, source code, file paths, command output, secrets, or credentials to BuilderPerks.
BuilderPerks may receive your selected API URL, placement identifier, broad match reason or category, source surface, impression/click/relevance action, and optional feedback you choose to submit. If you register a builder, publisher, proof session, or advertiser pilot, we receive the form fields you submit, such as name, email, surface, broad keywords, proof notes, and contact details.
We use this information to show and measure clearly labeled BuilderPerks placements, prevent unwanted categories, improve relevance, support users, verify proof sessions, report aggregate performance to advertisers, and operate the product.
We do not sell your prompts, source code, browsing text, command output, secrets, or personal data. We do not transfer user data for personalized advertising, retargeting, credit scoring, or data broker use. Sponsored cards are selected by BuilderPerks placement data and broad local matching, not by selling private workflow context.
You can disable cards, pause cards for the day, dismiss any card, mark a card as not relevant, hide
categories, and uninstall the extension at any time. Terminal and CLI helpers store local configuration
under ~/.builderperks; removing that directory removes local BuilderPerks configuration.
The CLI also supports local controls such as builderperks pause,
builderperks resume, builderperks mute sponsor NAME, and
builderperks block-category CATEGORY. These preferences stay on your machine and are used
to avoid categories or sponsors you do not want to see.
Terminal and overlay integrations can write a local render ledger at
~/.builderperks/impressions.jsonl after a sponsored line or card is actually rendered.
The ledger is local proof/debug data only. It is not advertiser billing, publisher payout proof, or
fraud reconciliation. It does not store prompts, source code, command output, file paths, terminal
transcripts, or secrets.
BuilderPerks serves approved seed/direct and reviewed partner-feed offers through the BuilderPerks API. The Chrome companion does not load advertiser scripts or remote executable code into ChatGPT or Claude pages. Restricted partner backfill is off by default and only used for surfaces that explicitly opt in and pass approval checks.
Send privacy, deletion, or product questions through the feedback form on the BuilderPerks site or by replying from the email address used in your BuilderPerks workflow registration.