Firebase/Google has relaunched a lot of its services and also added new services to the mix.
We had previously integrated Firebase and Firebase hosting and will now update the old services accordingly, as well as add new services where appropriate. Just some of the features of new Firebase are described below:
- Analytics – see user behavior and measure attribution from a single dashboard.
- Cloud Messaging – deliver and receive messages across platforms reliably
- Authentication – reduce friction with robust authentication
- Realtime Database – store and sync app data in realtime
- Storage – store files with ease
- Hosting – deliver web content faster
- Remote Config – customize your app on the fly
- Test Lab – test in the lab, not on your users
- Crash Reporting – keep your app stable
- Notifications – engage with users at the right moment
- App Indexing – drive organic search traffic to your app
- Dynamic Links – send users to the right place inside your app
- Invites – empower your users to share your app
- AdWords – acquire users with the reach of Google
The way Firebase works is: all of the above features work independently, but they also work well together.
Firebase Analytics seems to be at the heart of what Google is trying to accomplish with Firebase, therefore let’s take a look at the requirements Google sets out for the privacy policy when running Firebase.
Privacy policy requirements for Firebase Analytics
The Firebase Analytics terms of service say the following:
“You must post a Privacy Policy and that Privacy Policy must provide notice of Your use of cookies, identifiers for mobile devices (e.g., Android Advertising Identifier or Advertising Identifier for iOS) or similar technology that are used to collect data. You must disclose the use of the Service, and how it collects and processes data. This can be done by displaying a prominent link to the site “How Google uses data when you use our partners’ sites or apps”, (located at How Google uses data when you use our partners’ sites or apps, or any other URL Google may provide from time to time) (…)”
and the Firebase Analytics Use Policy adds:
“You are required to notify your App Users by disclosing the following information:
- The Firebase Analytics features you have implemented.
- How you and third-party vendors use first-party cookies, or other first-party identifiers, and third-party cookies and similar technologies, such as identifiers for mobile devices (including Android Advertising ID and Advertising Identifier for iOS), or other third-party identifiers, together.
- How App Users can opt-out of the Firebase Analytics features you use, including through applicable device settings, such as the device advertising settings for mobile apps, or any other available means.”
How to write that privacy policy
Update July 2017: iubenda now has the following integrations regarding Firebase services:
- Firebase Authentication
- Firebase Cloud Functions
- Firebase Cloud Messaging
- Firebase Cloud Storage
- Firebase Crash Reporting
- Firebase Dynamic Links
- Firebase Hosting (old, updated)
- Firebase Invites
- Firebase Legacy (old, updated, now called Legacy)
- Firebase Notifications
- Firebase Performance Monitoring
- Firebase Realtime Database
- Firebase Remote Config
- Google Analytics for Firebase
With iubenda you can just find any of the Firebase features in our privacy policy generator, tap on them and add them to your privacy policy.
Remember to add a new custom section with opt-out information for your users, if you implement any opt-outs. Read more about this topic in the Firebase documentation.
Generate a privacy policy for your Firebase app
p.s. if you are using Google Analytics for Firebase, watch out, you’ll also need to follow the EU User Consent Policy, according to Google Analytics for Firebase Use Policy.
