You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are implementing clarity in our app, and as you can see in the following screenshots, the cookies are set before consent to clarity has given.
const clarity = window.clarity;
if (!!clarity) {
clarity('consent');
}
Now, we are aware that cookies are empty, and only filled with a value when consent is given. And erased the value when the consent is removed, but we would expect for the cookies to be erased / not used until consent is granted, instead of using them "empty"
The text was updated successfully, but these errors were encountered:
mmonteiroc
changed the title
[Bug] - Cookies used prior to consent give
[Bug] - Cookies used prior to consent given
Apr 3, 2024
As an add on, we just discovered that the MUID cookie is added before the consent is given.
Either this cookie should be flagged as "strictly necessary" ( so that we can comunicate this to our customers ) or it should only be added once the consent has been given
System is the same one as previously mentioned, where cookies are disabled by default, and the consent is notified like this window.clarity('consent')
Clarity version: v0.7.26
We are implementing clarity in our app, and as you can see in the following screenshots, the cookies are set before consent to clarity has given.
Now, we are aware that cookies are empty, and only filled with a value when consent is given. And erased the value when the consent is removed, but we would expect for the cookies to be erased / not used until consent is granted, instead of using them "empty"
The text was updated successfully, but these errors were encountered: