Structuring a playbook for Data Processing Agreements
A practical guide to configuring Review for DPAs, focusing on audit rights, sub-processor consent, and breach notification windows.
Data Processing Agreements (DPAs) are high-volume, low-variance documents. Because they are driven by statutory requirements—primarily the GDPR and equivalent state or national frameworks—the core concepts rarely change. Yet, because the financial consequences of a data breach are severe, the negotiations around the edges of these concepts are heavily contested.
For legal teams managing hundreds of vendor agreements a year, the DPA review process is often a bottleneck. A well-configured playbook in Review automates the mechanical checks, allowing counsel to focus on the commercial reality of the data transfer. This guide outlines how to structure a DPA playbook in ZAAN, focusing on the four most frequently negotiated provisions. We assume you are configuring the playbook from the perspective of a data processor.
Defining acceptable breach notification windows
Statutes often require notification of a data breach “without undue delay.” Commercial contracts usually demand a specific hour count. Controllers will push for 24 hours; processors generally seek 72 hours, which aligns with the processor’s own regulatory reporting deadline under the GDPR.
When configuring Review for breach notification, you must account for both numerical thresholds and vague language. We recommend setting a three-tier rule:
- High severity: Flag any notification window strictly less than 48 hours. Processors rarely have sufficient information within 24 hours to provide a meaningful notice, and agreeing to this creates an immediate compliance risk.
- Note severity: Flag the use of qualitative terms like “immediately” or “promptly” without a defined hour limit. Review will highlight these terms and propose an inline redline replacing them with “without undue delay, and in no event later than 72 hours.”
- Accept: Any specific threshold between 48 and 72 hours.
Our ZAAN-7B Counsel model is trained to recognise when a notification obligation is triggered by a “suspected” breach versus an “actual” breach. Your playbook should include a strict rule flagging any requirement to notify based merely on suspicion, as this leads to unnecessary alarm and operational strain.
Audit rights and the cost of inspection
Controllers require audit rights to verify compliance. Processors must ensure these audits do not disrupt normal business operations or become unfunded mandates.
A robust playbook configuration for audit rights requires Review to check for three distinct boundaries within the clause. If any are missing, the system should generate a Medium severity flag and propose a redline.
First, notice. The playbook should require a minimum of 30 days’ prior written notice for any routine audit. Second, frequency. The clause must limit audits to once per 12-month period, unless a prior audit revealed a material non-compliance or a security incident has occurred. Third, cost allocation. Controllers often draft audit clauses that are silent on costs, which defaults to the processor bearing the burden of hosting the auditor. Review should automatically insert language stating that audits are conducted at the controller’s sole expense.
Because Review understands the semantic relationship between clauses, it will not flag a missing cost allocation if a later, general expenses clause covers audit activities. It reads the whole agreement before generating the flag.
Sub-processor mechanics and objection periods
The mechanism for authorising new sub-processors is a standard friction point. Controllers prefer specific prior consent for every new vendor. Processors require general written authorisation to operate efficiently, coupled with a mechanism to notify the controller of changes.
Configure your playbook to reject “specific prior consent” models outright (High severity). Review will strike this language and replace it with a general authorisation framework.
You must then define the objection mechanics. If the processor adds a sub-processor, the controller needs a window to object. A standard configuration accepts a 15-to-30-day objection window. The critical element your playbook must check for is the resolution mechanism if an objection occurs. If the draft allows the controller to simply terminate the agreement for convenience upon objection, Review should flag this. The preferred redline should require the parties to discuss a commercially reasonable alternative in good faith before any termination right crystallises.
Liability caps within the DPA context
The interplay between a DPA and a Master Services Agreement (MSA) regarding liability is complex. Controllers frequently attempt to carve data protection breaches out of the MSA’s general limitation of liability, effectively making the processor’s liability uncapped.
Using Review 4.2, you can define strict floors for liability exposure. The playbook should be set