HostingWebflow and the GDPR: agreement, role and data location.
Webflow is a hosting 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
- Hosting
- Usual role
- Usually a processor
- Data location
- Often the United States, check your account
- Agreement
- Published by the vendor
What does Webflow do with personal data?
Build, host and publish the company website, including forms where enabled. That is how Privacyboard describes a typical use of Webflow, as a starting point you can edit.
The data usually involved: website visitor request metadata, form submissions where enabled and site administration account details.
Is Webflow a processor or a controller?
Most customers use Webflow as a processor: it handles personal data on their instructions, for the purposes they set. That is the common reading for hosting 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 Webflow store personal data?
Webflow is usually associated with the United States, but the location can depend on your plan or settings. Privacyboard prefills it as a starting point that you should check in your account.
How to find yours: Webflow publishes sites through a global network; check Webflow’s documentation and data processing terms for where customer data is stored.
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.
Does Webflow have a data processing agreement?
Checked on 1 November 2026. Vendors change their pages, so check the date.
Yes. Webflow 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: Effective date shown on the page: Nov 2023.
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 Webflow agreementHow to declare Webflow
- 1
In your privacy policy
Name Webflow as a recipient, say what it is used for (build, host and publish the company website, including forms where enabled) 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 Webflow 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 Webflow 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 Webflow
- Confirm the region of every service you use, since it is often chosen per project or per resource.
- If any region is outside the EEA, record the transfer safeguard (SCCs, adequacy decision or Data Privacy Framework).
- Check the provider’s subprocessor list and how it announces changes.
- Keep the agreement text you accepted and the date you accepted it.
Questions, answered.
Is Webflow GDPR compliant?
Privacyboard does not certify vendors. Compliance depends on how Webflow 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 Webflow have a DPA?
Yes. Webflow 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://webflow.com/legal/dpa.
Is Webflow a data processor?
Usually, yes. Most customers use Webflow 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 Webflow store data?
Webflow is usually associated with the United States, but the location can depend on your plan or settings. Privacyboard prefills it as a starting point that you should check in your account. How to find yours: Webflow publishes sites through a global network; check Webflow’s documentation and data processing terms for where customer data is stored.
Do I need to mention Webflow in my privacy policy?
Yes, if Webflow 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 Webflow to my vendor list?
In Privacyboard, pick Webflow 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 Webflow. 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.