Your wording
Your clauses stay yours
Upload the agreement your practice already uses as a firm template. The body is untouched; the placeholders for the client's legal name, address and contact are filled from confirmed answers.
Loading…
Data processing agreements
The agreement is the short part. Its schedules — who else touches the data, where it goes, on what basis — are built from the vendors you confirmed, and a fact nobody knows is marked rather than invented.
Doing this for clients rather than your own company? The same page for a practice.
Free · No sign-up · Up to ten websites
A data processing agreement is the contract Article 28 of the GDPR requires between a controller and a processor. When you sell to an enterprise, you are the processor and their legal team reads what you send back.
What slows a company down is not the clauses, which are largely settled. It is Annex II and III: the list of sub-processors with their legal entities, and the table of transfers outside the EEA with the mechanism each one relies on.
What it has to cover
Your wording
Upload the agreement your practice already uses as a firm template. The body is untouched; the placeholders for the client's legal name, address and contact are filled from confirmed answers.
Schedules from data
The description of processing, the sub-processor annex and the transfer table come from the client's confirmed facts and the vendor registry, by code — never from a model's paraphrase.
Ends honestly
If the client has not told you how long support conversations are kept, the schedule says so with the question to ask. It does not offer a plausible retention period.
Every vendor fact comes from our own registry: 225 vendors with the date each entry was checked.
Your agreement, with the client's legal name, registered address and privacy contact filled from answers you confirmed.
Legal entity, country, purpose, transfer mechanism and DPA link for every vendor that client uses, with the date each was checked.
Every vendor outside the EEA with the mechanism it relies on, assembled from the registry rather than recalled.
The same confirmed answers produce the record of processing, the privacy policy and the retention schedule alongside the agreement.
When a vendor changes its contracting entity, every client agreement naming it is flagged, with the documents to regenerate.
DOCX and PDF carrying your logo and firm name, with no mention of us in the text or the file metadata.
Add the wording your practice uses as a firm template, with placeholders where client details belong.
Answer in the workspace or send the client a link for the parts only they know. You confirm every answer before it is used.
The agreement is drafted with its schedules built from those facts. You read it, export it under your brand, and hear when a vendor change dates part of it.
Enter up to ten client websites. Free, no sign-up, the first report in about a minute.