CMSBuilder.io and the GDPR: agreement, role and data location.
Builder.io is a cms 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
- CMS
- Usual role
- Usually a processor
- Data location
- Set per account or project
- Agreement
- Published by the vendor
What does Builder.io do with personal data?
Create, store and publish website or app content in a content management system. That is how Privacyboard describes a typical use of Builder.io, as a starting point you can edit.
The data usually involved: editor names, work email addresses, published content and any personal data included in entries.
Is Builder.io a processor or a controller?
Most customers use Builder.io as a processor: it handles personal data on their instructions, for the purposes they set. That is the common reading for cms 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 Builder.io store personal data?
Builder.io does not have one fixed location for every customer. The location depends on the plan, the account and the services you enable.
How to find yours: Check the project or space settings: the region is often chosen when it is created.
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 Builder.io have a data processing agreement?
Checked on 1 November 2026. Vendors change their pages, so check the date.
Yes. Builder.io 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: Europe Data Processing Addendum updated August 19, 2026, for Builder.io, Inc. No single hosting region specified.
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 Builder.io agreementHow to declare Builder.io
- 1
In your privacy policy
Name Builder.io as a recipient, say what it is used for (create, store and publish website or app content in a content management system) 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 Builder.io 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 Builder.io 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 Builder.io
- Keep personal data out of content entries unless you need it.
- Check the region chosen for each project or space.
- Review editor accounts and remove people who have left.
- Record any integration that sends content or visitor data elsewhere.
Questions, answered.
Is Builder.io GDPR compliant?
Privacyboard does not certify vendors. Compliance depends on how Builder.io 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 Builder.io have a DPA?
Yes. Builder.io 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.builder.io/legal/edpa.
Is Builder.io a data processor?
Usually, yes. Most customers use Builder.io 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 Builder.io store data?
Builder.io does not have one fixed location for every customer. The location depends on the plan, the account and the services you enable. How to find yours: Check the project or space settings: the region is often chosen when it is created.
Do I need to mention Builder.io in my privacy policy?
Yes, if Builder.io 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 Builder.io to my vendor list?
In Privacyboard, pick Builder.io 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 Builder.io. 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.