DatabaseFirebase and the GDPR: agreement, role and data location.
Firebase is a database 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
- Database
- Usual role
- Usually a processor
- Data location
- Set per account or project
- Agreement
- Published by the vendor
What does Firebase do with personal data?
Store application data and manage end-user authentication. That is how Privacyboard describes a typical use of Firebase, as a starting point you can edit.
The data usually involved: email addresses, account identifiers, authentication metadata and customer-uploaded records.
Is Firebase a processor or a controller?
Most customers use Firebase as a processor: it handles personal data on their instructions, for the purposes they set. That is the common reading for database 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 Firebase store personal data?
Firebase does not have one fixed location for every customer. Chosen once at creation and cannot be changed afterwards.
How to find yours: Project settings → Default GCP resource location. Firestore and Storage locations are set at creation.
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 Firebase have a data processing agreement?
Checked on 1 November 2026. Vendors change their pages, so check the date.
Yes. Firebase 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: "Firebase Data Processing and Security Terms", separate from the Google Cloud DPA. Last modified Aug 2024.
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 Firebase agreementHow to declare Firebase
- 1
In your privacy policy
Name Firebase as a recipient, say what it is used for (store application data and manage end-user authentication) 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 Firebase 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 Firebase 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 Firebase
- Confirm the region chosen when the database was created.
- Check backup retention, since deleted records can live on in backups.
- Review who has access to production data and how that access is logged.
- Record any transfer outside the EEA and its safeguard.
Questions, answered.
Is Firebase GDPR compliant?
Privacyboard does not certify vendors. Compliance depends on how Firebase 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 Firebase have a DPA?
Yes. Firebase 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://firebase.google.com/terms/data-processing-terms.
Is Firebase a data processor?
Usually, yes. Most customers use Firebase 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 Firebase store data?
Firebase does not have one fixed location for every customer. Chosen once at creation and cannot be changed afterwards. How to find yours: Project settings → Default GCP resource location. Firestore and Storage locations are set at creation.
Do I need to mention Firebase in my privacy policy?
Yes, if Firebase 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 Firebase to my vendor list?
In Privacyboard, pick Firebase 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 Firebase. 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.