Skip to content

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

Merged
JustMaris merged 1 commit into
mainfrom
docs/verified-list-caveat
Sep 12, 2026
Merged

docs: clarify what "verified" does and doesn't mean#60
JustMaris merged 1 commit into
mainfrom
docs/verified-list-caveat

Conversation

@JustMaris

Copy link
Copy Markdown
Member

Small follow-up to #55. The README's "Choosing a broker list" section said the verified list holds "confirmed data brokers with a current first-party privacy email" — accurate about what the research pass did, but a reader could take "confirmed" as a stronger promise (that a broker will actually act on a request) than any static list can make. Adds one paragraph making that explicit.

"Confirmed data brokers with a current first-party privacy email" reads
stronger than what the verification pass actually did: it confirms
identity and a working contact (plus a CA registry cross-check for most US
entries), not that any broker has been sent a request and shown to honor
it - no static list can promise that. Says so plainly instead of letting
"confirmed"/"verified" imply more than it does.
@JustMaris
JustMaris merged commit f3a1f13 into main Sep 12, 2026
@JustMaris
JustMaris deleted the docs/verified-list-caveat branch September 12, 2026 14:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant