SaaS processor · EU B2B customers
GDPR DPA Generator for SaaS
Draft a customer-specific Article 28 data processing agreement in minutes. You are the processor; each of your EU B2B customers is the controller. The generator selects clauses on the server from the facts you enter, then you review the draft clause by clause.
All generator features are free in this MVP.
Draft, not legal advice. This tool generates a starting draft for review. It does not provide legal advice or guarantee GDPR compliance. Have qualified counsel review the agreement before signature.
Customer DPA workspace
No draft generated yet.
Draft status
Draft generated
- Clauses generated
- —
- Clauses to review
- —
- Template version
- —
Found a gap?
If a requirement is missing from this draft, report it separately. This entry does not depend on any generated clause.
How to Use
- Prepare the legal names and addresses of your customer (controller) and your company (processor).
- Describe the processing: service summary, purposes, personal data categories and data subject categories.
- Configure sub-processors: no sub-processors, general written authorization, or specific authorization, plus the notice period.
- Choose the transfer path: EEA only, or outside the EEA with SCCs if you have already decided to use the EU Standard Contractual Clauses.
- Select security measures, breach notification hours, and what happens to data after termination (delete, return, or controller choice).
- Generate the draft and review each clause. Confirm the clauses that fit, or apply a server-generated alternative with a short reason tag.
- Copy the full draft to your clipboard or print it with your browser, then send it to your customer for review and signature.
Why a Customer-Specific DPA Matters for SaaS
In a typical B2B SaaS relationship, the customer decides why and how personal data is processed, and your company processes that data to deliver the service. GDPR Article 28 requires a written contract between the controller and the processor that covers the processing instructions, duration, nature and purpose, the categories of data and data subjects, and the processor’s obligations.
A privacy policy is not that contract. It explains your own practices to end users; it does not bind you to one customer’s instructions. Copying the same generic annex into every deal also creates a quieter problem: the described data, sub-processors and security measures drift away from what the service actually does.
This tool takes the opposite approach. Each draft is generated from the facts of one customer relationship, so a hosted analytics feature, a support tool and a payment vendor can produce different clauses and a different annex. The result still needs review, but the starting point reflects the deal in front of you.
What the Generator Covers
The generated draft follows the processor obligations in GDPR Article 28 and the usual SaaS annexes:
- Processing only on documented instructions, including transfer rules.
- Confidentiality of personnel authorised to process data.
- Security measures appropriate to the risk, in line with Article 32.
- Sub-processor authorization, notice and flow-down obligations.
- Assistance with data subject requests and with impact assessments.
- Breach notification to the controller.
- Deletion or return of data at the end of the service.
- Audit and information rights for the controller.
Annexes describe the parties, the processing details, the sub-processor list, the transfer path and the security measures you selected. The draft is plain text and is meant to be reviewed clause by clause.
Method and Coverage Formula
The server selects clauses and variants from the structured facts you submit. The front end does not contain an Article 28 rule library, a risk score or legal text assembly. After generation, each clause keeps a rule identifier, a rule version and a confidence value so that corrections can be connected back to the clause that produced them.
The summary reports how many applicable required clauses were generated:
coverage_ratio = generated_applicable_count / applicable_required_totalThe denominator is set by the server for this fact pattern and can reach 100%. It is a template coverage indicator, not a GDPR compliance score or a legal opinion. If no required clause applies, the ratio is empty and the interface says so instead of showing 100%.
International Transfers
Two structured paths are available. “EEA only” states that no personal data leaves the European Economic Area; the SCC linking clause is not included. “Outside the EEA with SCCs” is available only when you have already decided to use the EU Standard Contractual Clauses; the draft then adds a clause that connects the DPA to that transfer mechanism.
This tool does not choose SCC modules, complete the SCC annexes, assess whether a transfer is lawful or produce a transfer impact assessment. Other transfer situations need separate legal review.
Sub-processors and Security Annexes
“No sub-processors” records that you use none. “General written authorization” lets you add or replace vendors after a notice period. “Specific authorization” ties the customer’s approval to the vendors you list. In all three cases the draft must match reality; an authorization clause cannot make an undisclosed vendor compliant.
The same rule applies to security. Select only measures you actually operate, because the annex becomes a contractual statement about encryption, access control, logging, backups, incident response and training.
A Lightweight Workflow for 3–20 Customers
Small SaaS teams often negotiate a handful of DPAs at once. The workspace uses local references from C01 to C20. A reference stores the customer label, the processing preset and result metadata in your browser, so you can reopen a customer and see which clauses you already reviewed.
Party names, addresses, email addresses and document text are deliberately excluded from local history. When you reopen a workspace you re-enter those details and generate a fresh draft; the saved preset only spares you from re-selecting purposes, data categories, sub-processor settings and security measures.
Scope and Limits
This is a drafting aid. It does not decide whether your processing is lawful, whether a transfer mechanism applies, or whether your security measures are adequate. It does not replace qualified counsel, a data protection impact assessment, a record of processing activities, or a signing process.
The draft becomes a contract only when the parties review and sign it. Nothing on this page creates a binding agreement, records acceptance, or verifies a signature.
Data Sources and Review
The clause structure follows GDPR Article 28 and Article 32. The primary legal source is the official GDPR text published by the European Union. The template version shown in a generated draft comes from the server response; this page does not claim an automatic legal update or an unreviewed endorsement.
Because the legal text and the generated draft both need human review, treat the output as a working document for your counsel, not as finished advice.
Reference note. Coverage is a template metric, not a compliance guarantee. Verified against the official GDPR text at EUR-Lex. Template version and generation time are reported by the server for each draft.
Frequently asked questions
Short answers about the draft, the transfer options and local storage.
Do I need a DPA with my SaaS customers?
If you process personal data on behalf of a business customer, GDPR Article 28 requires a written contract that sets out the processing instructions, duration, nature and purpose. The customer is usually the controller and your SaaS is the processor. This tool produces a starting draft of that contract for one customer at a time.
How is a DPA different from a privacy policy?
A privacy policy explains to end users what data you collect and why. A DPA is a contract between your company and a business customer that governs how you process data on that customer's behalf. A privacy policy does not replace the Article 28 contract.
Which transfer option should I choose?
Choose EEA only when no personal data leaves the European Economic Area. Choose outside the EEA with SCCs only if you have already decided to use the EU Standard Contractual Clauses. The generator adds a linking clause for that path. It does not select SCC modules or assess whether a transfer is lawful, so consult qualified counsel for other transfer situations.
What if I use sub-processors?
Select general written authorization or specific authorization and list up to 10 sub-processors. The draft adds the matching authorization and notice terms. Review the list before you send the draft, because the agreement must reflect your real vendors.
What should I do after generating the draft?
Review every clause against your actual service, apply alternatives where they fit better, then copy or print the draft. Send it to the customer for review and signature. This tool does not sign, send or track agreements.
Where is my data stored?
Form values are sent to the generation service only to produce the draft. Your browser can keep a local workspace record with a customer reference, processing presets and result metadata; party names, addresses, email addresses and document text are not saved in local history. Analytics events, if you accept them, contain counts and timings, not company names or draft text.
Is this generator free?
All generator features are free in this MVP. There is no account, no payment step and no locked section.
Does this tool provide legal advice?
No. This tool generates a starting draft for review. It does not provide legal advice or guarantee GDPR compliance. Have qualified counsel review the agreement before signature.