Consent Log

Why should I use consent log?

To comply with GDPR, website owners must be able to demonstrate that they have obtained user consent for data processing activities. This requirement is articulated in recital 42 of the GDPR, which states:

“Where processing is based on the data subject’s consent, the controller should be able to demonstrate that the data subject has given consent to the processing operation” 

In practice, this means that businesses must keep clear records of when and how consent was obtained. These records should include details such as the date and time of consent, the specific data processing activities consented to, and any methods used to obtain consent. Ensuring this documentation is in place not only helps in compliance with GDPR but also enhances transparency and trust with users, demonstrating a commitment to protecting their privacy rights.

What information is stored?

CookieHub only stores necessary data required to demonstrate user choices. Below is a complete list of data stored:

Token

A random string stored in the CookieHub cookie in the users browser along with the settings for the cookie categories. In case you need to demonstrate the consent, you’ll have to request this token from the subject to find the entry from the consent log.

Anonymized IP address

The IP address of the client. The last part of the IP address is replaced with 0 as IP address could be considered personal information.

Date and time

The date and time of consent.

Url

The full url that the user was viewing when he configured consents using the CookieHub widget.

Country

The registered country code for the IP address. When using geolocation this can be useful to identify if the user consented or didn’t get any choices.

User agent

The user agent usually contains the browser and operating string information.