It means that you need to keep records of the cookie preferences your users set when they visit your site.
If you have a cookie banner, you do.
Failure to comply means that the cookie consents you do capture will be considered invalid in the eyes of the law, and you may be at risk for sanctions.
It’s easy: Activate the Cookie and Consent Preference Log in the Privacy Controls and Cookie Solution, now included up to 25,000 pageviews per month in our new Essentials plan.
Then $71.88/year instead of $172/year
✅ No extra configuration required
Save $143 by subscribing to the new Essentials plan. Plus:
The Cookie and Consent Preference Log allows you to create records of your users’ cookie consent preferences when they visit your site. You need this feature to align with the requirements of most Data Protection Authorities across Europe (including the UK, France, Italy, Belgium, and more).
Yes, the Essentials plan includes the Cookie and Consent Preference Log with up to 25,000 pageviews per month. If you need more, you can either leverage Extra Usage, which allows the product to continue working with an extra charge after you reach the limit of use for your plan, or upgrade to a bigger plan. Please see the pricing page for more details.
Yes, if your website installs non-exempt cookies and European users visit it, you need to keep valid records of your users’ cookie preferences.
In other words, regardless of the number of monthly pageviews, you need to store a cookie and consent preference log if you have a cookie banner.
No, the Consent Database collects and stores proof of consent specifically for online and offline forms, and requires some setup.
The Cookie and Consent Preference Log, however, is a fully automated feature of the Privacy Controls and Cookie Solution, our solution for managing consent preferences for cookies, trackers and similar technologies.
The Cookie and Consent Preference Log solves this problem – without the need for a dedicated configuration. For each consent given, we collect:
This way, the consent is collected via the string of 6 hexadecimal characters and the IP address is uniquely linked to a specific user. If necessary, the DPA may: