GDPR consent log: ensuring compliance with CookieMan

Absolutely.
The log is designed to comply with regulatory requirements related to the European Regulation (GDPR) and other regulations.
You can use this link to learn more.

Maintaining a compliant and always easily searchable Consent Log can be a difficult task.
Indeed, it must be considered that visitors can express their consents not only in relation to cookies but also when they decide to subscribe to a newsletter by filling out a form, they are expressing consent.
The Consent Log should contain all of the visitor’s consents, however they have expressed them, in all of the forms they have filled out.
CookieMan makes the Consent Log available automatically.
The Cookie Consent Log is automatically created and made available.
The Registry for forms is easily implemented: you create the forms with whatever tool you want and then integrate a line of code that CookieMan provides and you’re done.

No, there are several legal bases that make the processing of personal and special data of the data subject lawful. Consent is one of the legal bases.
The data controller should first look for other legal bases for which the processing it is implementing is possible. Lacking the support of other bases, it can rest the processing on consent.
The acquisition of consent must respond to precise rules because only then is it lawful.
For this reason, it is essential to have a CMP that can manage the acquisition of consents in a lawful and compliant manner.

The ePrivacy Regulation was adopted in 2017 but for reasons of waiting for entry into force it has been postponed several times and is currently still awaiting entry into force.
The ePrivacy Directive (2002/58/EC, amended in 2009) is still in force.

The ePrivacy Directive continues to regulate the use of cookies, electronic communication, and other privacy issues until the Regulation comes into force
The ePrivacy Regulation is expected to supplement and replace the ePrivacy Directive, but the delay in coming into force causes a regulatory situation in transition.

The adoption of the consent logis part of a broader need on the part of the data controller to be able to provide proof of having received consent from the data subject.
In a website, the data controller is the owner or rather publisher of the site and the data subject is the visitor.
The visitor can give or not give consents to allow or disallow the handling of his or her personal data. He does so through the cookie banner and not only. He or she can also do so through filling out a form, for example, in which the check box to subscribe to a newsletter might be included.
All such consents, or non-consents, expressed by the visitor must be documented in case someone (entitled to do so) comes asking for proof.
To document the choices made by the visitor, a consent log is needed, a list in essence indicating the visitor’s reference and his or her choice regarding a consent he or she could provide or withhold.
Not having a tool to give evidence of the visitor’s choices does not meet many regulations, including the European Regulation (GDPR).

The adoption of the consent log is part of a broader need on the part of the data controller to be able to provide evidence of having received consent from the data subject.
In order to document the choices made by the visitor, a consent log is needed, a list in essence indicating the visitor’s reference and his or her choice regarding a consent that he or she could provide or withhold.
The log should include at least this information:

• who provided consent
• When and how the individual user’s consent was acquired
• The context in which consent was given (e.g., for cookies, newsletter subscription, etc.).
• A reference to the legal documents and conditions in place at the time consent was acquired (if applicable)

At CookieMan consulting the Consent Log is very simple: select the Consent item from the top menu.
The list shows:

• Visitor ID (unique to the visitor found on their cookie banner)
• Info (date and time of collection and information about the form if consent given in a form)
• Consents (consent status by cookie categories or by check boxes in forms)

If you want to learn more click the link.

The adoption of the consent log is part of a broader need on the part of the data controller to be able to provide evidence of having received consent from the data subject.
In a website, the data controller is the owner or rather publisher of the site and the data subject is the visitor.
The visitor can give or not give consents to allow or disallow the handling of his or her personal data. He does so through the cookie banner and not only. He or she can also do so through filling out a form, for example, in which the check box to subscribe to a newsletter might be included.
All such consents, or non-consents, expressed by the visitor must be documented in case someone (entitled to do so) comes asking for proof.
To document the choices made by the visitor, a consent log is needed, a list in essence indicating the visitor’s reference and his or her choice regarding a consent he or she could provide or withhold.
Not having a tool to give evidence of the visitor’s choices does not meet many regulations, including the European Regulation (GDPR).

To learn more use this link.