Adapt cookie banner for GDPR.

What is this feature about? (1 sentence)

This will make our cookies banner more compliant for GDPR while ensuring that customer support via Intercom is not impaired.

Why is it needed? What is the value? For whom do we build it?

• The data protection team reach out: Our cookie banner is implemented a “nudging” way meaning the accepting cookies button is more prominent as the declining cookies button. In some german jurisdiction this was ruled as not GDPR compliant.
• More details on Slack
• Currently, when not accepting analytics cookies, Intercom is not possible. The user doesn’t even see it.
• Intercom is a very valuable feedback channel for us.

High-level overview of the feature

• Users should always have a way to access support.
• Split out customer support from Analytics, i.e. have 3 check boxes:
  • Necessary (Pre-checked, cannot be changed)
  • Customer support (not pre-checked, for Intercom)
  • Analytics (not pre-checked, for Google analytics)
• Adapt the info text to:

We use cookies to provide you with the best experience and to help improve our website and application. Please read our Cookie Policy for more information. By clicking “Accept all”, you agree to the storing of cookies on your device to enhance site navigation, analyze site usage and provide customer support.

• Accept and deny buttons need to be equal in terms of their “prominence”.

  • I would call them “Accept selection” and “Accept all”

• Show the Intercom live chat icon always ()

  • If Customer support cookie is accepted -> Existing behavior
  • If Customer support cookie is not accepted:
    • Let the user know that this requires the Customer Support cookie (“You attempted to open the customer support chat. Please accept the customer support cookie.” )
    • Ask the user to accept or deny that cookie
    • I don’t know what’s the best way to solve this, UX-wise. Currently I think a bottom sheet since that’s where the cookies are managed currently. Other apps use a popup.

Screens

Zeplin: https://zpl.io/VKQ0Xm7 https://zpl.io/V17YkDk

Misc

Current one:

Updates

• Jan 11, Tobi: Add more details

[tschubotz]

yep, that sounds correct to me!

The cookie banner is displayed when the user visits the landing page for the first time and there is an fake Intercom button displayed too.

To be 100% correct, I’d rather say "The cookie baner is displayed when the user visits the landing page and they haven’t previously clicked “Accept selection” or “Accept all”.

(Besides, the cookie banner also appears with the user-selection when clicking “preferences” in the footer - same like it works currently. )

[tschubotz]

The langing page (gnosis-safe.io/) also needs that and there is currently another landing page iteration under way. @germartinez will work on the landing page update. Once done, we can see if it makes sense if German also does this change in the webapp or whether we then pick it up here.