4 ms·

Hi, I honestly hate the cookie banner myself - that's why I made it as much invisible as possible. But I'm using Google's Firebase for user authentication and t

Hi, I honestly hate the cookie banner myself - that's why I made it as much invisible as possible. But I'm using Google's Firebase for user authentication and therefore it uses cookies. I also store your choice of theme dark/light into a cookie so it's there for you next time. I believe that's why I have to have the banner there. Or am I wrong?

ocdtrekkie 5y ago
You probably shouldn't backend on a Google service if you value your users' privacy. The theme cookie is easier to solve: Use CSS media preferences instead and use people's browser settings to choose it. That being said, cookie warnings may not be necessary if you aren't storing anything personally identifiable.
ALittleLight 5y ago
Per my understanding of GDPR you only need the cookie warning for cookies unrelated to your site's fundamental operation. Admittedly, I'm not a lawyer and I've not really liked too closely at it, but I don't think you need a warning just because you use a cookie.
crazypython 5y ago
Firebase is easy to set up but pricey to scale and hard to migrate off of.
- fakedang 5y ago
  Firebase Authentication is free though, and very convenient to integrate off the bat.
  - trizoza 5y ago
    Yeah, that's what I'm using - no limits on users or registrations or logins. Pretty good deal for an indie hacker.
napsterbr 5y ago
I always thought that for purely functional cookies (like storing theme preferences) the banner is uncalled for. Is there a place I can read more about? I guess this varies from jurisdiction to jurisdiction? This (cookie compliance) is a mess...