For enterprise

Know who you are dealing with, without becoming the place their data leaks from.

Compliance, fraud, and onboarding teams need certainty about a counterparty and end up holding a filing cabinet of everyone who ever proved it. human.tech returns a verifiable result instead of a copy of the document, so the certainty stays and the liability does not.

2,184,101Verified accounts
51,557,974Credentials issued
438,809Attestation transactions on-chain
150+Ecosystem partners

Verified accounts and credentials as of 2026-06-10. On-chain figures as of 2026-07-31.

Built on open standards
ICAO·W3C Verifiable Credentials·eIDAS 2.0·FATF Travel Rule
Read the third-party audits
The problem, decomposed

Every onboarding decision reduces to four questions.

Personhood, identity, disclosure, and authority. Most compliance stacks answer the first two by collecting everything and the last two not at all. Each of these has its own answer, and each answer can be given without collecting the person.

Is this a real person?

Proof of personhood

Establish that a record belongs to a real, unique human. The check holds across systems that never share a database, so one person cannot quietly become fifty applicants, fifty submitters, or fifty voters.

Human Passport →

Are they who they claim to be?

Identity verification

Government ID, residency, age, and screening against sanctions and politically-exposed-person lists. Each check returns a verifiable result a counterparty can trust, rather than another copy of the document.

Proof of Clean Hands →

What may be revealed, and to whom?

Privacy-preserving disclosure

Private by default, with disclosure set by rule instead of by habit. What is published, what goes only to a regulator, and what stays sealed is decided up front, and every disclosure is provable after the fact.

Clean SDK →

Who may act on their behalf?

Delegated authority

Wallets a person holds themselves, and agents that operate inside limits a human set in advance. Every action carries the authority it was granted, so a delegate can be given real reach without being handed the account.

WaaP →
What you integrate

Three pieces, one compliance model.

A screening result you can show a regulator normally arrives attached to a record you would rather not be holding.It does not have to arrive that way.

Clean SDK

The checks, as a library

Add private, screened transactions without building identity, sanctions, or zero-knowledge proving yourself. Every transfer proves a unique human and clean funds in zero knowledge, in a few lines of code.

See Clean SDK →
Shield

Privacy with compliance, in production

Shield moves funds onto a private ledger and back, screening every transfer at entry and exit. It is the reference deployment of the same primitives, which means the compliance model has been run against real money rather than only described.

See Shield →
Proof of Clean Hands

A clean result, not a dossier

A person proves they pass sanctions and illicit-funds screening without handing you the identity behind the proof. You get an answer you can defend to a supervisor, and you do not inherit a file you now have to protect.

Read the primitive →
The disclosure model

Private by default. Disclosed by rule.

This is not a promise that nothing is kept. Encrypted material is kept, because a regulator can compel disclosure and a system that retained nothing could not answer them. The claim is narrower and stronger: what is kept is ciphertext, the rule that opens it is written before anything is collected, and the opening is enforced by cryptography rather than by policy.

Human Passport, the personhood layer, is built the same way. It stores no IP addresses, names, emails, or personal details to do its job.

Proof of Clean Hands, from the beginning →
  • 01

    Private by default

    No field is exposed because a system happened to collect it. Sealed is the starting state, and every disclosure after that is a decision somebody made on purpose.

  • 02

    Disclosure set by rule

    What is retained is retained as ciphertext. It opens only under a rule agreed in advance and enforced cryptographically, so releasing it is never a matter of an operator changing their mind.

  • 03

    Proved, not photocopied

    A check returns a zero-knowledge proof that the condition holds. The verifier learns the answer and never receives the document, so your systems stop accumulating copies you would then have to defend.

  • 04

    Provable after the fact

    Every disclosure leaves evidence that it happened and under which rule. A supervisor can reconstruct what was released without you keeping a plaintext archive to show them.

Bring us the rule you have to satisfy.

We work with compliance, fraud, and onboarding teams, and with the regulators that supervise them. Tell us the check you are required to make and we will tell you plainly whether cryptography helps, including when it does not.

Holonym Foundation, a Delaware public benefit corporation