Open consent for
human identity.
A protocol any system can call before it displays, edits, generates, publishes, verifies, or distributes a person's face, voice, likeness, motion, style, or work.
Check consent
before identity access
Authorize scope
who, what, where, how long
Prove use
receipt, watermark, registry
What DIAP protects
Human identity is now a software surface.
Identity no longer lives only in contracts, footage, recordings, or portfolios. It is becoming an input to products. DIAP gives those products a shared way to ask permission before use and prove what happened after use.
Face and likeness
portraits, avatars, doubles, digital replicas, profile images, campaign imagery
Voice and sound
voice agents, dubbing, cloning, synthetic vocals, narration, audio ads
Motion and style
gait, gesture, performance capture, signature movement, embodied avatars
Work and authorship
scripts, writing, characters, images, music, creative style, training references
Runtime path
Consent becomes an API check.
DIAP is not a marketplace, agent, model, social network, or licensing middleman. It is the consent and proof layer those systems can call when human identity is involved.
Identify
A product detects that a human identity or protected work is about to be displayed, edited, generated, verified, distributed, or used as reference.
Check visibility
The product asks whether the identity or module can even be discovered, listed, selected, or previewed in that context.
Request scope
It requests a grant with exact action, asset, project, app, territory, duration, output type, and policy profile.
Authorize or deny
DIAP returns a signed short-lived token or fails closed. A yes for one use is not a yes for every use.
Record proof
After use, the product submits a receipt and attaches a watermark, output hash, registry entry, or verification handle.
Revoke
When consent changes, future checks and tokens update. Products receive events and stop future use outside the grant.
diap.my.id
The human-facing identity vault.
diap.me explains the protocol. diap.my.id is the secure vault layer other systems can integrate into their own products. A SaaS app, creative tool, marketplace, or platform can offer DIAP-protected identity vaults to its users without building custody, consent, revocation, receipts, and audit infrastructure from scratch.
See the vault layerIdentity modules
Face, voice, likeness, motion, style, and work can be represented as permission-controlled modules.
Layer 1 visibility
Control whether a module can be discovered, previewed, listed, or selected before any use request exists.
Layer 2 grants
Approve or deny scoped requests from products: what use, which output, for how long, and under what constraints.
Kill switch
Revoke future access to one module, one app, one grant, or the whole vault when consent changes.
Receipts
See what was authorized and what proof was submitted after a product used the grant.
SaaS-ready vaults
Any product can integrate DIAP so its own users get secure identity vaults without that product storing raw identity data.
The protocol has four jobs.
Request consent. Verify scope. Record use. Revoke cleanly.
Visibility
Can this system discover or display this identity?
Authorization
Is this exact use allowed now?
Proof
Which token, receipt, watermark, or registry entry proves it?
Revocation
What happens when consent changes?
What a grant says
Permission is scoped, not implied.
Uploading a file, appearing in public, or being technically reproducible does not mean every product has permission. DIAP turns the permission question into signed, narrow grants.
Example request
POST /api/v1/license/request subject: did:diap:maya-chen module: voice right: synthetic_dubbing project: documentary-localization territory: EU expires: 2026-11-01 receipt_required: true
Who calls DIAP
One consent layer across many products.
Any system that can touch a person's identity can integrate the same check: discover, request, verify, use, receipt, revoke.
diap.my.id is vault infrastructure for other products.
A SaaS company does not need to become an identity custodian to offer DIAP security. It can integrate DIAP into its own project, send users into secure hosted vault flows, and receive only policy decisions, signed grants, webhooks, and receipts. We provide the vault layer; partners keep their product experience.
Read the system.
Short pages first. Full spec when needed.