---
name: betterprivacy
description: Find where the user's own personal data (name, address, phone, email) is published online, get it removed with GDPR/CCPA requests, track takedowns and check data breaches, using the BetterPrivacy MCP server. Use when the user asks what the internet knows about them, about people-search sites or data brokers, removing their data, or whether their email was in a breach.
---

# BetterPrivacy

BetterPrivacy (https://betterprivacy.me) finds pages that publish a person's own data — people-search sites, data brokers, directories, forums, news — ranks them by risk, and helps get them taken down.

## Connect

Two MCP servers (Streamable HTTP):

- **Account (recommended):** `https://betterprivacy.me/mcp/account` — signs in with OAuth to the user's BetterPrivacy account. Sees their saved results, statuses and breaches.
- **No account:** `https://betterprivacy.me/mcp` — a one-off scan preview (top 3 results) and removal letters. No sign-in.

Setup guides for each assistant: https://betterprivacy.me/agents

If neither server is connected, tell the user how to add one (link the guide) instead of guessing results.

## Rules

1. **Only the user's own data**, or someone who has asked them to act for them. Never look up other people. If the request is about someone else, decline and explain.
2. **Confirm before scanning.** `scan_my_exposure` needs `confirm_own_data: true`; ask the user first, and say their details are sent to an AI search provider.
3. **Nothing is sent without the user.** Removal requests are drafts. Show the full draft and the address; the user sends it themselves (dashboard or mail app). Never claim a request was sent.
4. **Change statuses only when the user says so** (`update_finding_status`).
5. **Free plan:** only the top 3 pages are visible; mention the rest are locked and link https://betterprivacy.me/#pricing once, without pushing.
6. Don't repeat sensitive details (home address, phone) back more than needed.

## Signed-in workflow (`/mcp/account`)

1. `get_my_privacy_overview` — plan, counts by risk and status, last check, breaches. If there's no scan yet, send the user to https://betterprivacy.me/onboarding.
2. `list_my_findings` — pages with `finding_id`, risk, status, exposed data and removal contact. Filter with `status` (`found` = still open) or `risk`.
3. For each open page, most sensitive first, offer:
   - **Request removal:** `draft_removal_request_for_finding` → show the draft and where to send it. After the user sends it: `update_finding_status` → `requested`.
   - **Fine with it:** `update_finding_status` → `fine`.
   - **Not me:** `update_finding_status` → `dismissed`.
4. Pages marked requested: if the user says a page is gone, set `removed`. Sites have 30 days to answer GDPR requests.
5. `check_my_breaches` — breaches can't be taken down; advise changing those passwords (and reused ones), turning on two-factor authentication, and watching for phishing.

New scans run in the app (Dashboard → "Scan again"), not through the assistant.

## No-account workflow (`/mcp`)

1. Ask for full name plus city/country (and optionally email, phone, usernames) and confirmation that the details are the user's own.
2. `scan_my_exposure` (takes 1–3 minutes) → explain the top results, most sensitive first.
3. `draft_removal_request` for a page the user wants gone.
4. To save results and track removals, suggest running the scan at https://betterprivacy.me/onboarding and connecting the account server.

## Explaining results

- **High risk:** people-search and data-broker profiles, or pages with a private address, phone, date of birth, relatives or ID data. Remove these first.
- **Company register sites** (North Data, OpenCorporates…) are low risk. Removal is unlikely: this site republishes the public company register, which you appear in when you run a company. To limit what's shown, ask the register itself.
- Use `get_service_info` for pricing, sources and FAQ.
