Data protection and cyber security

Data processing agreements with suppliers

The Article 28 clauses a law firm needs with IT, cloud, telephony and outsourced suppliers, how to review a supplier's terms and the red flags to look for.

Ava research teamPublished 7 min read

On this page
  1. Your suppliers hold more of your clients' data than you do
  2. Controller or processor?
  3. What Article 28 requires
  4. What a law firm should add
  5. AI tools need the same discipline
  6. Reviewing a supplier in six steps
  7. Keeping the supplier register alive
  8. Red flags
  9. Frequently asked questions
  10. References

Key takeaways

  • Use only processors that give sufficient guarantees, and put the eight Article 28(3) terms in writing[1].
  • Only 15% of businesses reviewed the cyber risks posed by their immediate suppliers, and 6% their wider supply chain[2].
  • Law firms need more than the statutory minimum: confidentiality and privilege, fast breach notice, data location, no reuse for training and a usable exit.
  • The SRA expects firms to remain accountable for AI outputs, including errors by a third-party chatbot[3], so contracts must support real oversight.
  • Keep a supplier register with role, data, location, contract date and review date for every supplier that touches client data.

Your suppliers hold more of your clients' data than you do

A modern firm's client data lives mostly in other people's systems: cloud email, case and document management, practice accounting, telephony and call recording, e-signature, identity verification, outsourced typing, archive storage, confidential waste and the managed IT provider who can reach all of them. Professional, scientific and technical businesses are more likely to access AI by buying external software or ready-to-use services than through free tools[4], and 46% of businesses using or planning AI use it, or plan to, for customer service[5]. Every one of those relationships is a data protection relationship.

Supplier risk is also where oversight is thinnest. The Cyber Security Breaches Survey 2025/2026 found that only 15% of businesses had reviewed the risks posed by their immediate suppliers and 6% their wider supply chain, with micro businesses lowest at 12%[2].

Businesses that reviewed risks from immediate suppliersCyber Security Breaches Survey 2025/2026. Across all businesses the figure was 15%.
Businesses that reviewed risks from immediate suppliersBar chart. Micro businesses: 12%; Small businesses: 22%; Medium businesses: 30%; Large businesses: 48%.Micro businessesMicro businesses: 12%12%Small businessesSmall businesses: 22%22%Medium businessesMedium businesses: 30%30%Large businessesLarge businesses: 48%48%Businesses that reviewed risks from immediate suppliersBar chart. Micro businesses: 12%; Small businesses: 22%; Medium businesses: 30%; Large businesses: 48%.Micro businessesMicro businesses: 12%12%Small businessesSmall businesses: 22%22%Medium businessesMedium businesses: 30%30%Large businessesLarge businesses: 48%48%

Source: GOV.UK (DSIT and Home Office), 2026[2]

Show the data
ItemValue
Micro businesses12%
Small businesses22%
Medium businesses30%
Large businesses48%

Controller or processor?

Article 28 applies when a supplier processes personal data on your behalf and under your instructions: a processor. Some suppliers are controllers in their own right, because they decide why data is used. The label in the supplier's own terms is not decisive; what they actually do with the data is.

Typical roles; confirm each against the actual arrangement.
SupplierUsual roleWhy
Cloud email and document storageProcessorStores and handles data on your instructions
Case management software (hosted)ProcessorHosts your matter data; you decide its use
Managed IT supportProcessorAccesses systems to support you
Outsourced typing or answering serviceProcessorHandles client information on your behalf
Identity verification providerOften joint or independent controller for some dataMay use results for its own fraud prevention
Barristers, experts, process serversIndependent controllersExercise their own professional judgement
Banks and HM Land RegistryIndependent controllersAct under their own legal duties

What Article 28 requires

You must use only processors that provide sufficient guarantees of appropriate technical and organisational measures, and a processor must not engage a sub-processor without your prior specific or general written authorisation; under a general authorisation it must tell you about changes so you can object[1]. The contract must then require the processor to[1]:

  1. Process only on your documented instructions, including on international transfers, unless the law requires otherwise.
  2. Ensure its staff are bound by confidentiality.
  3. Take the security measures required by Article 32.
  4. Follow the rules on engaging sub-processors.
  5. Help you respond to people exercising their rights.
  6. Help you with security, breach notification, impact assessments and prior consultation.
  7. Delete or return all personal data at the end of the service, at your choice.
  8. Make available the information you need to show compliance, and allow audits and inspections.

Many suppliers publish a standard data processing addendum that covers these points. Your job is to check it rather than assume it, and to add what a law firm needs on top.

What a law firm should add

  • Confidentiality and privilege. A clause recognising that the data includes privileged and confidential client information, and that the supplier will not disclose it, including to authorities, without telling you first where the law allows.
  • Breach notice in hours, not days. Without undue delay is too vague when your own deadline to notify the regulator is measured in hours. Ask for notice within 24 hours of the supplier becoming aware, with updates as facts emerge.
  • Data location. A list of countries where data is stored or accessed, including support teams, and notice before that changes.
  • No secondary use. A prohibition on using your data to train models, build benchmarks or improve the supplier's services for others, unless you have agreed it.
  • Exit in a usable format. Return of data in a standard format, within a set period, at no or capped cost, followed by certified deletion.
  • Regulatory cooperation. Cooperation with the SRA and the data protection regulator, and with your insurers, in any investigation.
  • Staff vetting and access logging for anyone who can see client data.
  • Evidence of security, such as Cyber Essentials Plus or ISO 27001 certification, and a commitment to keep it current.

AI tools need the same discipline

Tools that summarise calls, draft letters, answer enquiries or review documents are processors like any other, but they raise particular questions about where data goes and whether it is reused. The SRA has said firms remain responsible and accountable for outputs from AI they use, including errors in advice given by a third-party chatbot[3]. A contract that gives you no visibility of how the tool behaves, no audit trail and no control over reuse makes that accountability hard to exercise.

If you are assessing an AI Employee such as Ava for answering enquiries, ask exactly what you would ask any telephony or intake supplier: where call recordings and notes are stored, who can access them, whether they are used to train models, how quickly you will hear about an incident and how data is returned when the contract ends. Then carry out a data protection impact assessment before switching it on.

Reviewing a supplier in six steps

  1. Map the data

    Write down what client and staff data the supplier will see, whose it is, and whether it includes special category or criminal offence data.

  2. Confirm the role

    Decide whether the supplier is a processor, a controller or both for different data, and record why.

  3. Read the terms against Article 28

    Tick off each of the eight required terms in the supplier's addendum. Note anything missing or qualified.

  4. Check location and sub-processors

    Obtain the sub-processor list and the countries involved, and check the transfer safeguard for each.

  5. Negotiate the law firm additions

    Prioritise breach notice, no secondary use and exit. Smaller suppliers often accept these; large platforms may offer configuration options instead.

  6. Record and diarise

    Add the supplier to your register with the contract date, the data involved and a review date, normally annually or on renewal.

Keeping the supplier register alive

Signing a good agreement is the start, not the end. Suppliers change ownership, move hosting, add sub-processors and suffer incidents of their own. A register that is updated only when someone remembers will be out of date when you need it most, typically in the first hours of an incident when you are trying to work out who holds what.

For each supplier that touches personal data, record:

  • The service, the internal owner and the teams that use it.
  • The categories of data and people involved, flagging special category and criminal offence data.
  • The supplier's role: processor, controller or joint controller.
  • Where the data is stored and accessed from, and the transfer safeguard relied on.
  • The contract and data processing terms in force, with dates and a link to the signed copy.
  • Security evidence held, such as certification and its expiry date.
  • The supplier's incident contact and your agreed breach notice period.
  • The next review date and the exit plan.

Review the register at least once a year with the partners, and in between whenever a supplier announces changed terms, a merger or a security incident. Ask suppliers that hold the most sensitive data to confirm annually, in writing, that their sub-processor list and data locations are unchanged. A two-line email that costs them nothing tells you a great deal about how seriously they take the relationship.

Finally, rehearse an exit. Ask your case management or document supplier for a test export of a closed matter. If the data comes back incomplete or unusable, you have learned something far more valuable than any clause can tell you.

Red flags

  1. The supplier says it is a controller for your client data because it improves its own service with it.
  2. Breach notice is limited to commercially reasonable efforts with no time limit.
  3. Sub-processors can be changed without notice or any right to object.
  4. Data is deleted immediately at termination with no return period.
  5. Audit rights are replaced entirely by a marketing summary of security.
  6. Terms can be changed unilaterally by updating a web page.

Example: a fictional firm moving to a new cloud telephony provider finds that the standard terms allow call recordings to be used to improve speech recognition across the supplier's customer base. The firm asks for that use to be switched off for its account, obtains written confirmation, adds a 24-hour breach notice clause and records the supplier's two overseas support locations and the safeguard relied on for each.

For suppliers that store or access data abroad, see international data transfers and cloud software.

Frequently asked questions

Do we need a separate data processing agreement if the supplier's terms already include one?

Not necessarily. A data processing addendum incorporated into the main terms is enough if it contains the Article 28 terms. Check it, record that you have, and negotiate any law-firm additions you need.

Is our barrister a processor?

No. Counsel acts as an independent controller, exercising their own professional judgement under their own regulatory duties, so Article 28 does not apply.

What if a large platform will not negotiate?

Use the configuration and enterprise options available, such as data location settings and disabling data use for product improvement, document your assessment, and decide whether the remaining risk is acceptable.

How often should we review supplier contracts?

At least at renewal, and whenever the supplier changes its terms, sub-processors or data locations, or reports a significant incident.

References

  1. legislation.gov.uk (The National Archives) (2016). UK GDPR Article 28: Processor (opens in a new tab) ↑

  2. GOV.UK (DSIT and Home Office) (2026). Cyber security breaches survey 2025/2026 (opens in a new tab) ↑

  3. Solicitors Regulation Authority (2023). Risk Outlook report: The use of artificial intelligence in the legal market (opens in a new tab) ↑

  4. Office for National Statistics (2026). Artificial intelligence in UK businesses: 2023 to 2026 (opens in a new tab) ↑

  5. Department for Science, Innovation and Technology (GOV.UK) (2026). Artificial Intelligence Adoption Research (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo