Blog – Digital Signing, eID & Compliance | Addo Sign

Subprocessors: GDPR Requirements and Agreements | Addo Sign

Written by Esben Emborg | 27. jul. 2026 01.45.00

When a company uses an external provider for digital signing or archiving, it becomes part of a chain of data processors, in which a sub-processor often plays a central role. To comply with the GDPR, it is essential to understand who is responsible, what agreements must be in place, and how documentation such as audit trails ensures traceability throughout the entire chain. The concept may seem technical, but it applies to any organization that processes personal data through third-party tools—from HR systems to signing platforms.

Roles in the data processing chain: data controller, data processor, and sub-processor

A data controller determines the purposes and means of processing personal data. A data processor carries out the processing on behalf of the data controller—for example, a vendor that hosts and signs your documents. When the data processor itself delegates part of the task to a third party—such as for hosting, email distribution, or signing infrastructure—that third party is called a subprocessor. The chain may consist of several links, but the original data processor retains full responsibility toward the data controller. This means that responsibility is not diluted simply because tasks are delegated.

Typical examples of sub-processors in a signing solution

Sub-processors are involved in many aspects of modern IT service delivery. These may include cloud and hosting providers that store documents, providers of eID validation, SMS and email services for notifications, or providers of storage and backup. In a signing platform, it is not uncommon for infrastructure, messaging, and identification to be handled by different subcontractors. When evaluating a solution, you should therefore always request an up-to-date list of subprocessors so that you know where your data is actually processed and stored—and whether the processing takes place within the EU/EEA.

Requirements for the subprocessor agreement under Article 28 of the GDPR

Article 28 of the GDPR requires that a written agreement be entered into at every stage of the chain. The subprocessor must be subject to the same data protection obligations that the processor has undertaken toward the data controller. Among other things, the agreement must describe the nature and purpose of the processing, its duration, the categories of data and data subjects, as well as the technical and organizational security measures. It must also specify assistance regarding access, erasure, and the handling of data breaches. GDPR requirements and e-signature regulations are closely linked to the need to document consent and data processing at every stage, so that you can demonstrate compliance if requested by the supervisory authority.

Approval, Notification, and Right to Object Regarding New Subprocessors

A data processor may only engage a subprocessor with the data controller’s approval. The approval may be specific, where each subprocessor is approved individually, or general, where broad permission is granted in advance. In the case of general approval, the data controller must be notified of planned replacements or additions so that there is a genuine opportunity to object before the change takes effect. It is therefore good practice to ensure that the supplier has a clear notification process and that your own approach to regulatory compliance describes how you internally evaluate and, if necessary, reject a new subprocessor.

Documentation, Auditing, and Liability if Something Goes Wrong

Liability cannot be waived by delegating tasks. If a subprocessor causes a breach, the data processor remains liable to the data controller, who in turn is liable to the data subjects. Therefore, independent documentation is crucial. An audit in accordance with ISAE 3000 provides a third-party-verified picture of whether controls are being followed in practice, and a complete audit trail shows who processed which data and when. The same documentation requirements apply when you collect information via a digital consent form or share sensitive files through secure file sharing, where traceability must be demonstrated upon request.

Checklist Before Choosing a Provider with Subprocessors

Before signing, you should request the full list of subprocessors, the geographic location of data processing, and documentation of security measures. Ask how changes to subprocessors are notified, what procedures apply in the event of a data breach, and whether operations are subject to independent audits. Also assess whether transfers outside the EU are covered by a valid legal basis for transfer. A well-documented and clearly defined setup makes it significantly easier for your company to fulfill its own responsibilities as a data controller or data processor—and it reduces the risk that a weak subcontractor will become your problem.

How to Keep Track of the Chain on an Ongoing Basis

Sub-processors are not a one-time exercise but something that requires ongoing maintenance, as suppliers change sub-processors over time. Therefore, maintain an up-to-date list of your data processors and their subprocessors, and link each one to the processing activity they support. Review the list at least once a year and whenever a vendor notifies you of a change, so you can respond within the objection deadline. This way, you’ll maintain an overview of where your personal data is actually being processed, and you’ll be able to quickly document the chain of responsibility if a data subject or a supervisory authority requests access.