DUBSAR for DPO

Role · DPO

Prepare an AI mission’s data review with the DPO

Before asking a client to review an AI agent’s mission, an integrator needs to explain which data the mission uses and which records it leaves behind. The content sent to the model is only part of the picture: a log, an attachment or an evidence record may retain information that is absent from the final prompt.

The review should produce a practical result: identify missing information, technical changes to prepare and assessments to assign to the appropriate people. This guide provides a record for organising that work with the DPO and the other people involved.

In brief

The question and the useful result.

Question
What should we give the DPO to examine an AI mission’s data, including information retained in logs and evidence?
Useful result
A review record separating observations, assessments and assigned follow-up work, including logs and evidence.

DUBSAR for DPO

Present the facts with their sources and limits

Start with a defined mission: its purpose, the version under review and the operations being examined. Reuse the client’s documents and observations available within the authorised scope. For each item, distinguish what has been observed, what a team or provider has stated and what remains unknown.

“The log contains a contact address” is a technical observation that needs a source and a date. “Keeping this information is justified” is a separate assessment that requires consideration of the context and applicable rules. The review record should keep both available without turning the first into a legal conclusion.

Avoid adding an entire file when a reference and a suitable extract can answer the question. Check that authorised reviewers can still access the referenced material.

DUBSAR for DPO

Example: removed from the prompt, retained in the log

In this illustrative scenario, a mission prepares a reply to a client. The team removes a telephone number before calling the model. The inspected prompt no longer contains the number, but the preparation log retains the original document. A copy of that log has also been attached to an investigation record. This scenario describes neither a validated integration nor a data removal feature available in DUBSAR.

The review starts with three separate observations:

Observation in the scenarioQuestion to assign
The number is absent from the inspected prompt.Which call and version were checked?
The number remains in the preparation log.Why does this copy exist, who can access it and what retention is intended?
A copy of the log appears in the investigation record.Does the review need the whole document, and who can change its content or access permissions?

The integrator can ask the log’s owner to establish its access and retention arrangements, then prepare a logging change if one is agreed. The appropriate people assess the data protection questions separately. A number’s absence from one prompt does not establish what happened to every copy.

DUBSAR for DPO

A portable data review record

This record can be used in the client’s documentation tools without DUBSAR. It is not an automatic product export. Start with the mission reference, the version examined, the review date and the participants.

For each row, add the source, the status of the information and the person responsible for supplying any missing answer.

FieldInformation to gather
PurposeThe intended outcome and the reason for using each set of data.
People affectedThe groups of people to whom the data may relate.
Data categoriesContent, identifiers and information held in source material, exchanges, logs and evidence.
RecipientsThe services and teams intended or actually observed, with any differences to resolve.
Known processing locationsDocumented locations for the processing and copies examined; leave the rest as unknown.
RetentionThe stated or configured period, its starting point and available evidence of its application, for each copy.
Access to evidenceThe people or roles able to read, copy or share the material, and the reason for that access.
Open questionsInformation to obtain, a technical change to consider or a legal assessment to request.
Owner of each answerA named contact, the answer needed, a due date and a reference showing how the question was resolved.

Keep technical observations in one part of the record and advice or decisions in another. Unknown information does not become confirmed when the meeting ends.

DUBSAR for DPO

Review the data held within the evidence

Each piece of evidence should answer a specific question. The request describes the intended outcome; authorisation states what was permitted; an attempt records the operation undertaken. An acknowledgement may establish receipt of a request without confirming the intended effect. For each item, ask which data it contains and why that data needs to remain accessible.

A file reference, a hash or metadata also needs examination. Its format alone cannot establish the absence of personal data. Recital 26 of the EU GDPR distinguishes anonymous information from pseudonymised data that can still identify a person with additional information. This provides a basis for examining possible links in the relevant context. Source: EUR-Lex, Recital 26 and Article 4(1) and (5), consulted on 18 October 2026.

DUBSAR for DPO

Finish the review with assigned follow-up work

Group the next steps into information to obtain, changes to prepare and assessments to request. Give each item a contact, a due date and a condition for closing it. For example: retrieve the log configuration, propose a retention period for review or request an assessment of the intended recipients.

Where the EU GDPR applies, Articles 24 and 38–39 distinguish the controller’s responsibility from the DPO’s advisory and monitoring tasks. Involving the DPO should therefore not be presented as transferring every project decision to them. Source: EUR-Lex, EU GDPR, Articles 24 and 38–39, consulted on 18 October 2026. These are EU references; the applicable legal framework must be assessed for the mission concerned, including where UK activities are involved.

In the client’s record, identify who provides advice, who can decide on a change and who implements it. The record prepares those discussions; it does not by itself establish that processing is compliant.

DUBSAR for DPO

Frequently asked questions

What should we give the DPO when information is still missing?

A dated record separating observations, statements received and unknowns. For each gap, state the information needed and who is responsible for obtaining it. The record can then organise the review without suggesting that its entire scope is already understood.

Can we retain only metadata or a hash?

Examine what they can establish and how they might be linked to other information. Keeping them proves neither anonymisation nor sufficient evidence. The choice should reflect the question to be answered, access, retention and appropriate advice.

Does the record approve the processing?

No. It prepares a review and records its questions, advice and assigned follow-up work. The applicable assessments and decisions must be identified separately, with the people or organisations responsible for them.

DUBSAR for DPO

Where DUBSAR fits

DUBSAR is developing a foundation that connects durable mission state, explicit authorisations, human decisions and execution evidence. Its intended role is to retain useful context about the actions within scope, including when their outcomes remain uncertain. This does not replace a review of the data and evidence the organisation chooses to keep.

Selected workflows have been tested; full B2B integration and validation are still underway. Pilots are not currently open.