Lifecycle
From account creation to revocation.
Hash.Contact keeps identity progressive and consent explicit at every step.
Create Hash.Contact
The user stays in control and can defer higher assurance until a use case requires it.
Verify mobile/email
The user stays in control and can defer higher assurance until a use case requires it.
Increase assurance when needed
The user stays in control and can defer higher assurance until a use case requires it.
Use with participating applications
The user stays in control and can defer higher assurance until a use case requires it.
Review exactly what is requested
The user stays in control and can defer higher assurance until a use case requires it.
Approve or deny
The user stays in control and can defer higher assurance until a use case requires it.
Review activity and revoke later
The user stays in control and can defer higher assurance until a use case requires it.
Consent mockup
Every request should be understandable before approval.
Example request
Acme Hotels
Wants to verify
- Identity verified
- Age above 18
- Address verified
Not shared
- Name
- Exact date of birth
- Identity document number
Purpose: Hotel guest verification
Access: One-time access
Progressive identity levels
The UI treats identity assurance as a configurable ladder rather than a single all-or-nothing profile.
Level 0
CompleteAccount Created
A Hash.Contact account exists with no extra identity requirement.
Level 1
CompleteContact Verified
Mobile and email verification are available for basic trust.
Level 2
CompleteBasic Identity
Name or basic profile verification can be added when needed.
Level 3
CurrentGovernment Identity
Government identity verification is complete for higher-assurance requests.
Level 4
AvailableEnhanced Verification
Address and additional credentials can be verified for specific workflows.
Level 5
AvailableAdvanced Assurance
High assurance remains configurable by jurisdiction and product policy.
Current assurance
successLevel 3
Government identity verified
Next available
infoLevel 4
Address and extra credentials
Required now
neutral0
No forced upgrade
Configurable
warningYes
Policy driven levels