Start with sources. A data protection officer needs to know exactly what each agent may read, where each fact comes from, how read permissions are scoped and reviewed, how data subject requests reach the agent’s record, and which decisions about people must stay with a person. Agents make these questions sharper, and the record makes them answerable.
Which sources may an agent read?
Only those named in its brief. That list is the DPO’s first document. For each source, the DPO should know the categories of personal data, the purpose, and the lawful basis under GDPR Article 6 or its local equivalent.
Every fact reaching a governed agent arrives stamped with where it came from:
| Provenance | Example | Data protection angle |
|---|---|---|
| Sealed | The core system of record | Accuracy rests with the system owner |
| Signed | A verified issuer or counterparty | Check the sharing basis with that party |
| Declared | What a customer or employee said | Unverified; treat with care in decisions |
| External | An emailed attachment, a web page | May contain third-party data; minimise |
Provenance helps with the accuracy principle in Article 5. An agent that knows a fact is only declared will not treat it as verified, and a reviewer can see that too.
How should read permissions be scoped?
Narrowly, per capability. An agent that answers order queries does not need payment card data or health notes. An agent that drafts HR letters does not need the whole personnel file.
The DPO should ask for each agent’s read scope in writing and review it whenever the agent gains a capability or depth. Depth runs from 1 (read) through 2 (draft), 3 (execute routine work within bounds), 4 (move money or take hard-to-undo actions) to 5 (coordinate other agents). Even at depth 1, reading personal data is processing, so minimisation applies from the start.
It also matters what the agent does not do with the data. With a governed approach, the business’s data is not used to retrain model weights; the agent is qualified through its brief, sources, bounds and certification. The DPO should confirm that in the contract and in the records of processing under Article 30.
How do data subject requests work with agents?
The record helps. Every verdict an agent produces is filed in an append-only record, with the facts it used and their sources. When a person asks what data was used about them, or how a decision was reached, the DPO can retrieve the relevant entries.
Two points need planning. First, the record is append-only, so erasure requests need a defined approach agreed with legal: what is retained as evidence of decisions, for how long, and how personal data within it is handled. Second, where an agent took part in a decision with legal or similarly significant effect, Article 22 rights may apply, including the right to human involvement. Design so that such decisions are held for a person.
When is an impact assessment needed?
Often. Agents that process personal data at scale, make or prepare decisions about people, or use new technology are likely to meet the threshold for a data protection impact assessment under Article 35. Under the EU AI Act, certain deployers of high-risk systems also need a fundamental rights impact assessment. The DPO should be involved before certification, not after go-live.
Who should the DPO work with?
The chief risk officer, who sees the same agents through limits and certification; see what a chief risk officer needs to know. Compliance, who test red lines; see the compliance team’s view. And the agent owners who write each brief. For the role itself, read what a data protection officer is.
Local law adds detail. In Nigeria, for instance, the Nigeria Data Protection Act 2023 and the Nigeria Data Protection Commission set the frame; see the Nigeria Data Protection Act and AI agents and what it means for training staff who use agents. The broader view by role is in AI agent skills by role.
What does the DPO need staff to know?
That reviewers see personal data in held items and must treat it accordingly. That a customer’s statement is declared, not proven. That external content can carry other people’s data. Staff who review agent work are processing personal data, and their training should say so.
Where the Academy fits
The Foundations track of Pryme Intelligence Academy includes a module on ownership, data and trust, and takes about four hours. Reviewers who handle personal data in held items daily should take the Operator track, whose module tests are set in their own industry and role.
Questions people ask
Is the agent a processor or part of the controller?
The business deploying the agent remains the controller for its processing. The platform provider’s role should be set out in the contract.
Can an agent answer a subject access request?
It can draft the response and gather data at depth 2. A person should check and send it.
Should agents read special category data?
Only where the purpose and lawful basis clearly require it, with tight read scope and extra review.