feat: gdpr compliance

[sshanzel]

Changes

• Update our Cookie Banner into two categories:
  • EU: allow users to update the cookie preference on a granular level.
  • Non EU: use the same updated cookie banner (delete the old one), but should only have one button labeled "I understand".
• Pixel tracking should be delayed being rendered for EU users until marketing is accepted.
• Introduce a placeholder for the YT contents to not render the integration, which registers a cookie, when not accepted. Again, for EU users.
• Even though we are storing the information in the browser cookie, I also had to use the local storage in order to know if the user have made past decisions about the preferences.
  • This is because our default value is true, but then we also need to check whether made any past decision already, which is the local storage in itself.
• You might notice some things were built in a reusable way which was not necessary in hindsight. We had some late decisions that led to using just one, so I just deleted the other parts that used those reusable blocks.

Events

Did you introduce any new tracking events?

Experiment

Did you introduce any new experiments?

Manual Testing

Caution

Please make sure existing components are not breaking/affected by this PR

MI-736 #done

Preview domain

https://mi-736.preview.app.daily.dev

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
daily-webapp	✅ Ready (Inspect)	Visit Preview	Jan 15, 2025 7:20pm

1 Skipped Deployment

Name	Status	Preview	Updated (UTC)
storybook	⬜️ Ignored (Inspect)		Jan 15, 2025 7:20pm