AuthenticationAuth0 and the GDPR: agreement, role and data location.
Auth0 is a authentication 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
- Authentication
- Usual role
- Usually a processor
- Data location
- Set per account or project
- Agreement
- Obtained through the vendor
What does Auth0 do with personal data?
Authenticate users and manage application sessions and access. That is how Privacyboard describes a typical use of Auth0, as a starting point you can edit.
The data usually involved: names, email addresses, user identifiers, IP addresses and authentication logs.
Is Auth0 a processor or a controller?
Most customers use Auth0 as a processor: it handles personal data on their instructions, for the purposes they set. That is the common reading for authentication 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 Auth0 store personal data?
Auth0 does not have one fixed location for every customer. Chosen when the tenant is created.
How to find yours: Tenant settings show the region (look at your tenant domain: us, eu, au, jp).
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 Auth0 have a data processing agreement?
Checked on 1 November 2026. Vendors change their pages, so check the date.
Auth0 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: Explains how to obtain the Auth0 DPA (Okta documents).
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 Auth0 reference pageHow to declare Auth0
- 1
In your privacy policy
Name Auth0 as a recipient, say what it is used for (authenticate users and manage application sessions and access) 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 Auth0 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 Auth0 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 Auth0
- Confirm where user records are stored and whether you can choose the region.
- Check how long sign-in logs are kept and how users are deleted.
- Keep the provider in your privacy policy as a recipient of account data.
- Review the provider’s security documentation for the controls you rely on.
Questions, answered.
Is Auth0 GDPR compliant?
Privacyboard does not certify vendors. Compliance depends on how Auth0 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 Auth0 have a DPA?
Auth0 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://support.auth0.com/center/s/article/DPA.
Is Auth0 a data processor?
Usually, yes. Most customers use Auth0 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 Auth0 store data?
Auth0 does not have one fixed location for every customer. Chosen when the tenant is created. How to find yours: Tenant settings show the region (look at your tenant domain: us, eu, au, jp).
Do I need to mention Auth0 in my privacy policy?
Yes, if Auth0 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 Auth0 to my vendor list?
In Privacyboard, pick Auth0 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 Auth0. 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.