An account can show
- Someone completed a sign-up
- A session is authenticated
- He/She/It wants to use the product
PERSONHOOD CREDENTIAL · PEP
Give your product a trustworthy participation rule: confirm a human is behind an action, or count each participant once for a defined purpose.
THE PRODUCT PROBLEM
An account can show
A personhood rule can help answer
Personhood Credential complements your login, accounts, and sessions. Your product still makes every final authorization decision.
CHOOSE YOUR RULE
Confirm that a human is behind an action when automation or fake participation would undermine the experience.
Count a participant once for a defined purpose when duplicate participation would break the product rule.
Uniqueness is a product rule, not a requirement to expose a participant’s real-world identity.
USE CASES
HOW IT WORKS
PEP is the registration and trust layer for app policy and domains. Your app continues to own users, sessions, stored data, and authorization.
PRIVACY BY DESIGN
Users see what your app requests before they approve it.
Match each request to a clear product rule.
Request only the attributes needed for that decision.
FOR PRODUCT TEAMS
No. Your app still owns accounts, sessions, and access control. Personhood Credential adds a verification signal when a product rule needs it.
Choose Human Credential when you need a human behind an action. Choose Uniqueness Credential when the same person must be counted only once.
The request should be limited to the credential and attributes needed for the specific product decision. Users review the request in their wallet before approval.
Not by default. Your app should request only the information it needs; a personhood check does not require a copy of passport data.
Yes. Your product determines where verification belongs, such as registration, a vote, a claim, or another protected action.
Your backend does. It verifies the presentation and applies your application’s policy before permitting an action.
That depends on the action’s risk and your product policy. Re-check credential state before sensitive or recurring decisions.
START WITH THE RIGHT RULE