KYC ("know your customer") proves who someone is and gives that identity to the business. Proof of personhood proves that someone is a real, unique person, and can do it without the business learning who they are. Both often start with the same government ID check. What differs is what the business receives, and what it has to keep.
The short answer
- Use KYC when you're legally required to know exactly who your customer is: banks, payment and money-transfer services, crypto exchanges, some marketplaces that pay out money, and some age-restricted sales.
- Use proof of personhood when what you need is one real person per account: communities, free tiers, referrals and giveaways, polls and reviews, dating and marketplaces before payouts.
Most sites asking users for an ID only need the second.
Side by side
| KYC | Proof of personhood | |
|---|---|---|
| Question answered | Who is this person? | Is this a real, unique person? |
| What the business receives | Name, birth date, address, document details, often images | A yes, and an ID for that person |
| Stops duplicate accounts? | Yes, by matching identities | Yes, by the per-person ID |
| Data the business must protect | Identity documents and personal data | An opaque ID |
| Breach impact | Serious: identity theft risk for every customer | Low: the ID means nothing elsewhere |
| User reaction | Many people hesitate to upload an ID | Easier to accept: "we won't learn who you are" |
| Reusable across sites? | Usually not: each business checks again | Often yes: verify once, sign in anywhere |
| Satisfies legal KYC and AML duties? | Yes, when done to the regulator's standard | No |
Why most sites don't need KYC
KYC exists for anti-money-laundering and fraud rules in regulated industries. A community, an app or a marketplace without payouts usually has no such duty. It wants fewer bots, fewer banned users coming back, and fewer people farming bonuses. KYC solves that, but at a cost:
- You hold identity data. Documents, names and birth dates become a breach target and a legal duty under privacy laws.
- You lose sign-ups. Asking for an ID on a site someone has just found drives many genuine people away.
- You pay per check, and the same person is checked again by every business they use.
Proof of personhood keeps the useful part, uniqueness, and drops the rest. See how to verify users without storing their IDs.
Using both
The two work well together:
- Proof of personhood at sign-up, so every account is a unique real person from day one.
- KYC only when it's required, for example before the first payout or a regulated transaction, and only for the users who reach that point.
That keeps identity data to the smallest group of people who need it, instead of everyone who signs up.
How Human Pass fits
Human Pass is proof of personhood built on a government ID check. A person verifies once with an identity-verification provider; Human Pass keeps only one-way fingerprints of the document, so the same document can't make a second Human Pass; and each site gets a yes and an ID for that person on that site, nothing else. It isn't a KYC service and doesn't satisfy KYC or AML obligations.