Skip to content

docs: clarify what "verified" does and doesn't mean #60

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
JustMaris merged 1 commit into from
Sep 12, 2026
Merged

docs: clarify what "verified" does and doesn't mean #60

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -297,6 +297,13 @@ options:
broker_list: verified # or: broker_file: /path/to/your-own-list.yaml
```

"Verified" means each entry is confirmed to be a real data broker with a
current, working contact we found by hand — most of the US ones are also
cross-checked against California's data-broker registry. It doesn't mean
any of them have been sent a request and confirmed to actually act on it;
no list can promise that in advance. `eraser status`/`pipeline` is how you
find out what a broker actually does once you've emailed it.

The weekly CI audit keeps the full list from rotting — it clears dead email
domains automatically and opens a PR for review.

Expand Down