Desk notes · EU commercial contracts · Position of the week
Sub-processor notice: the thirty-day position
Enterprise customers in the EU ask for prior approval of every sub-processor, and vendors offer a list and a promise to keep it updated. The workable middle is a notice period with a right to object, and the number we hold is thirty days.
Every SaaS product runs on other companies’ services: cloud infrastructure, email, analytics, support tools. Each is a sub-processor under the GDPR, which requires the customer’s authorisation before one is engaged. Customers ask for specific approval of every addition, and that is unworkable: a vendor with two hundred customers cannot seek two hundred consents to change its logging provider. See general versus specific authorisation in the processor guide.
The position
General authorisation for the sub-processors on a published list. Thirty days’ written notice before any addition, by email to a nominated address or through a subscription to the list page. A right to object on reasonable data-protection grounds. If the objection cannot be resolved, the customer may end the affected services without penalty.
Why thirty
Vendors open with fourteen days, which is too short for a customer’s privacy team to assess a new provider. Customers open with sixty, which stops a vendor from switching providers after an outage for two months. Thirty days is long enough to evaluate and short enough to operate, and it is where most negotiated DPAs end up.
Where we move
For regulated customers we allow a longer period for sub-processors that will hold special-category data, and sometimes a short list of named providers that need specific approval. We never move to specific approval for everything: the vendor would break that promise in the first quarter.
Next step
Seen something like this on your own paper?
Send it over. Twenty minutes, marked up, explained.