unbroker

Open-source agent workflow for data-broker opt-outs, consent, ledgering, and re-scans.

github.com

Zero KYC
Evidence and facts →

Open-source agent workflow for data-broker opt-outs, consent, ledgering, and re-scans.

Common useSelf-hosted data broker removalPrivacy Tools / Developer ToolsOperator dataHosted

Identity checksZero KYCNo document check recorded · identity exposure level 0/4

Evidence and riskVerified evidenceCautionMaterial claims checked against current sources.; those sources show trade-offs worth reading.

Last reviewedReviewed 5 Jul 2026KYC checked 5 Jul 2026 · unknown jurisdiction · Source → official documentationHow to cite this pageEvidence confidence94/100

Evidence and facts

JURISDICTIONUnknown

CAUTIONThe person must consent before a scan. The workflow keeps local records and limits fields sent to broker forms. A later re-scan verifies removal; a broker confirmation does not.

AUDITED BYNo audit listed

OPERATOR DATAHosted operator recorded

EVIDENCE CONFIDENCE

THIRD-PARTY REPORTED1/5

Why evidence is 94/100Formula 3.1

Source coverageMaterial claims checked against current sources: +70
Review ageOldest recorded check is 49 days old: +24

Full scoring method

LAST CHECKED2026-07-05

LAST UPDATED2026-07-05

Specs

DOCUMENT CHECKNone recorded

IDENTITY EXPOSURELevel 0/4

KYC TRIGGERSNo KYC account is required for the open-source skill itself. Broker opt-out forms may still request identifying fields to match and remove records.

FEEFree

NETWORKSCLI, Browser, Email, Cron

CATEGORIESPrivacy Tools, Developer Tools, Frameworks

COMMON USESSelf-hosted data broker removal, Doxxing cleanup with consent, Recurring broker re-scan workflows

FEATURESOpen source, Hermes skill, Data broker opt-outs, Consent gate, Local ledger, Least-disclosure planning, Email verification polling, Recurring re-scan queue, +2 more

TORNot listed

REGIONSGlobal availability

Review analysis, source material, related services, and history

Privacy automation

Automated removal and data shared

A local workflow with a deterministic queue, ledger, human fallback digest, and recurring re-checks.

Privacy tools Removal guide Self-host

Controls

CLIBrowserEmailCronManual digest

Autonomy3 / consented loop

Re-checkscheduled re-scan queue

How it works

Consent gatedDeterministic queueHuman fallbackRecurring recheckLeast disclosureLocal ledger

Human fallback

Hard CAPTCHAGovernment IDPhone callFax

Limits

Consent requiredYes

Local PIIYes

Least disclosureYes

Re-checksYes

Privacy

Personal data locationLocal by default

DisclosureLeast disclosure

VerificationRe-scan before confirmed

The privacy gain is control and auditability. The risk is PII handling: names, addresses, phone numbers, aliases, and emails are still processed locally and disclosed to broker-controlled removal channels when needed.

Where personal data goes

1consenting subject intake
2local unbroker record and ledger
3agent browser or web extraction pass
4broker opt-out form or rights email
5email verification link
6scheduled removal re-scan

About

Open-source Hermes Agent skill for consent-gated data broker removal, run through a local CLI and ledger.

Analysis

OVERVIEW

unbroker is an open-source Hermes Agent skill, authored by SHL0MS in the NousResearch repository, that plans consent-gated data broker opt-outs with a local CLI, ledger and recurring re-scan queue.

LIMITS

The tool handles sensitive personal identifiers by design and its broker dataset is adapted from a CC BY-NC-SA licensed list, so reuse carries attribution and non-commercial constraints, and a broker's confirmation alone does not verify removal without a re-scan.

USEFUL FOR

Self-hosters running consent-gated broker removal or doxxing cleanup who want a local ledger instead of sending data to a removal company.

Sources · reviewed 2026-07-16

GitHub repository ↗

Corporate identity

Registry-sourced, not audited. The facts below come from cited web research rather than a direct registry query. Each claim links its own source.

PARENT ENTITY: Nous Research, Inc.source ↗

Registry research · reviewed 2026-08-09

We wrote about this

How to Self-Host unbroker for Data Broker Removal

Frequently Asked Questions

Is identity verification required?

No identity verification is recorded for typical use. No KYC account is required for the open-source skill itself. Broker opt-out forms may still request identifying fields to match and remove records.

What can it automate?

It uses cli, browser, email, cron, manual-digest and requires recorded consent.

Where is it available?

Recorded availability: GLOBAL.

Is the operator based in a Five Eyes country?

The jurisdiction is not publicly confirmed. Check the provider site for incorporation details.

How are identity, operator, and evidence fields reported?

Identity exposure is level 0 of 4. A hosted operator is recorded. Jurisdiction is shown as context, not a safety verdict. Evidence confidence is 94/100 and recorded risk is caution.

How can it be controlled?

Available controls: CLI, Browser, Email, Cron.

Related Services

addy.ioaddy.ioaddy.io · Email · GB

Email aliasing, self-hostable, crypto accepted.

Evidence94 Zero KYCCaution

About Visit ↗

BTCPay Serverbtcpayserver.orgbtcpayserver.org · Merchants · JP

Self-hosted Bitcoin and Lightning payments.

Evidence59 Zero KYC

About Visit ↗

Calyx Institutecalyxinstitute.orgcalyxinstitute.org · Privacy Tools · US

US nonprofit privacy tools and hotspots.

Evidence94 Light KYCCaution

About Visit ↗

Sources and history

Service history

Latest meaningful changes to the facts shown on this provider page.

9 Aug 2026
Corporate registry information updated
Corporate
6 Aug 2026
Provider presentation updated
Evidence status, Recorded risk, Trust level
5 Aug 2026
Ship practical privacy release
Agent privacy / Data path, Agent privacy / Notes, Privacy warning

Full service history

9 Aug 2026updated
Corporate registry information updated
Corporate
not setEntity type: project-no-legal-entity; Governance model: company-sponsored; Repository url: https://github.com/NousResearch/hermes-agent/tree/main/optional-skills/security/unbroker; Parent entity: Nous Research, Inc.
Review source: official documentation · public history entry
8 Aug 2026updated
Provider summary rewritten
Description
Open-source Hermes Agent skill for consent-gated data broker removal. It plans searches, opt-outs, email verification, human fallbacks, and recurring re-scans through a local CLI and ledger. It is privacy tooling, not deletion proof.Open-source Hermes Agent skill for consent-gated data broker removal, run through a local CLI and ledger.
Review source: official documentation · public history entry
7 Aug 2026updated
Provider summary rewritten
Card summary
not setOpen-source tool for data broker removal.
Review source: official documentation · public history entry
6 Aug 2026updated
Provider presentation updated
Evidence status
not setverified
Recorded risk
not setcaution
Trust level
cautionnot set
Review source: official documentation · public history entry
5 Aug 2026updated
Ship practical privacy release
Agent privacy / Data path
consenting subject intake, local unbroker dossier and ledger, agent browser or web extraction pass, broker opt-out form or rights email, email verification link, scheduled removal re-scanconsenting subject intake, local unbroker record and ledger, agent browser or web extraction pass, broker opt-out form or rights email, email verification link, scheduled removal re-scan
Agent privacy / Notes
A consent-gated local workflow with a deterministic queue, ledger, human fallback digest, and recurring re-checks. It is designed for subject-authorized removal work rather than people-search profiling.A local workflow with a deterministic queue, ledger, human fallback digest, and recurring re-checks.
Privacy warning
Handles sensitive personal identifiers by design. The consent-gated flow uses subject authorization, local dossiers, least-disclosure broker forms, and re-scan verification. A broker confirmation alone does not verify removal; a re-scan verifies removal.The person must consent before a scan. The workflow keeps local records and limits fields sent to broker forms. A later re-scan verifies removal; a broker confirmation does not.
Review source: official documentation · public history entry
13 Jul 2026updated
Use plain operational unbroker language
Agent privacy / Notes
Useful because it turns broker removal into a consent-gated local workflow with a deterministic queue, ledger, human fallback digest, and recurring re-checks. It should not be run as OSINT against people who did not authorize it.A consent-gated local workflow with a deterministic queue, ledger, human fallback digest, and recurring re-checks. It is designed for subject-authorized removal work rather than people-search profiling.
Privacy warning
Handles sensitive personal identifiers by design. The workflow is for the subject or a person who gave consent. Keep dossiers local, disclose only required fields, and treat broker confirmations as untrusted until a re-scan verifies removal.Handles sensitive personal identifiers by design. The consent-gated flow uses subject authorization, local dossiers, least-disclosure broker forms, and re-scan verification. A broker confirmation alone does not verify removal; a re-scan verifies removal.
Review source: official documentation · public history entry
5 Jul 2026created
Add agent privacy unbroker lane
Provider profile
not setcreated
Review source: official documentation · public history entry

Only fields shown on the provider page are tracked. Private identifiers are never published.

Evidence basis: Claims on this page are linked to published sources for comparison, not certification, audit, endorsement, or recommendation; read the methodology and coverage map before relying on an entry.