AAcme Agreement Desk Contract management and e-signing. AI reviews every redline; a person signs. Set up your signature
Contracts / Umbrella Corp.

Data Processing Agreement

6 AI calls · 34,845 tokens
$0.05 · 32s model time
Umbrella Corp. DPA 4 versions Signed

Audit trail

Every version, review and decision, oldest first
  1. v1 sent to Umbrella Corp.Acme Cloud Inc. · 2026-10-22 11:23:08 UTC
    Acme_Data-Processing-Agreement_v1.docxv1 · ours OpenDownload
  2. v2 received from Umbrella Corp.Umbrella Corp. · 2026-10-22 11:23:08 UTC
    Umbrella_Data-Processing-Agreement_v2_redline.docxv2 · theirs OpenDownload
    3 changes from v1 AI recommends: Escalate to legal Full diff
    1 Escalate 2 Push back
    Related changes, read together
    Restrictions on Acme's infrastructure and vendor flexibility

    The customer is limiting where Acme can process data (EU only) and how quickly Acme can add new subprocessors (60 days' notice), which together constrain Acme's hosting and vendor choices.

    Escalate § 3.1.a added Group: Restrictions on Acme's infrastructure and vendor flexibility
    Provider will store and process Customer Personal Data only within the European Union.

    What it means

    The customer added a clause requiring Acme to store and process all Customer Personal Data only within the European Union. This restricts the existing right in 3.1 to transfer data outside the EEA.

    Impact on Acme

    Acme could not use its US-hosted infrastructure (e.g., AWS in the United States) or any non-EU processing, and it conflicts with clause 3.1 and our standard SCC-based transfer model. This needs a business and legal decision.

    Sources 95% confident
    Answer: Rejected, our wording restored by Ana Ruiz · 2026-10-22 11:23:26 UTC
    Internal: Our hosting is in the US and the EU; EU-only needs a product change.
    To Umbrella Corp.: We cannot commit to EU-only processing; transfers are covered by the SCCs.
    Push back Subprocessor Notice Period Key term · modified Group: Restrictions on Acme's infrastructure and vendor flexibility
    30 60 days before a new Subprocessor is engaged.

    What it means

    The customer doubled the advance notice Acme must give before adding a new subprocessor, from 30 days to 60 days.

    Impact on Acme

    Acme would have to wait twice as long before bringing in a new subprocessor, which slows vendor changes and infrastructure rollouts. It is also more than our standard position allows.

    AI's suggested reply to Umbrella Corp.

    We can offer general authorisation for listed subprocessors with 30 days' notice before a new one is engaged, plus the customer's right to object.

    Sources 95% confident
    Answer: Rejected, our wording restored by Ana Ruiz · 2026-10-22 11:23:26 UTC
    Internal: 60 days would block vendor changes.
    To Umbrella Corp.: We keep 30 days' notice with your right to object.
    Push back § 4.1 modified
    Upon becoming aware of any Security Incident, Provider will: (a) notify Customer without undue delay when feasible, but no later than 72 24 hours after becoming aware of the Security Incident; (b) provide timely information about the Security Incident as it becomes known or as is reasonably requested by Customer; and (c) promptly take reasonable steps to contain and investigate the Security Incident. Provider’s notification of or response to a Security Incident as required by this DPA will not be construed as an acknowledgment by Provider of any fault or liability for the Security Incident.

    What it means

    The customer shortened the deadline for Acme to notify them of a security incident from 72 hours to 24 hours after Acme becomes aware of it.

    Impact on Acme

    Acme would have a much tighter deadline to notify, risking breach of contract if investigation takes longer. This is stricter than the playbook minimum of 48 hours and stricter than GDPR requires of a processor.

    AI's suggested reply to Umbrella Corp.

    We can commit to notifying Customer without undue delay and no later than 72 hours (or, at most, 48 hours) after becoming aware of a Security Incident, as GDPR Art. 33(2) requires only notice without undue delay.

    Sources 95% confident
    Answer: Countered by Ana Ruiz · 2026-10-22 11:23:26 UTC
    Our wording: Upon becoming aware of any Security Incident, Provider will: (a) notify Customer without undue delay when feasible, but no later than 48 hours after becoming aware of the Security Incident; (b) provide timely information about the Security Incident as it becomes known or as is reasonably requested by Customer; and (c) promptly take reasonable steps to contain and investigate the Security Incident. Provider’s notification of or response to a Security Incident as required by this DPA will not be construed as an acknowledgment by Provider of any fault or liability for the Security Incident.
    Internal: 48 hours is the shortest we can operate.
    To Umbrella Corp.: We can commit to 48 hours, with details provided in phases.
  3. AI review finished: Escalate to legal2026-10-22 11:23:26 UTC
  4. Round closed by Ana Ruiz2026-10-22 11:23:27 UTC

    2 rejected, 1 countered

  5. v3 sent to Umbrella Corp.Acme Cloud Inc. · 2026-10-22 11:23:27 UTC
    Acme_Data-Processing-Agreement_v3.docxv3 · ours OpenDownload
    Cover note to Umbrella Corp. Our answer to your changes in v2. Version v3 is attached, unsigned. - Subprocessor Notice Period: not accepted; our original wording is restored. We keep 30 days' notice with your right to object. - § 3.1.a: not accepted; the new clause is taken out. We cannot commit to EU-only processing; transfers are covered by the SCCs. - § 4.1: we propose new wording, see the attached version. We can commit to 48 hours, with details provided in phases.
  6. v4 received from Umbrella Corp.Umbrella Corp. · 2026-10-22 11:23:27 UTC
    Umbrella_Data-Processing-Agreement_v4.docxv4 · theirs OpenDownload
    No changesUmbrella Corp. accepted v3 as it was
  7. Round closed by the desk2026-10-22 11:23:27 UTC

    No changes: Umbrella Corp. accepted v3.

  8. Signed by Ben Okafor for Acme2026-10-22 11:23:27 UTC
    Data Processing Agreement (signed).pdfv4 · signed OpenDownload

    Signed v4 (Umbrella_Data-Processing-Agreement_v4.docx), SHA-256 d4fb1e370e6156adad67b0c251cec72530fa5a27e7833b4105fd1d0a882b74d0. Final check: no red lines in the final text.

Clause history

Each changed clause, version by version

Subprocessor Notice Period

  1. v1 · Acme30 days before a new Subprocessor is engaged.
  2. v2 · Umbrella Corp.30 60 days before a new Subprocessor is engaged. push back
  3. v3 · Acme60 30 days before a new Subprocessor is engaged. rejected by Ana Ruiz

§ 3.1.a

  1. v1 · Acme(not in this version)
  2. v2 · Umbrella Corp.Provider will store and process Customer Personal Data only within the European Union.escalate
  3. v3 · Acme(removed)rejected by Ana Ruiz

§ 4.1

  1. v1 · AcmeUpon becoming aware of any Security Incident, Provider will: (a) notify Customer without undue delay when feasible, but no later than 72 hours after becoming aware of the Security Incident; (b) provide timely information about the Security Incident as it becomes known or as is reasonably requested by Customer; and (c) promptly take reasonable steps to contain and investigate the Security Incident. Provider’s notification of or response to a Security Incident as required by this DPA will not be construed as an acknowledgment by Provider of any fault or liability for the Security Incident.
  2. v2 · Umbrella Corp.Upon becoming aware of any Security … when feasible, but no later than 72 24 hours after becoming aware of the … or liability for the Security Incident. push back
  3. v3 · AcmeUpon becoming aware of any Security … when feasible, but no later than 24 48 hours after becoming aware of the … or liability for the Security Incident. countered by Ana Ruiz