[ad_1]
Hi again,
After researching a little on the subject on my own, I think I have understood what is happening and I leave the answer in case it is useful to other users, since it is a quite complex topic imho:
The cookie is still present because it is not possible to delete certain cookies from third party services because it would represent a security risk if someone could manipulate data from other domains (common examples are Facebook, Google, etc). What Complianz does to solve this problem is that all scripts rejected in a revocation (when Reject button is pressed), are set back to “text/plain” and can no longer connect to the third party domain.
Checking this URL is a great idea.
The only question I have left is: does this behavior comply with GDPR and spanish regulations?
Hello @path0,
As long as that specific cookie is detected in the Cookie Scan, and the list of cookies has been “Synchronized with CookieDatabase” under the Cookie Descriptions part of the Wizard:
That should make this specific _ga_HQG**** cookie appear under Cookie Descriptions. After which this cookie should appear as a Statistics cookie in the LocalStorage item cmplz_cookie_data, and shredded in case the currently given consent doesn’t match the category required for that cookie.
Please note the difference between ‘revoking consent’ and actually removing previously set cookies from the browser of your visitor. Revoking consent will result in previously accepted services getting blocked once more. The CookieShredder goes a step further by additionally removing those previously set cookies from the visitor’s browser, which is optional in most instances.
(Note: the above must not be regarded as legal advice, as I am not a qualified legal professional as well as that the Forum Guidelines do not allow for this.)
Kind regards,
Jarno