For people
Understand control, privacy, portable credentials, consent, devices, and protected recovery.
Learn the holder experienceExplore holder-controlled identity, verifiable credentials, privacy-preserving disclosure, secure recovery, interoperability, and institutional trust.
Choose your path
UbID separates who issues evidence, who controls it, who verifies it, and who makes the final decision.
Understand control, privacy, portable credentials, consent, devices, and protected recovery.
Learn the holder experienceExplore issuance, verification, policy, governance, assurance, and regulatory alignment.
Review institutional trustStart with roles, trust contracts, standards, public discovery, and controlled partner integration.
Build with UbIDExplore UbID
Move from foundational concepts to products, institutional solutions, public standards, and controlled integration.
Understand the issuer–holder–verifier model, verifiable credentials, selective disclosure, and the trust lifecycle.
Explore the public UbID product portfolio and the responsibility of each product domain.
See how the UbID trust model applies to education, government, finance, healthcare, and enterprise access.
Review privacy, security, verification, recovery, cryptographic protection, and accountable operations.
Understand the identity, credential, authentication, and messaging standards that support interoperability.
Start from roles, trust, policy, and data minimisation before moving into controlled partner integration.
The trust lifecycle
Identity evidence is assessed under an explicit assurance and governance policy.
An accountable issuer creates a signed credential with defined scope and lifecycle.
The holder authorizes a proportionate presentation for a declared purpose.
The verifier checks provenance, integrity, status, freshness, binding, and policy.
Device lifecycle, recovery, rotation, and evidence preserve trust over time.
UbID design principles
Verify what is needed while reducing unnecessary document and profile replication.
Use recognized identity, credential, authentication, and messaging standards without exposing internal systems.
Treat continuity as a multi-stage, authorized, reviewable protocol rather than a support shortcut.
Connect policy, cryptographic results, lifecycle events, and operational outcomes without logging secret material.