A Claude Code skill that helps you find data brokers selling your personal information and generates CCPA/OCPA opt-out requests to get your data deleted.
- Collects your information interactively through a step-by-step questionnaire (name, DOB, addresses, phone, email, social media, employers, and more)
- Searches the web using parallel agents to find which data brokers have your data
- Asks you to verify which results are actually you (handles common name collisions, family members, etc.)
- Generates personalized opt-out requests — pre-filled emails and a checklist of web forms to submit
- Sends opt-out emails directly from your Gmail account (optional, requires Gmail MCP)
Covers 50+ data brokers across people-search sites, commercial data brokers, B2B platforms, and telecom databases.
Clone the repo anywhere you like, then symlink it into your Claude Code skills directory:
git clone https://github.com/zachsis/databrokersbegone.git ~/repos/databrokersbegone
ln -s ~/repos/databrokersbegone ~/.claude/skills/databrokersbegoneTo update later, just pull:
cd ~/repos/databrokersbegone && git pullThe symlink means Claude Code picks up changes immediately — no copying needed.
git clone https://github.com/zachsis/databrokersbegone.git ~/.claude/skills/databrokersbegoneTo update:
cd ~/.claude/skills/databrokersbegone && git pullcd your-project
mkdir -p .claude/skills
git clone https://github.com/zachsis/databrokersbegone.git .claude/skills/databrokersbegone- Claude Code CLI, desktop app, or IDE extension
- WebSearch permission enabled (Claude Code will prompt you on first use)
- Internet access for data broker searches
If you want Claude to send the opt-out emails directly from your Gmail account instead of just generating text files, you need the Gmail MCP server connected.
Setup:
- In Claude Code, run
/mcpand select "claude.ai Gmail" - Complete the OAuth flow in your browser to authorize access to your Gmail account
- When running the skill, Claude will ask whether you want to send emails directly or just generate files
What it does: Sends the pre-filled CCPA/OCPA opt-out emails to each data broker's privacy address directly from your Gmail. You'll be asked to confirm before any email is sent.
Without Gmail MCP: The skill still works — it generates .txt files in ./databrokersbegone_emails/ that you can copy-paste into your email client manually.
In Claude Code, run:
/databrokersbegone
Or with a name:
/databrokersbegone Jane Smith
The skill walks you through a step-by-step questionnaire:
- Identity basics (name, aliases, DOB)
- Addresses (current + previous)
- Contact info (emails, phones — current and old)
- Online presence (social media, usernames, domains, known breaches)
- Professional & assets (employers, licenses, education, vehicles, property)
- Family disambiguation (relatives with similar names to exclude)
- Profile confirmation before searching
After running, you'll have these files in your current directory:
| File | Purpose |
|---|---|
databrokersbegone_profile.json |
Your verified personal profile (used for searches) |
databrokersbegone_checklist.md |
Phased action plan with all opt-out steps |
databrokersbegone_emails/*.txt |
Pre-filled opt-out emails ready to send |
databrokersbegone_report.md |
Summary report with follow-up dates |
The generated opt-out requests cite:
- CCPA (California Consumer Privacy Act) — applies to all CA-registered data brokers regardless of where you live
- OCPA (Oregon Consumer Privacy Act) — for Oregon residents
- Additional state privacy laws are referenced in
brokers.mdfor CO, CT, VA, TX, MT, UT
- Run quarterly. Data brokers re-add your data from new public records. Set a reminder to re-run every 3 months.
- Start with the California DROP portal (privacy.ca.gov/drop/) — one request covers all CA-registered brokers.
- Be persistent with difficult brokers (MyLife, Radaris). File complaints with your state AG if they don't comply within 45 days.
- Use all name variations when searching — brokers may file you under different spellings.
MIT