Blog

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

  1. Roles of the parties are stated (controller, processor, sub-processor).
  2. Processing purposes and data categories are listed in an annex.
  3. Standard contractual clauses are attached, with the correct module.
  4. Sub-processor list is current and has a notice period for changes.
  5. You have a right to object to new sub-processors.
  6. Breach notification has a fixed window, not “without undue delay” alone.
  7. Audit rights exist, even if satisfied by third-party reports.
  8. Deletion or return of data at the end of the agreement is specified.
  9. International transfers are covered by a valid mechanism.
  10. Security measures are described, not just referenced.
  11. Liability for data breaches is addressed in the main agreement.
  12. 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.

Give your team its week back

Bring three contracts you reviewed last month. We'll show you what Clausewell finds in each, live, in 30 minutes.

Elena MarchettiKarim HaddadNia OkaforAroha NgataMargaret EllisTalk to legal engineers who've sat in your chair