How to Review a Data Processing Agreement

Harper James advises businesses on commercial contracts and data protection obligations under the laws of England and Wales. A Data Processing Agreement (DPA) sets out how a processor handles personal data for a controller and should be reviewed alongside the main services agreement, privacy notice and technical arrangements.

Confirm the roles and scope

Start by identifying the parties and confirming whether each party is acting as a controller, processor or sub-processor. The DPA should describe the processing in a schedule covering the subject matter, duration, nature and purpose of processing, types of personal data and categories of data subjects. Check that these descriptions match the service being supplied. A supplier that determines its own purposes for using data is not acting solely as a processor for that activity.

Check the required processor terms

Under UK GDPR, the DPA should require the processor to:

The agreement should also explain how the processor handles a personal data breach, including notification procedures, required information and cooperation. Avoid relying only on a general obligation to notify. The timing, communication route and responsibility for investigating the incident should be clear.

Review sub-processors and international transfers

Check whether the processor can appoint sub-processors, whether prior written authorisation is required and how changes are notified. The processor remains responsible for its sub-processors, so the DPA should require equivalent data protection obligations to flow down the chain. Identify where data is accessed or stored. Transfers outside the UK require an appropriate transfer mechanism and a documented assessment of the protection available in the destination country.

Align the DPA with the commercial deal

Compare the DPA with the limitation of liability clause, indemnities, insurance requirements, service levels and termination rights in the main contract. Confirm who pays for audits, assistance with data subject requests and deletion or migration of data. Check that security commitments are specific enough to assess, including access controls, encryption, resilience, backup and testing requirements. Finally, ensure the contract reflects operational reality, including the actual data fields collected, retention periods, approved sub-processors and the process for changing instructions.