Does it need the visitor’s consent?
Yes. Firebase Authentication brings third-party content or features. If it sets cookies or contacts its servers before the visitor uses it, you need their consent: the content stays hidden until they choose, with a button to turn it on.
The vendor is based outside the European Union (United States): the data sent may be transferred outside the EU. Mention it in your privacy policy.
Spot it on your site
- Open your site in a private window, without clicking the banner.
- Developer tools › Network.
identitytoolkit.googleapis.comis already there? Firebase Authentication fires before consent.
Block Firebase Authentication until consent
When the scan finds Firebase Authentication, Nodbar files it under “Content and preferences” and holds its scripts back until the visitor chooses. After the install, a new scan checks that nothing fires before consent any more.
Your banner in your colours, with Firebase Authentication blocked until the visitor chooses.
Create my bannerFAQ
Is Firebase Authentication required?
No. Firebase Authentication brings third-party content: it can stay hidden until the visitor agrees, with a button to turn it on.
Can I use Firebase Authentication without a cookie banner?
Yes, if it stores nothing and does not contact its servers before the visitor uses it. Otherwise, you need their consent.
What happens if the visitor rejects it?
The Firebase Authentication content stays hidden; the rest of the site must work normally.
Sources: Nodbar’s tracker database and Open Cookie Database, EDPB guidelines on the ePrivacy Directive. Updated on . This is not legal advice.