AutomationMake and the GDPR: agreement, role and data location.
Make is a automation tool. Most customers use it as a processor, it publishes its data processing agreement, and the data location depends on your account. Below: what to check and how to declare it.
Prefilled for you · Free to set up · No credit card
In short
- Category
- Automation
- Usual role
- Usually a processor
- Data location
- Set per account or project
- Agreement
- Published by the vendor
What does Make do with personal data?
Automate workflows and transfer selected records between connected applications. That is how Privacyboard describes a typical use of Make, as a starting point you can edit.
The data usually involved: personal data included in configured workflow inputs, outputs and execution logs.
Is Make a processor or a controller?
Most customers use Make as a processor: it handles personal data on their instructions, for the purposes they set. That is the common reading for automation tools and it is what Privacyboard suggests.
As a processor, it needs a written agreement with you under Article 28, and you should know which subprocessors it uses. Confirm the role against your own agreement, because the way you use a tool can change it.
Where does Make store personal data?
Make does not have one fixed location for every customer. Set by the zone of your account.
How to find yours: The address of your Make account shows its zone (for example eu1.make.com or us1.make.com).
Even when the main location is in the EU, ask whether subprocessors or support access involve a transfer outside the EEA, and record it if so.
Does Make have a data processing agreement?
Checked on 1 November 2026. Vendors change their pages, so check the date.
Yes. Make publishes the text of its data processing agreement as a PDF on its own website. Article 28 of the GDPR requires a written contract with every processor, so this is the document to read and keep.
What we noted when we opened the page: PDF titled "Celonis Data Processing Agreement for Make" (Make is operated by Celonis).
A page that exists does not mean you are covered. Whether the agreement applies to you depends on your plan and on what you accepted, so record the decision yourself in your vendor list.
Read the Make agreementHow to declare Make
- 1
In your privacy policy
Name Make as a recipient, say what it is used for (automate workflows and transfer selected records between connected applications) and mention any transfer outside the EEA. Articles 13 and 14 ask you to tell people who receives their data.
- 2
In your vendor list
Add Make with its purpose, the data involved, its role, its region and a link to the agreement. Privacyboard prefills all of this, you confirm or correct it.
- 3
In your processing register
Link Make to the activities that use it, so each record shows its recipients. Article 30 asks the register to list the categories of recipients.
What to check before relying on Make
- List the workflows that carry personal data and what fields they pass.
- Check run-history retention, since inputs and outputs are often logged.
- Review which connected apps the tool can read.
- Record the provider as a recipient and note its region.
Questions, answered.
Is Make GDPR compliant?
Privacyboard does not certify vendors. Compliance depends on how Make is configured and used, on the agreement you have with it and on your own practices. What can be checked is documented here: it publishes a data processing agreement, the usual role and the data location. Read the agreement itself before relying on it.
Does Make have a DPA?
Yes. Make publishes the text of its data processing agreement as a PDF on its own website. Article 28 of the GDPR requires a written contract with every processor, so this is the document to read and keep. You can read it at https://www.make.com/data-processing-agreement.pdf.
Is Make a data processor?
Usually, yes. Most customers use Make as a processor that acts on their instructions. Check your own agreement and how you use the tool, because the role can differ.
Where does Make store data?
Make does not have one fixed location for every customer. Set by the zone of your account. How to find yours: The address of your Make account shows its zone (for example eu1.make.com or us1.make.com).
Do I need to mention Make in my privacy policy?
Yes, if Make handles personal data for you. The GDPR asks you to tell people who receives their data (Articles 13 and 14). Name the vendor or its category, say what it is used for and mention any transfer outside the EEA.
How do I add Make to my vendor list?
In Privacyboard, pick Make from the catalog. The purpose, the data, the suggested role and a link to its agreement are prefilled, and you confirm each one. Creating a workspace is free.
Privacyboard is not affiliated with Make. Names and logos belong to their owners and are used only to identify the tool. This page summarises public documents as checked on 1 November 2026; it is guidance, not legal advice, and it does not certify any vendor.