Identity resolution: what privacy and IAM teams need to fix

TL;DR: Identity resolution only works safely when linking identifiers across systems is governed by consent, jurisdiction, and rights workflows, according to Transcend. Without that layer, organisations risk incomplete deletion, stale opt-outs, and AI training on data they are not entitled to use.

Editorial analysis by NHI Mgmt Group, based on content published by Transcend: “Identity resolution for enterprises: A privacy-safe guide”.

Key questions

Q: How should organisations govern digital identity when AI is part of the service model?

A: They should treat identity assurance, access control, and AI oversight as one governance chain.

Q: Why do deletion and opt-out requests fail in fragmented enterprise data estates?

A: They fail when the request is recorded in one system but not propagated to every downstream system that reuses the person's identifiers.

Q: When should privacy teams prioritise identity governance over broader data cleanup?

A: When rights requests, AI training, or customer profiling depend on knowing exactly which records belong to which person.

Practitioner guidance

• Define identity resolution as a governed workflow Document which identifiers may be linked, under what consent basis, and in which jurisdictions the linkage is permitted.
• Propagate opt-outs and deletions across every system Test whether preference changes, suppression flags, and erasure requests reach CDPs, CRMs, warehouses, SaaS tools, and AI pipelines without manual reconciliation.
• Audit identity mappings for stale or conflicting records Look for duplicate profiles, outdated joins, and unresolved identifiers that can cause false matches or incomplete rights handling.

Bottom line: Identity resolution creates governance risk when linkage decisions ignore consent, jurisdiction, and purpose limitations.

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →