Topic starter
06/11/2026 6:37 pm
TL;DR: AI agents are becoming a new interface for customer interactions, which shifts privacy from human-driven workflows to agent-to-agent data exchange, where collection, lineage and task-scoped access must be enforced before personal data spreads across tools, according to Didomi. The governance challenge is no longer consent capture alone, but preserving purpose, permission and revocation as data moves through automated workflows.
Editorial analysis by NHI Mgmt Group, based on content published by Didomi: “Privacy in the age of AI agents: My thoughts for the last stretch of 2026”.
Key questions
Q: How do you limit AI agents to the minimum data they need?
A: Limit AI agents with scoped service identities, tool-level authorisation and filtered data retrieval so they can only read the records needed for the current task.
Q: Why do privacy controls fail when agents handle customer data?
A: Privacy controls fail when the agent’s runtime access is broader than the consented purpose, or when customer data is copied into prompts, logs, caches or downstream tools without fresh enforcement.
Q: How does privacy lineage work in AI workflows?
A: Privacy lineage tracks how personal data moves through an AI workflow, from source to prompt, model input, output, log and downstream system, together with the purpose, consent state and retention rules attached to each use.
Practitioner guidance
- Define agent data scopes by task Map each agent workflow to the smallest usable data set, then block access to unrelated profile fields, history and preferences.
- Attach privacy policy to the data flow Record purpose, consent state, retention expectations and withdrawal handling so downstream systems can enforce the same rules.
- Minimise copied personal data in agent prompts Prevent agents from seeing full customer records when an order reference or delivery status is sufficient for the task.
Bottom line: AI-mediated privacy shifts the core control problem from user interaction to delegated data use across systems.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
06/11/2026 6:41 pm
Agent-mediated privacy is becoming an access-control problem, not just a consent problem. When AI systems intermediate between people and services, privacy decisions move into the execution path. That means the policy question is no longer only whether a person agreed once, but whether the system can keep applying that decision correctly as data is re-used. Organisations that still treat privacy as a front-door checkbox will miss the real control surface.
A few things that frame the scale:
- The agentic AI market is already worth $5 billion and is projected to reach $50 billion by 2030.
A question worth separating out:
Q: What should teams do when an agent no longer needs personal data?
A: Remove the agent’s access token, API key or delegated role immediately, then disable any cached data copies, derived outputs and tool connections that still expose the personal data. Revoke the exposure path across storage, prompts, logs and downstream systems so the agent cannot continue to read or reconstitute the data after the task ends.
👉 Read our full editorial: Privacy governance must move to agent-to-agent data exchange