Skip to content
CUNICULA

unbroker

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

github.com

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

Common useSelf-hosted data broker removalPrivacy Tools / Developer ToolsOperator dataUnknown
Identity checksNo routine 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 25 Oct 2026KYC checked 25 Oct 2026 · unknown jurisdiction · Source → official documentationHow to cite this pageSource coverageVerified evidenceRecorded riskCaution
Evidence and facts

Evidence and facts

CUNICULA SCORE 4.0
80/100Reviewed evidencePrivacy 25/25 · Control 20/20 · Transparency 12/20 · Security 17/25 · Accountability 6/10 · Method
JURISDICTIONUnknown
CAUTIONCase 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.
AUDITED BYNo audit listed
OPERATOR DATAUnknown
SOURCE COVERAGE
Verified evidenceTHIRD-PARTY REPORTED2/4Reviewed 25 Oct 2026 · Source → official documentation
LAST CHECKED2026-10-25
LAST UPDATED2026-10-25

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 software; model, browser, email and hosting costs may apply.
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

Consent gates the workflow. The agent can submit routine requests without per-submission approval; difficult cases can require human action.

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 PIIReview
Least disclosureYes
Re-checksYes
Privacy
Personal data locationMixed
DisclosureLeast disclosure
VerificationRe-scan before confirmed

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.

Where personal data goes
  1. 1Consenting subject intake
  2. 2Local case files and ledger
  3. 3Agent with configured local or cloud browser
  4. 4Broker forms or email
  5. 5Optional email provider and Google Sheets tracker
  6. 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

OVERVIEW

Open-source Hermes skill for consent-based data broker opt-outs, with local case records and optional external browser, email and tracking services.

LIMITS

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.

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.

Corporate identity

Provider statements; Other cited research. Not audited. Each claim links its own source.

PARENT ENTITY
Nous Research, Inc.provider statement ↗
Corporate identity research · reviewed 2026-10-25

We wrote about this

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.

Related Services

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.