Manage Cookie Consent Easily

The process of collecting cookie consent includes clearly and explicitly informing the user of the cookies and similar technologies you run on your site/app, their purposes, the user’s right to grant or refuse consent, and how they can exercise that right.

The cookie consent must be informed, explicit, and given via an unambiguous opt-in action.

Specifically, you must:

• display a clearly visible cookie banner/ notice at the user’s first visit (you can read what the banner should contain here);
• provide a link in the banner to a more detailed cookie policy;
• display a command to accept all cookies;
• display a command to reject all cookies;
• add a link to a dedicated area where users can make any granular choice as to the functionalities, the third parties and the categories of cookies to be installed;
• block all non-exempt cookies and scripts from being run until after consent is received;

No, the Cookie Law does not require that you list and name individual cookies. You are instead explicitly required to clearly state their type, purposes, and if they are third-party trackers, you shall also indicate the third party who is managing them and link to the relevant third-party privacy/cookie policy.

The Cookie Law does not require that you list and name individual cookies. However, you are required to clearly state their categories and purpose.

This decision by the Authority is likely deliberate as to require this would mean that individual website/app owners would have to constantly monitor every single third-party cookie, looking for changes that are outside of their control. This would be both unreasonable and likely unhelpful to the average user.

Active consent refers to consent that is based on the user being clearly and sufficiently informed of the purpose, categories and use of the cookies being used by your website, and that is indicated by an explicit affirmative action.

Subject to the local authority, these active behaviors may include continued browsing, clicking, scrolling the page or some method that requires the user to actively proceed.

This is somewhat left up to your discretion as according to the general guidelines no specific mechanism (e.g. checkboxes) is mentioned as mandatory: provided that your method facilitates active consent, however, it’s worth noting here the because the ePrivacy is, in fact, a Directive, the specifics of how requirements should be met are heavily dependent on individual Member State law.

For this reason, we give you the option to easily enable or disable the Privacy Controls and Cookie Solution’s “scroll to consent” feature should the particular Member State law require it.

The Cookie Law itself does not require that records of consent be kept, but instead indicates that you should be able to prove that consent occurred — even if that consent has been withdrawn. However it’s important to note that some EU Data Protection Authorities in alignment with the GDPR, now require that records of consent – rather than simply proof – be kept. If this applies to your particular situation, you will need to maintain valid records of consent.