§ InsightsNo. 311

Privacy notice for AI tools: what to tell clients and their staff

An AI supplier is a new recipient of client data. What Articles 13 and 14 require your privacy notice to say, and when client staff must be told.

Two accountants at a meeting table discussing client files and their privacy notice for AI tools

This article is stated as at 22 November 2026. The ICO's guidance on the right to be informed and on AI is under review following the Data (Use and Access) Act 2025, and its guidance on automated decision making is still in draft, so the detail may change. Take advice on your own circumstances before acting.

If you pass client or client staff data to an AI supplier, Articles 13 and 14 of the UK GDPR require your privacy notice to cover that AI processing. It has to name the supplier or describe its category, state any transfer outside the UK, and reach people before the processing starts. Data that clients send you about their staff and customers falls under Article 14, which sets a one month outer limit. Notices drafted before 19 June 2026 also need to mention the new right to complain to the practice.

Does our privacy notice need to change when we start using an AI tool?

Usually, yes. A privacy notice must list the recipients or categories of recipients of personal data, and the ICO’s guidance confirms that recipients include processors acting on your behalf. An AI supplier that receives client files is a new recipient, so a notice written before you appointed it is incomplete, even if the purpose of the work (preparing and reviewing accounts, running payroll) has not changed.

If you intend to use data for a purpose other than the one it was collected for, Articles 13(3) and 14(4) require you to tell people before that further processing begins. The ICO also says you must bring any new use of someone’s data to their attention before you start the processing. Either way, settle the supplier contract, update the notice, tell clients and ask them to tell their staff, and only then send data to the tool.

Whether the tool fits the purposes and lawful basis you already rely on is a separate question, set out in our note on the lawful basis for AI review; the contract, security and record keeping are covered in our guide to client data and UK GDPR.

What Articles 13 and 14 require a privacy notice to say

Article 13 applies to data you collect from the person it is about: a sole trader client, a director, a landlord sending you rental figures. Article 14 applies to data you get from someone else, and in a practice that is a large share of every file: the client’s employees on the payroll, and the customers and suppliers named in the ledgers. The full list is in Article 14 of the UK GDPR and its Article 13 counterpart. The items an AI supplier touches are these.

Requirement (UK GDPR, UK wide) Article 13 Article 14 What to check for an AI supplier
Purposes and legal basis 13(1)(c) 14(1)(c) The tool’s use fits the stated purposes
Legitimate interests, if relied on 13(1)(d) 14(2)(b) The interest is described in plain terms
Categories of personal data Not required 14(1)(d) Payroll, ledger and contact data sent to the supplier
Recipients or categories of recipients 13(1)(e) 14(1)(e) The supplier, and how its sub processors are covered
Transfers outside the UK 13(1)(f) 14(1)(f) Where the supplier processes data, and the safeguard relied on
Storage period or criteria 13(2)(a) 14(2)(a) The supplier’s retention and deletion terms
Right to complain to the controller 13(2)(ca) 14(2)(da) In force from 19 June 2026
Right to complain to the Information Commission 13(2)(d) 14(2)(e) Wording amended from 30 September 2026
Source of the data Not required 14(2)(f) The client
Automated decision making 13(2)(f) 14(2)(g) Only for solely automated significant decisions (see below)

Article 12 adds that the information must be concise, transparent, intelligible and easily accessible, in clear and plain language. A short paragraph saying in ordinary words what the AI supplier does with a client’s figures will serve clients better than a page of legal drafting.

Should we name the AI supplier or describe a category?

The ICO says you can give either the names of recipients or the categories they fall within. Its test is to choose whichever is most meaningful and useful for individuals. “Technology providers” is a category in name only, because it covers your email host as much as a tool that reads a full set of accounts. A description such as “a specialist provider of AI review of accounts, acting as our processor” tells a client what actually happens to their figures.

Naming the supplier is clearer but needs upkeep. Under Article 28(2), a processor working under a general written authorisation must tell you about intended changes to its sub processors and give you the chance to object, and that notice from the supplier is your prompt to review the privacy notice. If the supplier or any of its sub processors handles data outside the UK, the notice must also say so and state the basis for the transfer.

Check the supplier’s role before you describe it. The ICO’s AI guidance says the provider of a tool that customers use is likely to be a processor. A provider that develops its own models using the data, though, is likely to be a controller for that part of the processing, and roles follow the facts whatever the contract calls them.

The notice and the Article 28 contract should tell the same story. The contract must confine the supplier to your documented instructions, control its sub processors, require it to delete or return data at the end, and allow audits. Our list of questions to ask an AI supplier covers what to get in writing before you update the notice.

Client staff and customers: when the Article 14 deadlines run

Article 14(3) sets three outer limits. The information must be given within a reasonable period and at the latest within one month of obtaining the data, by the first communication at the latest if you use the data to contact the person, and at the latest on first disclosure if you plan to disclose it to another recipient. For client staff whose payroll data you already hold, the first upload to an AI supplier is that disclosure, so their information needs to be in place before that upload.

Practices rarely deal with these people directly, so the practical route is through the client. One approach is a clause in the engagement letter asking the client to point its staff to your notice, together with a sentence the client can add to its own employee privacy information. For clients themselves, the engagement letter and onboarding papers are the natural places, and our article on telling clients you use AI suggests how to put it.

Neither of the two tempting exceptions in the restructured Article 14(5) is safe to lean on.

  • Disproportionate effort, Article 14(5)(e). The ICO treats it as the exception. You must show that the effort is not warranted by the impact on the people concerned, you must still publish the information, and you should carry out a DPIA. Having no direct contact with client staff is unlikely to be enough when the client can pass the message on easily. If you are weighing it, start with our note on when a practice needs a DPIA.
  • Professional secrecy, Article 14(5)(d). This covers confidentiality regulated by domestic law, including a statutory obligation of secrecy. We have seen nothing that settles whether an accountant’s duty of confidentiality qualifies, so we would not build a notice on it.

Is an AI review tool automated decision making?

The disclosure in Articles 13(2)(f) and 14(2)(g) is about automated decisions that are subject to the Article 22C safeguards. Since 5 February 2026, Article 22A has defined a decision as based solely on automated processing if there is no meaningful human involvement in taking it. A decision is significant if it has a legal effect on the person, or a similarly significant effect.

Take a tool that reads a set of accounts and raises review points, which a qualified reviewer then accepts or rejects. On that test the tool takes no decision, because the reviewer decides and the partner signs. Those decisions are also mostly about a company’s accounts rather than significant decisions about an individual. For most review tools, then, the disclosure is not triggered, and calling the tool automated decision making would mislead clients about how their work is handled. The ICO has not said this directly, so record your reasoning on file.

That reasoning only holds if the human involvement is real. The ICO’s draft guidance on automated decision making, consulted on from 31 March to 29 May 2026 and not yet final, describes meaningful involvement as active, by someone with the discretion and authority to change the outcome, before the decision is applied, and it says that ad hoc spot checks are not enough. A reviewer who clears flags without reading them is the weak point, which is why it pays to evidence human review of AI output.

If a tool genuinely took a significant decision about a person with no meaningful human involvement, the notice would need to say so, with meaningful information about the logic and likely consequences, and the Article 22C safeguards would apply. Separately, the ICO says that where AI creates new data about people that they would not reasonably expect, you must tell them within a reasonable period and within a month at the latest.

What notices drafted before the 2026 changes are likely to miss

The Data (Use and Access) Act 2025 changed the text of both articles during 2026, so a notice drafted before 30 September 2026 needs checking even if you never adopt an AI tool.

  • Right to complain to the practice. From 19 June 2026, the notice must mention the right to complain to the controller under section 164A of the Data Protection Act 2018, which also requires you to acknowledge a complaint within the period of 30 days beginning with the day you receive it. The ICO’s complaints guidance adds that people must be told they can also complain to the ICO.
  • The regulator’s name. From 30 September 2026, Articles 13(2)(d) and 14(2)(e) refer to the right to complain to the Information Commission.
  • Automated decisions. From 5 February 2026, the old Article 22 was replaced by Articles 22A to 22D, and the Article 14(5) exceptions were restructured, so a notice that cites the old article numbers is out of date.

Key dates

Date (UK wide) What changed
5 February 2026 Data (Use and Access) Act 2025 amendments to Articles 13 and 14 in force; Articles 22A to 22D replace Article 22
31 March 2026 to 29 May 2026 ICO consultation on draft guidance on automated decision making
19 June 2026 Section 164A complaints to controllers in force; notices must mention the right to complain to the controller
30 September 2026 Articles 13 and 14 refer to the Information Commission

Questions practices ask

Does the AI supplier have to give its own privacy notice to our clients?

Where the supplier acts only on your instructions as a processor, the duty sits with your practice as controller, so your notice has to cover the supplier. If it uses the data for purposes of its own, such as developing its models, the ICO says it is likely to be a controller for that part, and your notice should say plainly that the supplier uses the data for its own purposes. Check the contract before you rely on calling it your processor.

What if the AI supplier uses our client data to train its own models?

The ICO's AI guidance says a provider that develops its own models using customer data is likely to be a controller for that part of the processing, whatever the contract calls it. Article 28 already requires the processor contract to confine the supplier to your documented instructions, so check whether training on client data is permitted and, if it is, either have it removed or say so in your notice.

Is putting the updated privacy notice on our website enough?

No. The ICO says publishing privacy information on a website is not enough by itself, and you must take active steps to make people aware of it. For clients, a short note with the engagement letter or onboarding papers is a natural route. For client staff, ask the client to point them to your notice, for example alongside its own employee privacy information.

Do we need to tell our clients' employees that their payroll data goes through an AI tool?

Yes, if their payroll data reaches the AI supplier. Those employees are entitled to Article 14 information, including the recipients or categories of recipients, and it must reach them within a month at the latest and no later than the first disclosure to the supplier. Because practices rarely deal with them directly, the practical route is through the client, and you should not assume the disproportionate effort exception applies.

Sources

Part of the guide: Client data, UK GDPR and AI tools in an accountancy practice