Are you using cookies on your site? You should display a cookie banner to collect user consent. Here are 5 common mistakes that you should avoid.
Why is this wrong? Almost all European Data Protection Authorities state that there must be a clear option for rejecting or refusing to give consent, which must be just as visible as the Accept option.
Why is this wrong? This is a mistake when your website is available in more than one language. You need to make sure your users get a clear understanding of your banner.
💡 The content of the banner also differs depending on the region of users. For example, California has its own data protection law called the CPRA (CCPA amendment), which requires mentioning specific information.
A Consent Management Platform (CMP) like iubenda can help you. You can pre-select your desired languages, and the software automatically shows a cookie banner that is compliant with the applicable law in the correct language(s), depending on the user’s geolocation.
Why is this wrong? According to the law on cookies, no cookie can be installed on the user’s browser without their consent. This means that scripts of a Facebook Like button, for example, can’t be executed.
As this is quite technical, the best way to handle this, once again, is with a dedicated tool that can do this automatically.
Why is this wrong? Collecting consent is one thing. Keeping a record of consent and preferences is another. The vast majority of Data Protection Authorities across the EU have emphasized this requirement (which stems from the GDPR).
Just like the previous point, this is definitely tricky to implement. The iubenda CMP has a specific tool called the Cookie and Consent Preference Logs which stores proofs of users’ consent preferences. You can retrieve the information at any time via a dedicated dashboard.
Why is this wrong? For example, you could have forgotten to mention in your policy a new technology that is now running and installing cookies on users’ devices.