Website owners are legally obliged to let visitors revoke (take back) a previously given consent and must also be able to document any consent choice made by any visitor. Both of these are possible with Cookie Consent.
Every time someone accepts cookies on a website, proof of that consent must be stored so that it can be retrieved in the unlikely event that the visitor requests documentation that he or she did in fact consent. The visitor has the right to request this according to certain legal frameworks such as the GDPR's right to transparency.
Consent information is stored on Cookiebot's servers and we'll be able to retrieve it on request. In order to match a consent with a specific visitor, Cookiebot adds a unique identifier called consent ID to each consent provided.
If a visitor requests proof that they consented or withdrew a consent to cookies, you can ask them to locate this ID and send it to you. You can then pass it on to us in a Service Desk ticket so we can look it up in the consent database and provide proof of consent.
Where do visitors find the consent ID?
The visitor's most recent consent choice and their consent ID can be located in the cookie declaration.
Consent ID traceability
The consent ID is stored in a cookie in the visitor's local storage. Be aware that if the visitor clears cookies on their browser, the consent ID will also be cleared and we will no longer be able to trace that visitor's unique consent.
Visitors can revoke their consent or change consent preferences at any time on the cookie declaration.
Adding a "withdraw/renew consent" button
If you do not wish to make use of the cookie declaration, then you must provide alternative ways for the user to easily withdraw their consent.
For example, if you wish to insert a "renew consent" link in the website footer, you can add the following snippet into an HTML module:
This creates a link which, when clicked, displays the cookie banner to the visitor: