Set up your bannerConfigure Your ToolsAnalytics

Google Firebase

How to configure Google Firebase at different risk levels and map it in the Consenter Manager.

This work is licensed under CC BY-SA 4.0

Typical processing purposes: Improve the service, Support marketing analytics

Overview

This guide explains how to implement different privacy configurations for Google Firebase on websites and how to reflect them in the Consenter Manager.

  1. Configure the third-party service.
  2. Map the selected configuration in the Consenter Manager.
  3. Update your privacy policy to reflect the actual implementation.

The configurations are comparative examples, not guarantees of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.

At a glance

Scope. This guide covers the Firebase JavaScript SDK on websites, specifically the client-side products that collect visitor data: Performance Monitoring and Google Analytics for Firebase. Firebase back-end products used for the site's own functions (Hosting, Authentication, Firestore, Realtime Database) are infrastructure for the operator's application and are not covered.

What the service does in this scope. Performance Monitoring collects page-load and network-request timings together with Firebase installation IDs and IP addresses. Google Analytics for Firebase on the web is Google Analytics and "is subject to separate terms".

Legal role. "When customers use Firebase, Google is generally a data processor under GDPR" under the Firebase Data Processing and Security Terms. Google Analytics is a separate service with separate terms; refer to the Google Analytics 4 guide for its configuration and mapping.

Configurations included.

ConfigurationSummary
Configuration A — Medium riskPerformance Monitoring only; Analytics not initialised; loaded after consent.
Configuration B — Higher riskPerformance Monitoring plus Google Analytics for Firebase; loaded after consent; Analytics configured and mapped per the GA4 guide.

No configuration without prior consent. Performance Monitoring stores a Firebase installation ID in the browser. No consent-free configuration is documented.

ActionConfiguration A — Medium riskConfiguration B — Higher risk
Firebase products initialised in the browserPerformance MonitoringPerformance Monitoring, Analytics
LoadingBlocked until consentBlocked until consent
Consenter Manager entriesOne entry (Google as Processor)Firebase entry plus a Google Analytics entry (see GA4 guide)

Step 1 — Configure Google Firebase

#Configuration areaWhere to configure itConfiguration A — Medium riskConfiguration B — Higher risk
1Processing purposesOperator decisionImprove the serviceImprove the service; Support marketing analytics
2Products initialisedWeb app code (getPerformance, getAnalytics)getPerformance onlygetPerformance and getAnalytics
3Data processing termsFirebase console > Project settings > accept the Firebase Data Processing and Security TermsAcceptedAccepted (Analytics: separate GA terms)
4LoadingConsenter script blocking for the Firebase SDKBlocked until consentBlocked until consent
5Performance Monitoring data collectioninstrumentationEnabled / dataCollectionEnabled settings of the Performance SDKEnabled after consent; disabled on withdrawalSame
6RetentionNot configurable in the Firebase console for Performance Monitoring——

Step 2 — Map the configuration in the Consenter Manager

Processing location. Google LLC is a US company and can be required to disclose data in its possession, custody or control regardless of storage location. Google participates in the EU–US Data Privacy Framework.

Configuration A — Medium risk

Consenter Manager fieldValue to selectBasis and conditions
Processing purposesImprove the servicePerformance monitoring.
Tracking methodFirst party tracking (cross-session)The Firebase installation ID persists in the browser for the site.
IdentifierDevice identifiers, IP addressFirebase installation IDs; IP addresses.
Data categoriesDevice identifiers, IP address, Device characteristics, Browsing and interaction dataTimings of page loads and network requests.
Legal role of data recipientProcessorFirebase Data Processing and Security Terms.
Personalisation modelNo personalisation—
Maximum storage durationNot documented—
Processing locationUnited States as potential processing and access locationSee note above.

Configuration B — Higher risk

Map the Firebase entry as in Configuration A, and create a separate Google Analytics entry following the Google Analytics 4 guide (Google Analytics is subject to separate terms).

Privacy-policy follow-up

  • Google as processor for Firebase; Performance Monitoring data and installation IDs; for B, Google Analytics as described in the GA4 guide; US transfer, DPF and potential access by US authorities.

Verification checklist

  • No Firebase installation or performance requests before consent.
  • A: getAnalytics not called anywhere in the bundle.
  • Firebase Data Processing and Security Terms accepted in the console.

How is this guide?

Shape Consenter Together

Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.

Need Help?

Last updated on

On this page