Data Processing Agreement

A controller–processor template for personal data processing, security, and sub-processors.


What this contract contains

Preamble and parties.In the creator you enter each party, pick which side decides how personal data is used, and name the main agreement this DPA attaches to. That choice labels one party Controller and the other Processor. Names the DPA, the parties, and the main agreement it attaches to. Choose who is the controller in the creator.
Definitions. Gives GDPR meanings to personal data, processing, controller, processor, and personal data breach.
Details of the processing.In the creator you describe why data is processed, which categories and whose data are involved, and how long processing lasts. Records the purpose, data types, subjects, and how long processing lasts.
Roles of the parties. Labels one party the controller and the other the processor. The controller is responsible for a lawful basis and required notices.
Documented instructions. The processor may only process personal data on documented instructions, and must say if an instruction appears unlawful.
Confidentiality of personnel. People who process the data must be bound by confidentiality, and access is limited to those who need it.
Security of processing. Requires technical and organizational measures appropriate to the risk, including encryption, availability, and regular testing.
Sub-processors.Customers need visibility into who else will touch the data. In the creator you choose prior approval or notice-and-objection, and how many days’ notice a new sub-processor requires. Sets how downstream processors are approved and how much notice is required. Choose both in the creator.
Data subject rights. The processor helps the controller respond to data-subject requests and forwards any request it receives directly.
Personal data breach.In the creator you choose how quickly a personal data breach must be reported. The processor must notify the controller of a personal data breach on the timing you set.
Assistance. The processor helps with security, breach notices to authorities, impact assessments, and consultation with regulators.
End of processing. Says whether personal data is deleted, returned, or the controller chooses when the services end.
Audits.Audit frequency is a creator setting. The default is once a year unless there has been an incident. Sets how often the controller can review the processor's compliance.
Transfers.The transfer safeguard, standard contractual clauses or another mechanism you name, is a creator setting. Skip transfers if personal data stays in the EEA or UK. Says whether personal data may leave the EEA or UK, and which safeguard applies.
Liability and the main agreement. Liability follows the limits in the main agreement. The rest of that agreement stays in effect.
Governing law.Governing law and venue decide which state’s rules apply and where a dispute must be filed, or whether it goes to arbitration instead. In the creator you pick a listed jurisdiction or enter another, then choose court or arbitration so the sample is not locked to a default state. Sets the state law that governs the DPA and where disputes must be brought. Choose the jurisdiction in the creator.
General. Covers assignment limits, waiver rules, severability, entire agreement language, notices, and counterpart or electronic-signature execution language.
Signature blocks. Authorized signatory and title lines for each party, ready for wet-ink or e-signature fields.

Frequently asked questions

When should I use a DPA?

Use a DPA when a SaaS or services vendor processes personal data for a customer, for GDPR Article 28-style processor contracts, and when enterprise security reviews require a processor agreement.

Is this DPA compatible with the EU GDPR?

Yes. This template is a GDPR Article 28 contract between a controller and a processor. It records the purpose and duration of processing, the types of personal data, and the categories of data subjects, and it limits the processor to documented instructions. It also covers confidentiality, security, sub-processors, help with data-subject requests, breach notice, audits, and deletion or return when the services end. If personal data leaves the EEA, the United Kingdom, or Switzerland, it can include the EU Standard Contractual Clauses, the UK Addendum, and Swiss adaptations. That is the processor contract a customer in the EU usually needs before a vendor, including a vendor outside the EU, handles personal data for them.

Is a DPA the same as a privacy policy?

No. A privacy policy explains practices to individuals. A DPA is a contract between organizations about how personal data is processed on documented instructions, with security, sub-processor, audit, and return-or-deletion duties.

Can I download this DPA template?

Yes. Use Download .docx to get a Word file with placeholders such as [Party A] and [Effective Date]. You can edit it in Word or Google Docs, or create a filled-in version in the free contract creator.

Is the sample legally binding as shown?

No. Placeholder sample text is a starting point. It becomes an agreement for your deal after you fill in the details—manually or in the free contract creator—and the parties sign. A DPA is meant to sit with a main services or SaaS agreement, not replace it.

When should I use the free contract creator instead of editing the file?

Use the free contract creator if you want guided choices for who is the controller, the main agreement, processing purpose, data types, duration, sub-processor approval, transfers, breach notice, end-of-processing, audits, and governing law, without hunting through every blank yourself.

Didn't find an answer to your question? Book a short call and we'll walk through Formable with you.

Book a call