However, I notice that mixpanel is dropping a cookie and a localStorage value on page load - before the opt in function is called.
The localStorage value is simply an opt/in out flag with a number to serve as a boolean. The cookie, however, contains some client data like device id, initial referrer etc.
I'm worried about this, as it may not be GDPR-compliant. Ideally no cookies should be dropped until the user has consented.
Does anyone know why this cookie is dropped? Is it needed and is there a way to prevent it? I was under the impression that opting out by default = 0 cookies.
I have a React application that triggers the
init
function on mount:I'm trying to be GDPR-compliant, so as you can see I'm opting out by default. A cookie acceptance banner triggers the opt in user event:
However, I notice that mixpanel is dropping a cookie and a localStorage value on page load - before the opt in function is called.
The localStorage value is simply an opt/in out flag with a number to serve as a boolean. The cookie, however, contains some client data like device id, initial referrer etc.
I'm worried about this, as it may not be GDPR-compliant. Ideally no cookies should be dropped until the user has consented.
Does anyone know why this cookie is dropped? Is it needed and is there a way to prevent it? I was under the impression that opting out by default = 0 cookies.