Reviewing DPAs at scale: a checklist for privacy counsel
Twelve things to check in every data processing agreement, and how to stop reviewing the same sub-processor clause forty times a quarter.
Data processing agreements are repetitive by design, which makes them ideal for a playbook-driven review. The risk is not in the clauses you read carefully; it is in the ones you skim because they are usually fine.
The checklist
- Roles of the parties are stated (controller, processor, sub-processor).
- Processing purposes and data categories are listed in an annex.
- Standard contractual clauses are attached, with the correct module.
- Sub-processor list is current and has a notice period for changes.
- You have a right to object to new sub-processors.
- Breach notification has a fixed window, not “without undue delay” alone.
- Audit rights exist, even if satisfied by third-party reports.
- Deletion or return of data at the end of the agreement is specified.
- International transfers are covered by a valid mechanism.
- Security measures are described, not just referenced.
- Liability for data breaches is addressed in the main agreement.
- Governing law is consistent with the main agreement.
Automate the boring half
Items 1, 3, 4, 6 and 8 are almost always pass or fail. Let the review engine check them and spend your attention on transfers, security measures and liability.