Topic starter
25/10/2026 10:59 am
TL;DR: Digital identity systems need privacy by design because centralized identity provider models can expose transaction data, enable passive tracking and weaken trust, while decentralized wallets, selective disclosure and minimal retention reduce unnecessary visibility, according to Procivis. The governance test is no longer whether identity can authenticate users, but whether it can do so without creating surveillance, disclosure or retention risk by default.
Editorial analysis by NHI Mgmt Group, based on content published by Procivis: “Procivis One”.
Key questions
Q: How should organisations design digital identity without creating surveillance risk?
A: Organisations should minimise the amount of identity data exposed at each step, use selective disclosure where possible, and keep trust anchors narrow and auditable.
Q: When does selective disclosure become more than a privacy feature?
A: It becomes essential when the same credential can be reused across services or contexts.
Q: What breaks when identity revocation is designed with hidden back channels?
A: Hidden revocation checks can reintroduce linkability even in otherwise decentralised systems.
Practitioner guidance
- Define the minimum disclosure set Map each digital identity transaction to the smallest attribute set needed for the verifier to complete the check.
- Review revocation for hidden correlation Inspect revocation, wallet attestation and status-check workflows for issuer recontact, tracking identifiers or other back-channel dependencies that break unlinkability.
- Set retention limits for identity data Apply explicit retention schedules to identity claims, logs and credential metadata so systems do not preserve more behavioural context than the transaction requires.
Bottom line: Centralized identity provider models can undermine digital identity trust because they create an inherent opportunity for transaction-level tracking.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
27/10/2026 7:16 pm
Privacy by design is now a trust control, not a preference. In digital identity, the privacy model determines whether users will accept the system at all. If every verification creates a visible trail back to the issuer, the architecture itself becomes a surveillance mechanism, even when the implementation is technically correct. Practitioners should treat privacy as a prerequisite for durable identity governance, not a post-launch enhancement.
A question worth separating out:
Q: What governance checks should teams apply to privacy by design in digital identity?
A: Teams should test for data minimisation, retention discipline, explicit disclosure boundaries and correlation risk across the full credential lifecycle. Privacy by design is working only when the architecture prevents unnecessary identity leakage by default and does not rely on user behaviour to compensate for poor system design.
👉 Read our full editorial: Privacy by design now shapes digital identity trust and governance