Email aliasing, self-hostable, crypto accepted.
unbroker
Open-source agent workflow for data-broker opt-outs, consent, ledgering, and re-scans.
github.com
- No routine KYC
- Evidence and facts →
Open-source agent workflow for data-broker opt-outs, consent, ledgering, and re-scans.
Evidence and facts
Evidence and facts
Specs
Review analysis, source material, related services, and history
Automated removal and data shared
Consent gates the workflow. The agent can submit routine requests without per-submission approval; difficult cases can require human action.
Local files are plaintext by default, with optional age encryption. External browser, email and tracker choices affect where personal data goes. A broker confirmation alone does not establish deletion.
- 1Consenting subject intake
- 2Local case files and ledger
- 3Agent with configured local or cloud browser
- 4Broker forms or email
- 5Optional email provider and Google Sheets tracker
- 6Scheduled listing re-scan
About
Open-source Hermes skill for consent-based data broker opt-outs, with local case records and optional external browser, email and tracking services.
Analysis
Open-source Hermes skill for consent-based data broker opt-outs, with local case records and optional external browser, email and tracking services.
Case files are local by default and unencrypted unless encryption is enabled. Browser, email, model or Sheets services may receive personal data. A re-scan checks visible listings, not total deletion.
Self-hosters running consent-gated broker removal or doxxing cleanup who want a local ledger instead of sending data to a removal company.
Corporate identity
Provider statements; Other cited research. Not audited. Each claim links its own source.
- PARENT ENTITY
- Nous Research, Inc.provider statement ↗
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.
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. Hosted operator data has not been established. Jurisdiction is shown as context, not a safety verdict. Source coverage is verified evidence, last reviewed 2026-10-25, and recorded risk is caution.
How can it be controlled?
Available controls: CLI, Browser, Email, Cron, Manual digest.
What can it automate?
It uses CLI, Browser, Email, Cron, Manual digest and requires recorded consent.
Sources and history
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.