Skip to content
Consent management

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

iubenda is a consent management tool. Most customers use it as a processor, it explains how to get 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
Consent management
Usual role
Usually a processor
Data location
Set per account or project
Agreement
Obtained through the vendor

What does iubenda do with personal data?

Show cookie notices, record visitors’ consent choices and manage privacy documents. That is how Privacyboard describes a typical use of iubenda, as a starting point you can edit.

The data usually involved: visitor consent choices, consent identifiers, IP address and device details, and the pages where consent was given.

Is iubenda a processor or a controller?

Usually a processor

Most customers use iubenda as a processor: it handles personal data on their instructions, for the purposes they set. That is the common reading for consent management 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 iubenda store personal data?

Set per account or project

iubenda 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 iubenda’s data processing agreement and its subprocessor information.

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

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

iubenda does not publish the full text of its data processing agreement on a public page. The reference page explains how a customer gets or signs it, usually from inside the account. Article 28 of the GDPR still requires a written contract, so get it and keep a copy.

What we noted when we opened the page: A help page that links the agreement in several languages. Updated Nov 28, 2024. No data hosting statement.

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.

Open the iubenda reference page

How to declare iubenda

  1. 1

    In your privacy policy

    Name iubenda as a recipient, say what it is used for (show cookie notices, record visitors’ consent choices and manage privacy documents) 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 iubenda 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 iubenda 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 iubenda

  • Check that the banner blocks non-essential tags until the visitor agrees.
  • Keep consent records for as long as you may need to prove them, and no longer.
  • Link your privacy policy and cookie list from the banner.
  • Test the banner after any change to your site or tools.
FAQ

Questions, answered.

Is iubenda GDPR compliant?

Privacyboard does not certify vendors. Compliance depends on how iubenda is configured and used, on the agreement you have with it and on your own practices. What can be checked is documented here: it explains how to get a data processing agreement, the usual role and the data location. Read the agreement itself before relying on it.

Does iubenda have a DPA?

iubenda does not publish the full text of its data processing agreement on a public page. The reference page explains how a customer gets or signs it, usually from inside the account. Article 28 of the GDPR still requires a written contract, so get it and keep a copy. The reference page is https://www.iubenda.com/en/help/6758-data-processing-agreement-between-iubenda-and-its-users/.

Is iubenda a data processor?

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

iubenda 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 iubenda’s data processing agreement and its subprocessor information.

Do I need to mention iubenda in my privacy policy?

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

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