Firebase Privacy Policy: What to Disclose for Each Service
If your app uses Firebase, your privacy policy has to say what Firebase collects from your users. This page lists what each Firebase service collects and keeps, according to Google's own documentation, what to write about it, and a sample section you can adapt.
Quick answer
Every app that uses Firebase needs a privacy policy: Apple and Google Play require one for all apps, and Google's Analytics terms require you to disclose that you use Google Analytics. Firebase treats you as the data controller and Google as your processor, so you write the policy. List each Firebase service you use, what it collects, why, how long it is kept and what choices users have.
- Services covered
- 12 Firebase services
- Who writes the policy
- You, as the data controller
- Required by
- Apple, Google Play, Analytics terms
Reviewed against official sources on November 16, 2026. This guide is general information, not legal advice.
What each Firebase service collects
Data and retention below come from Google's Privacy and Security in Firebase page and its Play data disclosure pages. This is what Firebase collects by itself. Add whatever your own code sends.
| Service | What it collects | How long Google keeps it | What your policy should say |
|---|---|---|---|
| Google Analytics for Firebase | App-instance ID, the Android advertising ID, coarse location derived from a masked IP address, in-app purchase and subscription events, screen views and sessions. | Set by your data retention setting in Google Analytics. | That you use Google Analytics, what it collects, why, and a link to Google's page on how it uses data from apps. Google's Analytics terms require this. |
| Firebase Authentication | Passwords, email addresses, phone numbers, user agents and IP addresses. | IP addresses for a few weeks. Other sign-in data until you delete the user, then removed within 180 days. | The sign-in details you collect, that Google processes them for you, and that Authentication runs only from US data centers. |
| Crashlytics | Crash stack traces, Crashlytics installation UUIDs, Firebase installation IDs and, for native (NDK) crashes, minidump data. | 90 days, then removal starts. Minidumps only while the crash is processed. | That crash reports and device details are sent to Google to fix bugs, and how long they are kept. |
| Cloud Messaging (push notifications) | Firebase installation IDs, used to decide which device gets a message. | Until you delete the ID through the API, then removed within 180 days. | That you send notifications, the identifier used to deliver them, and how users turn them off. |
| Performance Monitoring | Firebase installation IDs and IP addresses (to map events to countries). | IP-linked events for 30 days, other performance data for 60 days. | That you measure app performance and that this uses device identifiers and IP addresses. |
| Remote Config | Firebase installation IDs, used to pick which settings each device gets. | Until you delete the ID, then removed within 180 days. | Usually covered by your device identifier wording. Mention personalization if you use it. |
| In-App Messaging | Firebase installation IDs and message impressions, clicks and dismissals. It requires the Analytics SDK. | Until you delete the ID, then removed within 180 days. | That you show in-app messages and track how people interact with them. Your Analytics wording must be there too. |
| App Check | Attestation material from Play Integrity, App Attest or reCAPTCHA, and App Check tokens. | Tokens last at most 7 days, or up to 30 days with replay protection. | That you check app and device integrity to protect your backend from abuse. |
| Firestore, Realtime Database and Cloud Storage | Whatever your app saves: profiles, messages, photos, files. Realtime Database also logs IP addresses and user agents for its profiler. | You decide for your own data. Realtime Database keeps IPs and user agents for a few days. | Every type of user data you store, why, and how long you keep it. This is usually the largest part of the policy. |
| Cloud Functions | IP addresses, used to run functions triggered by users. | Temporarily, only to provide the service. | Plus whatever personal data your own functions process or send elsewhere. |
| Firebase Hosting | IP addresses of incoming requests, for abuse detection and usage analysis. | A few months. | That your website's host logs visitors' IP addresses. |
| Firebase AI Logic | The prompts and responses your app sends to Gemini models, plus the signed-in user ID when used with Authentication. | Not stored by AI Logic itself. The Gemini API provider's retention applies. | That user input is sent to Google's AI models, what for, and whether it is used to train models. |
Firebase App Distribution also collects testers' names, email addresses and device identifiers, but only from people you invite to beta test, not from your app's users.
Skip the table work
Generate a privacy policy that lists the Firebase services you use
Pick Firebase and your other SDKs, such as RevenueCat, AdMob or Sentry, and get a privacy policy that covers each one. Edit it, then host it on a link you can paste into App Store Connect and Play Console.
- Firebase and 15+ app SDKs
- Hosted link for the stores
- Free account available
How to write the Firebase part of your privacy policy
1.List the Firebase SDKs in your app
Check build.gradle for com.google.firebase packages, your Podfile or Swift Package list for Firebase products, or package.json for @react-native-firebase or firebase. Note SDKs that come in with others: In-App Messaging pulls in Google Analytics and Firebase installations.
2.Note what each one collects
Use the table above for the data each service collects on its own, then add what your code sends: the fields you write to Firestore, user properties you set in Analytics, the content of crash logs you add.
3.Write the Firebase part of your policy
For each service, say what data, why, that Google processes it on your behalf, how long it is kept, and what choices users have. Firebase describes you as the data controller (GDPR) or business (CCPA) and Google as your processor or service provider, so the policy is yours to write.
4.Add the Google Analytics wording
If you use Analytics, Google's terms require your policy to cover your use of device identifiers, to disclose that you use Google Analytics and how it collects and processes data, for example by linking to Google's page at google.com/policies/privacy/partners.
5.Decide where you need consent first
Analytics, Crashlytics, Cloud Messaging and Performance Monitoring start automatically. If your users must opt in first, for example under EU rules, Firebase lets you turn off auto-initialization and start each service after the user agrees.
6.Match the store forms and link the policy
Apple and Google Play both require a privacy policy link in the store listing and inside the app. Fill in Play's Data safety form and Apple's privacy details from the same list, so the forms and the policy say the same thing.
Sample Firebase section for a privacy policy
For an app that uses Authentication, Firestore, Cloud Storage, Crashlytics, Cloud Messaging and Analytics. Delete the parts you do not use and fill in the brackets. It covers Firebase only, not the rest of a privacy policy.
Services we use to run the app We use Firebase, a set of services provided by Google LLC, to run parts of this app. Google processes this data on our behalf under its Firebase data processing terms. Sign-in (Firebase Authentication). When you create an account we collect your email address [and phone number]. Google also logs your IP address and device user agent for a few weeks to prevent abuse. Firebase Authentication is run from data centers in the United States. Your content (Cloud Firestore and Cloud Storage). We store [your profile, posts and photos] so the app works across your devices. We keep it until you delete your account. [Say how long backups last.] Crash reports (Firebase Crashlytics). If the app crashes, it sends a crash report with device details and an installation identifier so we can fix the problem. Crash reports are kept for 90 days. Notifications (Firebase Cloud Messaging). We use an installation identifier to deliver notifications. You can turn notifications off in your device settings. Analytics (Google Analytics for Firebase). We use Google Analytics to understand how the app is used. It collects an app-instance identifier, [the advertising identifier,] device information, purchase events and approximate location based on your IP address. You can turn analytics off in [Settings > Privacy]. To learn how Google uses this information, visit https://www.google.com/policies/privacy/partners/.
The store forms and the policy must agree
Google Play says your privacy policy must disclose how your app collects, uses and shares user data, not limited to what you put in the Data safety form. Apple's guideline 5.1.1(i) asks the policy to identify what the app collects and confirm that third parties such as analytics tools give the same protection. Build both store forms from the same list of SDKs you used for the policy. See our guides for Android apps and iOS apps.
General information, not legal advice. Firebase changes its services and documentation, so check the linked Google pages when you update your SDKs.
Get a complete policy
Turn the sample into a full privacy policy
The sample covers Firebase. Your policy also needs your contact details, user rights, children's data and the rest. Generate the whole thing in a few minutes.
Frequently asked questions
Do I need a privacy policy if my app uses Firebase?
Yes. Apple and Google Play require a privacy policy link for every app, in the store listing and inside the app. If you use Google Analytics for Firebase, Google's Analytics terms also require your privacy policy to disclose that you use it and how it collects and processes data.
Does Firebase give me a privacy policy for my app?
No. Firebase publishes what each of its services processes, but it describes the app developer as the data controller under GDPR, or the business under CCPA, with Google acting as processor or service provider. Writing and publishing the policy is the developer's job.
Is Firebase GDPR compliant?
Firebase offers Data Processing and Security Terms, and Google is certified under the EU-U.S. Data Privacy Framework. Whether your app complies depends on how you use it: what you collect, whether you get consent where it is needed, and what your privacy policy says.
Where does Firebase store user data?
Firebase Authentication runs only from data centers in the United States. Most other Firebase services run on Google's global infrastructure and may process data wherever Google has facilities, unless the service lets you choose a data location.
Do I have to mention Google Analytics separately from Firebase?
It is safest to. Google Analytics is a separate service with its own terms, and those terms require you to disclose that you use Google Analytics and how it collects and processes data. Linking to google.com/policies/privacy/partners is one way Google suggests doing it.
How do I fill in Google Play's Data safety form for Firebase?
Firebase publishes a page listing what each Android SDK collects automatically and what depends on your usage. Google says the developer is responsible for the answers, so combine that page with the data your own code collects.
More for app developers
Mobile app privacy policy
What iOS and Android apps need in one policy.
React Native privacy policy
Cross-platform apps and their SDKs.
Avoid a privacy policy rejection
Why Google Play and Apple reject policies, and how to fix it.
PolicyForge MCP server
Let your coding agent write and host the policy from your code.