Data Processing Agreement
A GDPR Article 28 processor agreement with the eight mandatory clauses and a filled-in processing schedule.
100% free. Runs entirely in your browser - your files and data never leave your device and nothing is uploaded to any server.
Template, not legal advice. This is a template, not legal advice. It covers the clauses Article 28(3) requires, but the schedule is what an auditor reads, and only you know what is really in it. Where personal data leaves the UK or EEA you also need a transfer risk assessment alongside the clauses referred to here - that assessment is a separate piece of work this cannot do for you.
Start from an example
Fills every answer with a worked example you can edit. Pick the one closest to your business.
Other documents you can generate
Most sites need more than one. A privacy policy without terms, or terms without a refund policy, leaves the obvious gap.
About this tool
Answer a handful of questions and the document writes itself. It exists for SaaS vendors, agencies and developers whose enterprise customers will not sign until a DPA exists, and during procurement, because it is usually the document holding up the contract is when it is worth twenty minutes. One point that separates a usable version from a copied one: article 28(3) lists eight things a processor contract must contain, and a DPA missing any one of them is not a DPA - it is a document that fails an audit. All eight are unconditional here; what the questionnaire changes is the schedule, which is the part auditors actually read and the part generic templates leave blank. Nothing irrelevant is included. A clause that does not apply to you is omitted, not padded - a document describing something you do not do is a problem in its own right. Nothing is uploaded. The whole thing is assembled locally, so confidential details stay on your machine and there is no account to create or delete later.
How to use this tool
- Answer the questionsController. Controller address. Processor. Nothing you type leaves the browser.
- Watch it assembleClauses appear and disappear as you answer, so the document matches what you actually do rather than a generic template.
- Copy or downloadCopy the text, or download as PDF, Word or plain text. The Word version is the one to edit.
Key features
- Runs entirely in your browser. Nothing uploaded, nothing stored, no account.
- Free with no watermark, no email wall and no per-document limit.
- Built from your answers, so clauses you do not need are left out rather than padded.
- Downloads as PDF, Word or plain text - the Word file is editable with no protection on it.
- Says plainly what it is and is not, above the preview rather than in a footer.
Common uses
- Giving a lawyer a draft to review rather than paying them to start from nothing.
- Replacing a copied document that describes a different business.
- Preparing what a client, an app store or a payment processor has asked to see.
- SaaS vendors, agencies and developers whose enterprise customers will not sign until a DPA exists.
- Getting something in place during procurement, because it is usually the document holding up the contract.
Tips for better results
- Keep a copy of each version with its date. When someone asks what your terms said last March, the answer needs to be a file rather than a memory.
- Fill in the free-text fields rather than skipping them. The named lists - processors, exclusions, deliverables - are what make it read as yours rather than copied.
- Read it before you publish it. It is a draft built from standard clauses, and you are the only person who knows whether every line is true of you.
- Download the Word version if you expect to edit it. The PDF is for publishing; the .docx is for changing.
Mistakes to avoid
- Naming no sub-processors. A DPA whose sub-processor list is empty while the service runs on AWS and sends mail through a third party is the first thing a security reviewer catches, and it stalls the deal rather than closing it.
- Leaving the placeholder text in. Anything in square brackets is a field you skipped, and readers spot them immediately.
- Publishing it and never looking again. These go stale - you add a tool, change a processor, start selling somewhere new, and the document still describes last year.
- Hiding it. A document nobody can find does not do its job - it belongs in the footer of every page.
Frequently asked questions
Answer the questions on the left. The document builds as you type, and you can copy it, or download it as PDF, Word or plain text when it looks right.
No. It assembles a draft from standard clauses, and every page says so above the preview. Missing or weak DPAs are found during vendor security reviews, which is a sales problem long before it is a regulatory one.
Yes - free, no signup, no email required and no watermark. It runs in your browser, which is why it costs nothing to provide.
Broadly, SaaS vendors, agencies and developers whose enterprise customers will not sign until a DPA exists. The best time to do it is during procurement, because it is usually the document holding up the contract.
Naming no sub-processors. A DPA whose sub-processor list is empty while the service runs on AWS and sends mail through a third party is the first thing a security reviewer catches, and it stalls the deal rather than closing it.
No. Everything happens on your device - nothing is sent to a server, nothing is stored, and closing the tab clears it.
Yes. Download the Word version and change anything you like - it is a normal .docx with no protection on it.
People also search for
- free data processing agreement template
- data processing agreement template usa
- data processing agreement template uk
- data processing agreement template for small business
- data processing agreement template template
- data processing agreement template no signup
- data processing agreement template