When your DPA changes, re-paper the whole book without a spreadsheet.
There is no signup flow to catch acceptance when the deal closes by order form. Pacts is that surface: one current text, per-client re-acceptance on every change, and a record that says who is on which version.
Free for 3 standard terms · 5 clients · no card. Your clients accept without an account.
Data-licensing and enrichment firms closing via order form plus emailed terms, audience and panel-data providers, API vendors whose mid-market deals are sales-assisted — where the DPA and sub-processor notices travel by email rather than inside a product.
When the text changes, how do you re-paper the book — and who’s on which version?
- Every text change re-papers the entire book — and the book is the product.
- Acceptance lives in email threads and order-form checkboxes that record a tick, not the text.
- Under GDPR a DPA change must be notified and approved — ‘we posted the new version’ is not compliance.
Same meeting. Same terms. A page they accept — not a contract they sign.
Versioned, per client
Every version is stored with its hash. Publishing a new one flags every client for re-acceptance and tracks who has.
Notified and approved, provably
Re-acceptance on every version is exactly what the EDPB asks for — and each one is a record, not a mailing.
The surface you don’t have
A private link per contact, no account: the acceptance surface a sales-led deal otherwise lacks.
Put these on Pacts:
Keep the negotiated MSA — or any client-imposed paper — in DocuSign. Does a click hold up? →
This is the whole recipient experience — try it.
A private link, the full text, one checkbox per document, one button. No account, no signature field, nothing to forward. Then the record, then the certificate.
See a sample certificateNo account · No signature · One click
Tick the box and accept — this is the whole recipient experience.
Start with the agreement you already send. Measure days-to-yes on your next five clients.
Send your first terms