Your AI tool is adding a sub-processor: GDPR Article 28(2) change notice and objection sheet with object-by dates for accountants and their SME clients (AI suppliers, SCC Decision 2021/915 Clause 7.7)
What you get: a finished sub-processor change sheet for accountants, tax advisers and bookkeepers whose small business clients receive emails such as "we are updating our list of sub-processors" from their AI tools (chatbots, note-takers, invoice readers, email assistants). One row per notice: type in eleven short answers and the sheet returns the object-by date, the days left, a result (ACCEPT, ASK SUPPLIER, OBJECT, DECIDE, STOP or NOTE ONLY) and a to-do list with the GDPR Article behind each step. Also included: a checklist for reading a notice, a copy-ready question email to the supplier, a copy-ready objection email and a client email. Formulas tested in LibreOffice on nine made-up rows.
Short answer: under GDPR Article 28(2) an AI supplier that processes personal data for your client (a processor) may not bring in another processor without the client's prior specific or general written authorisation. With a general authorisation the supplier must tell the client about any intended addition or replacement, "thereby giving the controller the opportunity to object". The GDPR does not set the notice period; the contract does. The Commission's standard contractual clauses (Implementing Decision (EU) 2021/915, Clause 7.7) leave it as "[SPECIFY TIME PERIOD]". So the client needs to know what its contract says, and to act before the period ends.
Why clients bring these emails to their accountant
- The notices look like spam ("Updates to our subprocessor list") and are often ignored, so the objection window passes unnoticed.
- AI tools change model hosts often, and a new host may sit outside the EU. That is a transfer under GDPR Chapter V (Articles 44 to 46).
- Records and notices go out of date: the client's record of processing must list recipients and third-country transfers (Article 30(1)(d), (e)), and the privacy notice must name recipients or categories of recipients and transfers (Article 13(1)(e), (f)).
- Customer and supplier questionnaires ask "list all sub-processors of your AI tools". The sheet becomes the answer.
Step 1: tab 1, Changes (one row per sub-processor notice)
| Column | What to write | Source |
|---|---|---|
| A | The AI tool (the client's supplier) and the client name | Client's software list |
| B | Name of the new or replacement sub-processor | Supplier notice |
| C | Added or Replacing old one | Art 28(2) |
| D | What it does (hosting, model, support, analytics) | Supplier notice |
| E | Where it processes the data: EU/EEA, Third country or ? | Supplier notice; Art 44 |
| F | Authorisation type in the client's contract (DPA): General, Specific or None found | Art 28(2); SCC Clause 7.7(a) |
| G | Date the notice was received (a date) | Email date |
| H | Notice period in the contract, in days (for example 30) | Contract; SCC Clause 7.7(a) "[SPECIFY TIME PERIOD]" |
| I | Does personal data of the client's customers or staff go to the sub-processor? Y, N or ? | Art 28(1), (4) |
| J | If third country: safeguard named in the notice or DPA: Adequacy, SCC, BCR, None or ? (leave empty for EU/EEA) | Art 45; Art 46(2)(b)-(d) |
| K | Does the supplier confirm the same data protection obligations are in the sub-processor contract? Y, N or ? | Art 28(4); SCC Clause 7.7(b) |
| L | Object by: =IF(OR(G2="",H2=""),"",G2+H2) | Formula |
| M | Days left: =IF(L2="","",L2-Settings!$B$1) (Settings!B1 holds the check date; put =TODAY() there in your copy) | Formula |
| N | Result: =IF(A2="","",IF(F2="None found","STOP: NO AUTHORISATION ON FILE",IF(I2="N","NOTE ONLY: NO PERSONAL DATA",IF(F2="Specific","DECIDE: YOUR WRITTEN YES IS NEEDED",IF(OR(I2="?",E2="?",K2="?",AND(E2="Third country",J2="?")),"ASK SUPPLIER",IF(AND(E2="Third country",J2="None"),"OBJECT: NO TRANSFER SAFEGUARD",IF(K2="N","OBJECT: OBLIGATIONS NOT PASSED DOWN","ACCEPT: UPDATE RECORDS"))))))) | Formula (our working rule) |
| O | Deadline: =IF(OR(N2="",L2=""),"",IF(OR(LEFT(N2,6)="OBJECT",N2="ASK SUPPLIER",LEFT(N2,6)="DECIDE"),IF(M2<0,"LATE BY "&-M2&" DAYS: WRITE TODAY",IF(M2=0,"DUE TODAY","DUE IN "&M2&" DAYS")),"NO DEADLINE")) | Formula |
| P | To-do: =TEXTJOIN("; ",TRUE,IF(N2="STOP: NO AUTHORISATION ON FILE","ask the supplier for its processor terms (DPA) and the sub-processor clause: a processor may not engage another processor without your prior specific or general written authorisation (Art 28(2))",""),IF(LEFT(N2,6)="DECIDE","reply in writing yes or no before the sub-processor starts: specific authorisation needs your prior written authorisation (Art 28(2); SCC Clause 7.7(a) Option 1)",""),IF(N2="ASK SUPPLIER","ask where it processes, what personal data it gets, which Chapter V safeguard applies and whether the same data protection obligations are in its contract (Art 28(4), Art 44, Art 46)",""),IF(N2="OBJECT: NO TRANSFER SAFEGUARD","object in writing before the object-by date: transfer to a third country without adequacy or an Art 46 safeguard (Art 44, 45, 46)",""),IF(N2="OBJECT: OBLIGATIONS NOT PASSED DOWN","object in writing: the same data protection obligations must be imposed on the sub-processor (Art 28(4))",""),IF(AND(E2="Third country",J2="Adequacy",I2<>"N"),"check the country (or US organisation) is covered by a Commission adequacy decision (Art 45)",""),IF(OR(LEFT(N2,6)="ACCEPT",LEFT(N2,6)="DECIDE"),"once accepted: add the recipient to your records (Art 30(1)(d)) and any transfer (Art 30(1)(e)); check the privacy notice lists recipients and transfers (Art 13(1)(e), (f))",""),IF(N2="NOTE ONLY: NO PERSONAL DATA","keep the notice with the contract; re-check if personal data later goes to it",""),IF(I2<>"N","keep the supplier notice and your reply with the contract","")) | Formula |
Copy the formulas into row 2 and fill down. Format column G and L as dates and M as a number. TEXTJOIN works in Excel 2019 or later, Microsoft 365, Google Sheets and LibreOffice. Column N is our working rule for sorting notices quickly, not a legal test: it checks missing authorisation first, then whether personal data is involved, then specific authorisation, open questions, transfer safeguards and the Article 28(4) flow-down.
Example rows (made up) and what the sheet returns at 29 Oct 2026
| Example (made up) | Key answers | Object by | Result | Deadline |
|---|---|---|---|---|
| 1: AI meeting note-taker, new speech-to-text vendor | EU/EEA, general, 30 days, personal data, flow-down Y | 2026-11-19 | ACCEPT: UPDATE RECORDS | NO DEADLINE |
| 2: AI website chatbot, new US model host | Third country, SCC, flow-down Y | 2026-10-24 | ACCEPT: UPDATE RECORDS | NO DEADLINE |
| 3: AI invoice reader, offshore labelling firm | Third country, safeguard None | 2026-11-24 | OBJECT: NO TRANSFER SAFEGUARD | DUE IN 26 DAYS |
| 4: AI email assistant, analytics start-up (notice 25 Sep) | Personal data ?, flow-down ? | 2026-10-25 | ASK SUPPLIER | LATE BY 4 DAYS: WRITE TODAY |
| 5: AI CV screening tool, cloud host | Specific authorisation, 10 days | 2026-11-06 | DECIDE: YOUR WRITTEN YES IS NEEDED | DUE IN 8 DAYS |
| 6: AI translation tool, status page service | No personal data | 2026-11-14 | NOTE ONLY: NO PERSONAL DATA | NO DEADLINE |
| 7: free AI writing app, no DPA found | Authorisation None found | 2026-10-28 | STOP: NO AUTHORISATION ON FILE | NO DEADLINE |
| 8: AI bookkeeping tool, support desk software | Third country, adequacy, flow-down N | 2026-11-04 | OBJECT: OBLIGATIONS NOT PASSED DOWN | DUE IN 6 DAYS |
| 9: AI phone answering, telephony provider | Third country, adequacy, flow-down Y | 2026-11-28 | ACCEPT: UPDATE RECORDS (to-do adds: check the adequacy decision) | NO DEADLINE |
Accepting does not need a reply under a general authorisation; the to-do column still lists the record and notice updates. In row 2 the window has passed, which does not matter for an ACCEPT row; in row 4 it has passed with questions open, so the client should write today and ask the supplier how it handles a late objection under the contract.
Checklist: reading a sub-processor notice
- Is the supplier a processor for the client? It processes personal data on the client's behalf (Article 28(1)). If the tool gets no personal data, there is no Article 28 step (row 6).
- Find the authorisation clause in the DPA or terms: specific (client approves each one) or general (agreed list, client informed of changes). Article 28(3)(d) requires the contract to cover the conditions for engaging another processor. No clause at all: row 7, STOP and ask.
- Note the notice period in the contract. The GDPR sets none; SCC Clause 7.7(a) Option 2 asks for notice "at least [SPECIFY TIME PERIOD] in advance" with "sufficient time to be able to object".
- Where is the data processed? Outside the EU/EEA, Chapter V applies to onward transfers too (Article 44). Look for an adequacy decision (Article 45) or an Article 46 safeguard such as standard data protection clauses or binding corporate rules.
- Same obligations passed down: the supplier must impose the same data protection obligations on the sub-processor and stays fully liable to the client for it (Article 28(4)). Under SCC Clause 7.7(c) the client can ask for a copy of the sub-processor agreement (it may be redacted).
- Update the paperwork: record of processing (Article 30(1)(d), (e)), privacy notice (Article 13(1)(e), (f)), and keep the notice and any reply with the contract.
Related sheets: Article 28 processor agreement (DPA) clause check, international transfer check for US suppliers, Article 30 records of processing and Article 13 privacy notice wording.
Email to the supplier: questions (template)
Subject: Your sub-processor notice of [date]: questions before [object-by date]
Hello,
We received your notice about [sub-processor name]. Under our data processing terms and GDPR Article 28(2) we may object to this change. Before [object-by date] please tell us: (1) what personal data of ours it will process and for what; (2) where it will process it, and if outside the EU/EEA, which safeguard under GDPR Article 45 or 46 applies; (3) that the sub-processor contract imposes the same data protection obligations as our agreement with you (Article 28(4)). Please treat this email as keeping our right to object open until you have answered.
Kind regards, [client name]
Email to the supplier: objection (template)
Subject: Objection to the addition of [sub-processor name]
Hello,
Referring to your notice of [date], we object under GDPR Article 28(2) and [clause number] of our data processing terms to the engagement of [sub-processor name] for our personal data, because [no transfer safeguard was named / the same data protection obligations are not confirmed / other reason]. Please confirm in writing that our personal data will not be processed by it, or tell us the options under our contract.
Kind regards, [client name]
Email to business clients (template)
Subject: Emails from your AI tools about "sub-processors": please forward them to us
Dear [name],
AI tools you use (chatbots, note-takers, invoice readers) regularly send notices that they are adding or replacing "sub-processors". Under GDPR Article 28(2) you can object within the period in your contract, and new sub-processors outside the EU need a transfer safeguard. Please forward any such email to us, with the supplier's data processing terms if you have them. We will log each one, tell you the object-by date and whether to accept, ask questions or object, and update your records of processing.
This is a first sort, not legal advice. Kind regards, [firm]
Keep the supplier list with the AI system record
Record each AI tool, its supplier and the evidence (DPA, notices, replies) in the EURO AI Register free edition. It runs in your browser with no account and no upload, covers your first 10 AI systems and 10 evidence records, the screening questions, duties by role with dates, and a printable Article 4 AI-literacy record.
When a client has more than 10 systems, the EURO AI Register membership starts at $19 a month and adds unlimited systems, rule updates and email help. Neither tool is legal advice or proof of compliance.
Partner programme opening soon
Partner programme opening soon: join the free waitlist. Planned terms are 50% of each referred sale (75% once you have 5+ paying customers), single level, paid through Gumroad only from revenue received.
Limits and open points
Guidance not read: we built this guide from the text of Regulation (EU) 2016/679 (GDPR) and Commission Implementing Decision (EU) 2021/915 on EUR-Lex. We did not read EDPB Guidelines 07/2020 on controller and processor, national authority guidance, or the list of Commission adequacy decisions for this guide; check them alongside this sheet. Open points: the GDPR does not say what happens if the client objects and the supplier goes ahead anyway, or how long "sufficient time" is; that depends on the contract. Treating a notice with no answer as accepted is our reading of a general authorisation, not a rule in the text. Many AI tools use their own standard terms rather than the Commission clauses; read the client's actual terms. The sheet sorts notices; it does not decide legal questions.
Frequently asked questions
Can a business object to a new sub-processor of its AI tool?
Yes, where the contract gives the supplier a general written authorisation: the supplier must inform the business of intended additions or replacements, giving it the opportunity to object (GDPR Article 28(2)). Under a specific authorisation, the supplier needs the business's prior written authorisation for each one.
How long is the notice period for sub-processor changes?
The GDPR does not set one. It is agreed in the contract; the Commission's standard contractual clauses (Implementing Decision (EU) 2021/915, Clause 7.7(a)) leave it as a period to be specified, with sufficient time to object before the sub-processor is engaged.
What if the new sub-processor is outside the EU?
The transfer must meet GDPR Chapter V, including onward transfers (Article 44): an adequacy decision (Article 45) or an appropriate safeguard such as standard data protection clauses or binding corporate rules (Article 46).
Who is responsible if the sub-processor fails?
The supplier must impose the same data protection obligations on the sub-processor and remains fully liable to the business for the sub-processor's performance (GDPR Article 28(4)).
Not legal advice. The sheet helps sort sub-processor notices; it does not decide legal questions. Spotted an error? Write to mininglife7@gmail.com and we correct it.
Sources
- Regulation (EU) 2016/679 (GDPR): Article 13(1)(e)-(f), Article 28(1)-(10), Article 30(1)(d)-(e), Articles 44, 45(1), 46(1)-(2), recitals 81 and 82 — eur-lex.europa.eu, CELEX 32016R0679 (read 29 Oct 2026)
- Commission Implementing Decision (EU) 2021/915 of 4 June 2021 on standard contractual clauses between controllers and processors (OJ L 199, 7.6.2021): Annex, Clause 7.7(a)-(e), Clause 7.8, Annex IV — eur-lex.europa.eu, CELEX 32021D0915 (read 29 Oct 2026)
Unadhi Guides are free, independent explainers. We correct errors as soon as we find them: write to mininglife7@gmail.com.