Skip to content
Hosting

Netlify and the GDPR: agreement, role and data location.

Netlify 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
Set per account or project
Agreement
Published by the vendor

What does Netlify do with personal data?

Host business websites, online services or other company systems. That is how Privacyboard describes a typical use of Netlify, as a starting point you can edit.

The data usually involved: website or service content, account identifiers, IP addresses and server logs where applicable.

Is Netlify a processor or a controller?

Usually a processor

Most customers use Netlify 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 Netlify store personal data?

Set per account or project

Netlify does not have one fixed location for every customer. Netlify does not name a data center in its agreement, so data may be processed outside the EEA.

How to find yours: Check your Netlify account settings and the data processing agreement; Netlify’s subprocessor list shows where data may be processed.

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 Netlify have a data processing agreement?

Checked on 1 November 2026. Vendors change their pages, so check the date.

Yes. Netlify 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: Called Data Processing Agreement. Updated Jun 2026. No data center is named: data may be processed outside the EEA, Switzerland and the UK, see the subprocessor list.

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 Netlify agreement

How to declare Netlify

  1. 1

    In your privacy policy

    Name Netlify as a recipient, say what it is used for (host business websites, online services or other company systems) and mention any transfer outside the EEA. Articles 13 and 14 ask you to tell people who receives their data.

  2. 2

    In your vendor list

    Add Netlify 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. 3

    In your processing register

    Link Netlify 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 Netlify

  • 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.
FAQ

Questions, answered.

Is Netlify GDPR compliant?

Privacyboard does not certify vendors. Compliance depends on how Netlify 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 Netlify have a DPA?

Yes. Netlify 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.netlify.com/pdf/netlify-dpa.pdf.

Is Netlify a data processor?

Usually, yes. Most customers use Netlify 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 Netlify store data?

Netlify does not have one fixed location for every customer. Netlify does not name a data center in its agreement, so data may be processed outside the EEA. How to find yours: Check your Netlify account settings and the data processing agreement; Netlify’s subprocessor list shows where data may be processed.

Do I need to mention Netlify in my privacy policy?

Yes, if Netlify 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 Netlify to my vendor list?

In Privacyboard, pick Netlify 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 Netlify. 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.

Be ready before they ask.

Start with your website address. In about 5 minutes your first documents are ready, with no password to create.

Start free