User consents Reports - Identify User by STAMP
Hi Team,
I saw that each time I change my preferences, Cookiebot makes a new STAMP unique random code that is stored on my local cookie "CookieConsent".
My question is:
How can I demonstrate that a User accepted category "Marketing" on date X after that he re-send his preferences on date Y (X+n) ?
this considering that the STAMP that identified the User on date X was overwritten by the new STAMP Y in the only place where the code is saved, namely the cookie itself ?
NB1: Here the reference about the GDPR you reported on your user guide:
Logging and demonstration of user consents
As you wrote:
The EU General Data Protection Regulation (GDPR) states the following in its Article 7 named 'Conditions for consent':
7.1 Where processing is based on consent, the controller shall be able to demonstrate that the data subject has consented to processing of his or her personal data.
In other words, you as a website owner or operator must be able to document that your website users coming from the European Union have given consent to you processing their personal data on your website.
As you can see the GDPR law does not say "unless the user has subsequently changed his preferences"
NB2: the problem is the same also if the User opens the acceptance box, do not change any preference, and click on "Accept selected" = Cookiebot generate a new STAMP and store it on cookie, overwriting the previous one, which is lost.
Thanks for your feedback
A.S.
PS: also consider this post
Please sign in to leave a comment.
Comments
0 comments