Back to the subscription dictionary

Data processing agreement

A data processing agreement sets binding terms where a processor handles personal data on a controller’s behalf. Under the GDPR, Article 28 governs this relationship. The agreement must reflect the actual processing and does not by itself prove compliance with every data-protection requirement.

Prepared with AIContent updated

Establish roles for each activity

Consider who determines the purposes and essential means, and whether the supplier acts on the controller’s behalf. Data access alone does not make a supplier a processor. One supplier can have different roles for different activities.

From data flow to agreed oversight

Illustrative assessment of a new hosting or SaaS supplier.

  1. Roles

    Establish who determines purposes

  2. Terms

    Describe instructions, data and safeguards

  3. Chain

    Assess sub-processors and transfers

  4. Oversight

    Review changes and actual performance

An NDA, privacy notice and DPA serve different purposes.

Describe processing and instructions

Terms must cover the subject matter, duration, nature, purpose, data types and categories of data subjects. Address documented instructions, confidentiality, security, assistance with rights and the other relevant Article 28 duties.

The terms can be an identifiable schedule to a wider contract. A general NDA or a statement promising to follow the GDPR does not by itself satisfy Article 28.

Sub-processors and oversight

Sub-processors need prior specific or general written authorisation. With general authorisation, intended changes must be notified so the controller can object under the agreed process. Relevant obligations must flow down the chain.

Provide for evidence and appropriate oversight. Follow-up should reflect risk and changes; there is no general rule that every supplier requires exactly the same annual audit.

Breaches and termination

The agreement must support prompt notification and assistance with personal-data breaches. Address deletion or return at the controller’s choice, subject to lawful retention requirements, including relevant copies and systems.

Other requirements still apply

The controller still needs a lawful basis and appropriate transparency. Special-category data needs additional conditions. Third-country transfers require their own assessment; a DPA is not automatically a sufficient transfer mechanism.

Use an appropriate template, adapted to data flows, countries, purposes and safeguards. Data protection can matter to customers, but a signature guarantees neither security, retention nor ARR growth.

Questions and answers

Does every supplier need a DPA?

No. Establish the role for the actual processing. Article 28 concerns processing on a controller’s behalf; independent and joint controllers need a different assessment.

Is a DPA enough for GDPR compliance?

No. It is one part alongside lawful basis, transparency, security, rights and any transfer requirements.

When should the agreement be reviewed?

Review relevant changes to processing, systems, countries, safeguards or sub-processors and as part of risk-based oversight. Compare the terms with actual operations.

Sources and documentation

We update our content regularly and do our best to keep it accurate. If you find an error or think something is missing, please tell us. We are always looking for ways to improve the content.

Found an error? Let us know