Celigo and the GDPR: agreement, role and data location.
Celigo 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
- Often Customer choice: US or Germany, check your account
- Agreement
- Published by the vendor
What does Celigo do with personal data?
Automate workflows and transfer selected records between connected applications. That is how Privacyboard describes a typical use of Celigo, as a starting point you can edit.
The data usually involved: security & access logs, Personal data included in configured workflow inputs, outputs
Is Celigo a processor or a controller?
Most customers use Celigo 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 Celigo store personal data?
Celigo is usually associated with Customer choice: US or Germany, but the location can depend on your plan or settings. Privacyboard prefills it as a starting point that you should check in your account.
What Celigo says (read on 2026-11-05): “subject to the Customer's selection of a regional data center” Source: https://www.celigo.com/global-processing-addendum/
How to find yours: Check your account settings, the address you log in to, or the provider’s data processing terms. Support can tell you if you cannot find it.
If the data is processed outside the European Economic Area, Articles 44 to 49 require a transfer mechanism, such as standard contractual clauses, an adequacy decision or the EU-US Data Privacy Framework. Your privacy policy should name it.
Which legal basis usually applies to Celigo?
The legal basis for Celigo depends on what goes through it. The legal basis depends on the data and the activity the workflow supports. Use the basis of that activity in your register.
This is a starting point, not legal advice: the basis belongs to your activity, and you confirm it in your register.
Does Celigo have a data processing agreement?
Checked on 5 November 2026. Vendors change their pages, so check the date.
Yes. Celigo publishes the text of its data processing agreement 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: Global Processing Addendum (undated). Contracting entity Celigo, Inc. Data hosted in the customer-selected regional data centre (US or Germany); DPF self-certification, then EU SCCs, UK IDTA and Swiss terms.
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 Celigo agreementHow to declare Celigo
- 1
In your privacy policy
Name Celigo 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 Celigo 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 Celigo 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 Celigo
- 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.
Go online for free. Grow when you need to.
Free puts you online. Pro adds requests, domains and your team; Business, your brand only.
Free
$0 forever
No card, no time limit
For getting compliant and going online on your own.
Start for freeKey features:
- Privacy and cookie policies
- Vendor and processing registers
- Requests and breaches tracked
- Impact assessment screening
- Privacy center on privacyboard.io
- Cookie banner on 1 domain
- 1 person
No card needed
ProRecommended
$32 per month
Billed $384 a year Save $84
For taking requests, covering all your sites and working as a team.
Start with ProEverything in Free, plus:
- DPA for your clients
- PDF and Excel exports
- Email reminders
- Request form and replies
- Your own domain
- Banner on 3 domains, every choice logged
- Weekly site scan
- Complete DPIAs and TIAs
- AI assistant connector
- Up to 5 people, with roles
Cancel any time
Business
$109 per month
Billed $1,308 a year Save $240
For proving it to customers and auditors, under your brand only.
Start with BusinessEverything in Pro, plus:
- No Privacyboard mention
- Security section and vendor alerts
- Evidence pack in one click
- Banner on 10 domains, daily scan
- Up to 50 people
- Two-step verification required
- Activity log kept 3 years
Bank transfer on request
Questions, answered.
Is Celigo GDPR compliant?
Privacyboard does not certify vendors. Compliance depends on how Celigo 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 Celigo have a DPA?
Yes. Celigo publishes the text of its data processing agreement 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.celigo.com/global-processing-addendum/.
Is Celigo a data processor?
Usually, yes. Most customers use Celigo as a processor that acts on their instructions. Check your own agreement and how you use the tool, because the role can differ.
Which legal basis applies when I use Celigo?
The legal basis for Celigo depends on what goes through it. The legal basis depends on the data and the activity the workflow supports. Use the basis of that activity in your register. This is a starting point, not legal advice: the basis belongs to your activity, and you confirm it in your register.
Where does Celigo store data?
Celigo is usually associated with Customer choice: US or Germany, but the location can depend on your plan or settings. Privacyboard prefills it as a starting point that you should check in your account. What Celigo says (read on 2026-11-05): “subject to the Customer's selection of a regional data center” Source: https://www.celigo.com/global-processing-addendum/
Do I need to mention Celigo in my privacy policy?
Yes, if Celigo 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 Celigo to my vendor list?
In Privacyboard, pick Celigo 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.
Similar tools
Privacyboard is not affiliated with Celigo. 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.