Skip to content
Privacyboard
Communications

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

Digitevent is a communications 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
Communications
Usual role
Usually a processor
Data location
Often France, check your account
Agreement
Obtained through the vendor

What does Digitevent do with personal data?

Send text messages, verification codes and notifications, and handle phone calls with customers. That is how Privacyboard describes a typical use of Digitevent, as a starting point you can edit.

The data usually involved: phone numbers, Messages & support requests, call metadata, delivery status

Is Digitevent a processor or a controller?

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

Digitevent is usually associated with France, 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 Digitevent says (read on 2026-11-05): “hosted on AWS in France”, with redundancy across the European Union Source: https://www.digitevent.com/en/gdpr-data-protection-security

How to find yours: Check the account’s region settings or the provider’s data processing terms.

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.

Which legal basis usually applies to Digitevent?

For the usual use of Digitevent, companies most often rely on performance of a contract and legitimate interests (GDPR Article 6(1)). Verification codes and service notifications are part of delivering the service; keeping logs rests on a legitimate interest.

The interest you would state: “Keeping a record of our communications to resolve disputes and improve our service.” The GDPR asks you to say which interest you pursue (Article 13(1)(d)).

Marketing texts and calls to individuals need consent. The balancing test is yours to do: the interest must be real, the processing necessary for it, and people’s rights must not outweigh it.

This is a starting point, not legal advice: the basis belongs to your activity, and you confirm it in your register.

Sources: GDPR Article 6, lawfulness of processing, EDPB Guidelines 1/2024 on legitimate interest

Does Digitevent have a data processing agreement?

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

Digitevent 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: Security and GDPR page says a Data Processing Agreement is available and can be incorporated into the customer's contract; DPO contact dpo@digitevent.com. Operated by DIGIT EVENT SAS (Paris).

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 Digitevent reference page

How to declare Digitevent

  1. 1

    In your privacy policy

    Name Digitevent as a recipient, say what it is used for (send text messages, verification codes and notifications, and handle phone calls with customers) 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 Digitevent 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 Digitevent 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 Digitevent

  • Confirm the region and any transfer outside the EEA.
  • Keep the agreement text you accepted and its date.
  • List the provider in your privacy policy and your processing register.
Pricing

Go online for free. Grow when you need to.

Free puts you online. Pro adds requests, domains and your team; Business, your brand only.

Per workspace, in US dollars. Cancel any time.

Free

$0 forever

No card, no time limit

For getting compliant and going online on your own.

Start for free

Key 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 Pro

Everything 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 Business

Everything 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

Compare every feature →

FAQ

Questions, answered.

Is Digitevent GDPR compliant?

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

Digitevent 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.digitevent.com/en/gdpr-data-protection-security.

Is Digitevent a data processor?

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

For the usual use of Digitevent, companies most often rely on performance of a contract and legitimate interests (GDPR Article 6(1)). Verification codes and service notifications are part of delivering the service; keeping logs rests on a legitimate interest. The interest you would state: “Keeping a record of our communications to resolve disputes and improve our service.” The GDPR asks you to say which interest you pursue (Article 13(1)(d)).

Where does Digitevent store data?

Digitevent is usually associated with France, 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 Digitevent says (read on 2026-11-05): “hosted on AWS in France”, with redundancy across the European Union Source: https://www.digitevent.com/en/gdpr-data-protection-security

Do I need to mention Digitevent in my privacy policy?

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

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

Compare all communications tools

Privacyboard is not affiliated with Digitevent. 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