DKAM is built as a trust, verification, permissions, scoring and discovery layer for wallet-bound Blucks. Sensitive credential material stays with the holder. DKAM anchors integrity through hashes, issuer references and status, not through central storage of raw documents. This page sets out how that works in plain English.
Raw identity documents, transcripts and evidence are held on the holder side of the Bluck and disclosed only on the holder's terms.
DKAM anchors hashes, issuer references and status. Verifiers check proofs rather than downloading archives of raw documents.
Each Bluck is anchored to an identifier you control for life. Future-ready for institutional custody where required.
Every issuance, verification and access event is logged. Individuals see who has seen what. Sensitive admin review is itself logged.
DKAM stores only what is needed to run the ecosystem: wallet linkage, hashes, status, consent events and discovery metadata.
Designed against WCAG 2.2 AA principles. Keyboard navigation, semantic structure and colour contrast are part of the design system.
Personal data on DKAM belongs to the individual. Institutions and organisations contribute verified facts about that individual. Recruiters and partners only see what an individual has consented to share, for as long as that consent stands.
Credentials follow the individual across borders without bilateral data-sharing deals.
Institution-issued credentials are time-stamped and bound to a verified individual. Provenance is preserved.
Independent certifications are a stated roadmap milestone, not a current claim. We will publish certifications only when they are actually held.
Security concerns can be reported through the Contact page and are routed to a named DKAM contact.
For investor, institutional or strategic partnership discussions, additional commercial, security and infrastructure detail is shared with named counterparts in the appropriate discussion context. Use the routes below to open that conversation.
Trust enquiries are owned by a named DKAM contact. Use the route that fits your remit. While a role is between holders, the DKAM founding team responds directly.
Investor conversations, strategic partnerships, commercial detail.
hello@dkam.ioThis page is maintained by the DKAM team. It states current platform controls and roadmap intent. It is not an independent certification. Specific commitments are confirmed in writing per institutional pilot.