What is a sub-processor, and why should a small practice care?

You chose your software. You did not choose the companies your software chose.

Every online tool leans on others: one to rent the servers, one to send the emails, one to answer support tickets, lately one to run the AI features. When those companies handle personal data that you put in, the GDPR calls your vendor a processor and the companies behind it sub-processors.

The law does not leave this to the vendor's taste. Under Article 28 a processor may not bring in another processor without the written authorisation of its customer, meaning you. In practice almost nobody is asked one by one. You gave a general authorisation when you accepted the contract, and for that case the law adds a condition: the vendor must tell you about intended changes, adding or replacing a sub-processor, so that you have the opportunity to object.

That is a real right, and it has a weakness you can see from here. It runs on notice. The vendor publishes a list somewhere on its website and promises to announce changes, often with a window of some weeks. If the announcement goes to an address nobody reads, the window closes with nobody standing at it.

For a five-person practice the list is worth ten minutes a few times a year. You are looking for three kinds of change. A new company that will see client data. A company in a country that was not on the list before. And a new purpose, which these days often means an AI provider has arrived.

Objecting does not always get you what you want. Often the honest outcome of an objection is that you leave. But a practice that knows the list changed can decide. A practice that does not know has had the decision made for it, quietly, by a web page.

Last checked 16 November 2026. Information, not legal advice.

SOURCES

Noise of Now reads the small print of the tools on a list like yours. The Tuesday letter is free.