-
Notifications
You must be signed in to change notification settings - Fork 363
Extend Privacy Policy for new cookies that are used #3473
Comments
Hey @johannesmoormann @lukasschor under what category should the Beamer/Feature Discoverability cookies fall into? Currently we are saving them on accepting "Customer support" together with Intercom.
Second question: For how long should these cookies be stored? |
Since it is not directly connected to customer support, I would move it into the Analytics section and just use the days that Beamer describes in their cookie section (most of them 300 days). |
I am talking with our Data Protection Officer about the update of the legal document https://gnosis-safe.io/cookie/ |
OK, so our Legal Team has reviewed their Privacy Policy and it is 👍 to be used. |
Under which category doese Beamer fall? |
I suggest we can rename “Customer support” to “Community support & updates” and place Beamer cookies under the same category as Intercom. |
Not sure I am answering your question correctly @iamacook but these are 3rd-Party cookies are saved to know the number of notifications yet to be seen |
cc @johannesmoormann on moving the Beamer cookies under the "Customer support" and rename it as per @katspaugh suggestion 👀 |
I think @katspaugh's suggestion makes a lot of sense. We could then ever isolate Beamer into it's own hook. (The same goes for Intercom, but that's out of scope). |
Goal
We want to be GDPR compliant when using Beamer.
ToDos
Extend cookie list on privacy policy page (https://www.getbeamer.com/docs/#cookies)Added the task in the EPIC PR to sync with the Privacy policy page
The text was updated successfully, but these errors were encountered: