DKAM & BluckTrust infrastructure
Trust & Privacy

Legal, privacy and compliance

These pages describe how DKAM handles identity, credential and capability data, what controls are in place today, and what is on the compliance roadmap. They are maintained by the DKAM team and updated as the platform matures.

Security

DKAM is built to earn institutional confidence. This page states our public security posture in plain language. Deeper architecture, control mappings and assurance evidence are shared with named counterparts during commercial and institutional discussions.

Holder-centric by design

Sensitive credential material is held on the holder side of each Bluck, not broadly centralised by DKAM. DKAM acts mainly as a trust, verification, permissions, scoring and discovery layer. Where verification is possible from a proof, a hash or a status check, we prefer that over holding the raw document.

  • Layer 1. Holder / Bluck. Holder-facing identity, encrypted credential references and disclosure controls.
  • Layer 2. DKAM coordination. Discovery, trust relationships, scoring, permissions, minimal searchable metadata, consent events.
  • Layer 3. Integrity and proof. Content hashes, issuance anchors, revocation status and append-only event logs.

What we commit to publicly

  • Encrypted transport and storage across the platform.
  • Real authentication with password protection, email verification and one-time codes.
  • Role-scoped access between individuals, organisations, universities and recruiters.
  • Consent-controlled, time-bound access to any personal data.
  • Append-only audit trails for verification, issuance and access events, visible to the individual.
  • Biometric liveness at onboarding.
  • Every sensitive administrative review is logged.

Wallet infrastructure

Each Bluck is wallet-bound. DKAM provisions a wallet-class identifier per holder as a permanent anchor and holds no wallet private key for it. Previously stored key material has been removed. Nothing signs on a holder's behalf, and the wallet layer is designed to accept holder side or institutional signing later, including MPC-secured key management, without changing the underlying records. We will not describe signing custody as live until it is.

Certifications

DKAM's controls are designed against recognised industry baselines. Independent certifications are a stated roadmap milestone. We will not claim a certification we do not hold.

Reporting a security concern

Please use the Contact page and choose the appropriate enquiry type. Security reports are routed to a named DKAM contact.

For investor, institutional or strategic partnership discussions, additional infrastructure and assurance detail is shared in the appropriate discussion context.