The questions to ask an AI supplier about client data are the ones that UK GDPR Article 28 and the ICO’s guidance point a practice towards settling in writing before it sends a single file: where the data goes, how long it stays, whether it trains anything, who else touches it, how it is secured, and how a breach reaches you. This article sets them out for partners and managers who are choosing or reviewing an AI tool for accounts work, with the legal source for each.
Why Article 28 frames the conversation
When a practice sends client files to a supplier that processes them on its behalf, the supplier is a processor and the practice, as controller, has duties of its own. Article 28(1) says the controller must use only processors that give sufficient guarantees to put appropriate technical and organisational measures in place. Article 28(3) says the processing must be governed by a contract or other legal act that binds the processor and sets out what it may do. In its worked example of a cloud provider supplying machine learning tools to clients, the ICO treats the clients as controllers and the provider as likely to be a processor. The practice should confirm the roles that apply to its own engagements.
Our guide to client data, the UK GDPR and AI in an accountancy practice places these questions in the wider picture. The ICO’s AI guidance says that when you buy an AI solution from a third party you are required to specify your requirements at the procurement stage, which is where the questions below belong.
Article 28(10) is the reason several questions matter. A processor that infringes the Regulation by determining the purposes and means of processing is treated as a controller for that processing. A supplier that uses client data for its own purposes is outside the role the contract gave it.
Data location and transfers
What to ask
- In which countries are the files stored, processed and backed up, including by any sub-processor?
- Can the practice choose or restrict the location?
- Does support staff outside the UK have access to client content?
- If data leaves the UK, which transfer mechanism does the supplier rely on?
Why it matters
The ICO defines a restricted transfer as a transfer of personal information to a separate organisation located outside the UK, and says that making the information accessible counts as well as sending it. Every restricted transfer needs one of three bases: adequacy regulations, one of the safeguards in Article 46 of the UK GDPR, or one of the exceptions in Article 49. Where you rely on a safeguard, the ICO says you must also complete a transfer risk assessment. A supplier that answers “our cloud is global” has not answered the question.
Checked against the ICO’s international transfers guide, last updated 15 January 2026, on 21 November 2026. The ICO says its guidance is under review because of the Data (Use and Access) Act, so confirm the current text before you rely on it.
Retention and deletion
What to ask
- What does the supplier keep once a review is finished: the uploaded file, extracted text, the output, logs, backups?
- For how long, and who decides?
- Can the practice delete a file, or a client’s whole set, on request, and what does the supplier confirm in writing?
- What happens to everything at the end of the contract?
Why it matters
Article 28(3) requires the contract to say that the processor deletes or returns the personal data when the services end. The practice also has its own retention rules for client files, and a supplier copy that outlasts them creates a second copy to manage. Ask for the deletion position to cover backups and derived data such as embeddings or extracted text, and ask how the supplier would evidence it.
Training on client data
What to ask
- Is any client content, output or feedback used to train, tune or evaluate a model, for the practice or for anyone else?
- Is that off by default, and is the position written into the contract and not only the marketing pages?
- If the supplier says it uses only de-identified data, how does it de-identify, and who checks?
Why it matters
Article 28(3) requires the processor to process personal data only on documented instructions from the controller. Training a general model for the supplier’s own benefit is hard to square with that, and Article 28(10) says a processor that determines the purposes and means of processing is treated as a controller for it. The practice would then have disclosed client data to another controller, which is a different legal position from using a processor. Ask for an unqualified answer and a clause that says it.
Sub-processors
What to ask
- Who are the sub-processors, what does each do, and where is each located?
- Does the supplier rely on a third party for the underlying model or hosting?
- How will the practice be told of a change, and can it object?
Why it matters
Under Article 28(2) a processor must not engage another processor without the controller’s prior specific or general written authorisation. Where the authorisation is general, the processor must inform the controller of intended changes so that the controller has the chance to object. Article 28(4) requires the same data protection obligations to be imposed on the sub-processor by contract, and the initial processor remains fully liable to the controller if the sub-processor fails. The ICO notes that very few organisations build AI systems entirely in-house, so a supply chain is the norm, and a short list is worth asking for.
Security and breach notification
Security: what to ask
- How is client content protected in transit and at rest, and who at the supplier can read it?
- How does the supplier test its controls, and can it show an independent assessment?
- How is a client’s data kept separate from other customers’ data?
- What access does the practice have to audit the supplier or to receive information that demonstrates compliance?
Article 32(1) requires a level of security appropriate to the risk, and lists examples that include pseudonymisation and encryption, the ongoing confidentiality, integrity, availability and resilience of systems, and a process for regularly testing, assessing and evaluating the effectiveness of the measures. Article 28(3) also requires the contract to oblige the processor to help with audits. The ICO says AI systems introduce new kinds of complexity not found in more traditional IT systems, which is a reason to ask about the AI components specifically as well as the hosting.
Breach notification: what to ask
- What does the contract say about telling the practice of a breach, and by when?
- Who at the practice receives the notice, and how is it delivered out of hours?
- What information will the supplier provide so that the practice can assess the breach?
Article 33(2) says the processor must notify the controller without undue delay after becoming aware of a personal data breach. The ICO’s breach guidance says a notifiable breach must be reported to the ICO not later than 72 hours after becoming aware of it, and that a processor must inform the controller without undue delay as soon as it becomes aware. Ask for a contractual notice period that leaves the practice time to act on its own 72 hours.
Recording the answers
A table of answers kept on file supports the supplier review and feeds the risk assessment. A practice could keep it in this form.
| Topic | Supplier’s answer and where it is written | Practice’s view |
|---|---|---|
| Location and transfers | Contract clause and sub-processor list | Accept, or restrict |
| Retention and deletion | Contract clause and deletion confirmation | Accept, or negotiate |
| Training on client data | Contract clause | Accept only if the answer is no |
| Sub-processors | List, notice and objection process | Accept, or object |
| Security and audit | Security schedule and any independent report | Accept, or ask |
| Breach notice | Contract clause and contact route | Accept, or negotiate |
Take the answer from the contract, not from the sales material, and date it, then repeat the review when the supplier changes its terms or its sub-processors, because the assessment is only as current as its latest answer. Our guide to choosing an accounts review tool and testing it sets these questions alongside the questions about the work the tool does.
Responsibility for the accounts stays with the board and the partner, as our guide to professional responsibility for AI-reviewed accounts explains.
Questions practices ask
Does Article 28 apply if the supplier says it is only a software provider?
It applies if the supplier processes personal data on the practice’s behalf, whatever it calls itself. The test is what it does with the data. If it also decides its own purposes for that data, Article 28(10) treats it as a controller for that processing.
Is a standard terms page enough for the contract?
Article 28(3) requires a binding contract that sets out the processing and the controller’s rights, and that covers documented instructions, confidentiality, security, help with data subject rights and audits, and deletion or return of the data. Standard terms can meet it, so read them against the Article. Gaps are for negotiation or for choosing another supplier.
Do we have to tell clients we use an AI tool?
The ICO’s guidance on AI and data protection has a chapter on transparency. Read it for the position on explaining AI processing to the people affected, and then decide what your engagement letter and privacy notice should say.
Who should approve the supplier answers?
The person in the practice who is accountable for data protection, usually with the partner who will rely on the tool. Article 35(2) requires the controller to seek the advice of the data protection officer where one has been designated.
Can we use client files to test a tool before we sign a contract?
Not safely, because sending real files to a supplier is processing and the written terms should be in place first. If you want to test on realistic material, ask the supplier what it can offer under contract, or use files that contain no personal data.
Sources
- UK GDPR, Article 28: processor, legislation.gov.uk, read 21 November 2026
- UK GDPR, Article 32: security of processing, legislation.gov.uk, read 21 November 2026
- UK GDPR, Article 33: notification of a personal data breach, legislation.gov.uk, read 21 November 2026
- UK GDPR, Article 35: data protection impact assessment, legislation.gov.uk, read 21 November 2026
- Personal data breaches: a guide, Information Commissioner’s Office, updated 20 August 2025
- A brief guide to international transfers, Information Commissioner’s Office, updated 15 January 2026
- What are the accountability and governance implications of AI?, Information Commissioner’s Office, updated 15 March 2023
- How should we assess security and data minimisation in AI?, Information Commissioner’s Office, read 21 November 2026