HUMΛN Passport — portable, human-owned identity

Overview

HUMΛN Passport gives each person portable control of their digital identity: private data custody, explicit consent on every disclosure, and faster sign-ins that do not require third parties to hold raw identity records. Start by creating a Passport on your device or request integration access for your service.

Key claims

• HUMΛN Passport gives individuals portable control of their identity, enabling private data custody, explicit consent, and lower-friction sign-ins.
• Under Principle One, authoritative identity records are held by the person or their chosen storage; relying services receive proofs, not raw datasets.
• HUMΛN Passport operates as a production identity layer composed of device-rooted keys, DIDs, credential issuers, and verifier endpoints that services call.
• Integrations replace bulk attribute exchange with selective disclosure and proof verification, which reduces data retention and audit complexity for relying services.
• Consent and disclosure events are logged as part of the verifiable flow so audits do not require central retrieval of raw identity attributes.

Principle One

All identity material lives under the person’s control. Device-rooted cryptographic keys, a decentralized identifier (DID), and any verifiable credentials belong to the person or their chosen storage. Services receive cryptographic proofs, not bulk datasets. That changes three integration rules:

• Data custody. The authoritative record stays with the person. Relying services receive claims or proofs and keep only the minimum needed for their workflow.
• Consent logs. Every disclosure is logged as a consent event the person can review or revoke. Logs are attested as part of the verifiable flow so audits do not require central retrieval of raw attributes.
• Integration contracts. Contracts between a service and a person are about which claims may be requested, how long verifiers retain receipts, and what evidence is required for re-issuance or revocation.

Production-forward: Passport is an identity layer you run now

HUMΛN Passport is a running identity layer composed of device-origin keys, DID records, credential issuers, and verifier endpoints your services call. Integration is an API and SDK surface for issuing credentials, requesting selective disclosure, and verifying cryptographic proofs. In production this reduces friction by turning expensive data exchanges into lightweight proof checks the service can perform in real time.

What integration looks like

Embed the Passport SDK on the client for key and consent handling, call a verifier endpoint to check proofs, and accept selective disclosures instead of storing raw attributes. Expect to adapt your retention and audit policies to the Passport model rather than rely on existing identity stores.

• Integrations replace bulk attribute exchange with selective disclosure and proof verification, which reduces data retention and audit complexity for relying services.

flowchart LR
  A[Device-rooted key] --> B[DID]
  B --> C[Verifiable credential (issued)]
  C --> D[Selective disclosure request]
  D --> E[Relying party verifies proof]

Next step

If you are a person, create a Passport and retain your consent log. If you run a service, request integration access and start with one proof-based flow like sign-in or age verification to validate the model in production.

Create a Passport

Request integration access