unbroker finds where a consenting person's info is exposed across data brokers and people-search sites and files the removals, running as far as each site allows and handing only genuinely human-only steps (hard CAPTCHA, gov-ID, phone, fax) back as an end-of-run digest. - Deterministic stdlib CLI (scripts/pdd.py) owns config, dossiers+consent, the broker DB, tier planning, the ledger, email, and the autonomous action queue; the agent scans/submits with native tools (web_extract, browser_*, delegate_task, cronjob, terminal). - Verify-before-disclose, least-disclosure (never volunteers SSN), consent gate, opaque ids, optional age-at-rest encryption, file-locked ledger. - Jurisdiction-aware (CCPA/CPRA, GDPR, generic); CA DROP one-shot covers the state registry (~545) in a single request; BADBOOL + curated people-search coverage; scheduled re-scan for re-listing. - No CAPTCHA-solving services or anti-bot bypass; browser email mode needs no stored password. - 85 hermetic tests (tests/skills/test_unbroker_skill.py; SMTP/IMAP via injected fakes, registry via CSV fixtures). Ships placeholder data only. Broker dataset adapted from BADBOOL (Yael Grauer, CC BY-NC-SA 4.0).
2.1 KiB
California DROP portal (highest-leverage lever)
The California Delete Request and Opt-out Platform (privacy.ca.gov/drop) lets a California
resident demand deletion from every registered data broker with a single verified request, for
free. DROP is live (as of 2026); registered brokers must begin processing requests on
2026-08-01. The registered universe is the California Data Broker Registry (~545 brokers in
2025), which this skill ingests as its own coverage lane (pdd.py registry); one DROP request covers
all of them, which is how this skill reaches (and exceeds) the breadth of commercial services.
When to use
For any subject with residency_jurisdiction starting US-CA, sequence DROP first: pdd.py next
surfaces a single drop_submit action covering the whole registry. Then handle the individual
people-search sites (which are also worked directly because they hold free, indexed listings). After
filing, run pdd.py drop <subject> --filed so the loop stops re-surfacing it. For non-CA subjects
DROP does not apply; cover the registry brokers with targeted CCPA/GDPR deletion emails
(pdd.py registry --search, then pdd.py send-email).
Flow (agent-assisted, mostly human verification)
- The operator creates/verifies a DROP account (identity verification is required by the state; this
is a human step -
human_task_queued). - Submit one deletion request covering all registered brokers.
- Record a single ledger case
case_<subject>_dropto track it; marksubmitted->awaiting_processing. Registered brokers must process deletions on the state's schedule. - After the DROP cycle, re-scan the people-search long tail and only act on sites still showing data.
Caveats
- DROP covers registered data brokers, not every people-search site. Keep doing the individual opt-outs for non-registered sites.
- Identity verification means parts of this cannot (and should not) be fully automated.
- FCRA-regulated brokers (flagged in the registry,
optout.fcra) hold consumer-report data with separate rules; deletion may be limited and a dispute or security-freeze may apply instead.