Hi @alarch,
Thank you! When consent is revoked, further placement of cookies will be blocked on new pages and visits. Because cookies are stored in the browser, the only way to immediately delete those cookies is by clearing the browser as a visitor.
If the cookies are not cleared by the visitor it will depend on the retention period per cookie, every session, every day or sometimes even years.
This means reloading the page wouldn’t retroactively change which cookies are already placed, but will block all future cookies.
Hope this helps. Let me know if it’s unclear.
Regards Aert
I’d like to add that, in earlier versions of Complianz, this feature was included.
The problem is that, like @aahulsebos describes, cookies are not cleared on this reload. While it would be possible to clear cookies which are placed on your own website’s domain, this would not clear cookies from Facebook, Twitter, etc, because these services place their cookies on their own domain (e.g. facebook.com), which is why companies like Facebook can track you across multiple websites: on each site they can access the cookies on their own domain in an iframe. And these cookies are the first that should be deleted on revoke.
Because of this technical limitation it is not possible to actually clear cookies on revoke, and additionally the lesser user experience the reload would cause, we have decided to drop this feature.
Maybe an alternative would be to notify the user of the need to clear the browser cache to prevent further tracking.
Thread Starter
alarch
(@alarch)
Thanks for the very prompt replies. That’s fine, I can adjust the user notifications as you suggest.
Out of interest, what I’m finding is that after revoking consent a simple reload of the page is sufficient to allow Google and Twitter cookies to disappear from the cookies list in Firefox, as displayed using developer tools. So perhaps a page re-load might work for some websites and not others? A possible optional feature?
@alarch @rogierlankhorst
This will depend on the website, the browser (Firefox has a different way of storing cookies) and the settings per browser, plus the cookies set per 3rd party. But these are interesting variables to have a look at. I will try to recreate the Firefox and the Google/Twitter disappearance. Interesting, thanks for letting us know!
Regards Aert
Interesting behaviour! I seem to be getting similar results in Chrome, but with different services. For example, Facebook disappears after reload, but Google doesn’t as opposed to your results in Firefox.
Because I don’t think a page reload will actually clear the cookies, I suspect that the disappearance of the cookies doesn’t mean the cookies aren’t there anymore. I think it’s more likely that the display only shows the available frames in the websource.
This needs further investigation.
Thanks for your input. We’ll get back to you on this.
Thread Starter
alarch
(@alarch)
To be more precise, it’s the Google domain cookies that disappear on reload after allowing functional cookies only – not the Google Analytics cookies associated with the website domain. The Twitter cookies disappear on Chrome, Firefox and Opera. Whether or not it’s a reporting issue, as you suggest, I’m not able to say.
Hi @alarch,
For a quick update, we can see the disappearance. The question now arises if they are actually disabled or just removed from the Chrome/Firefox console.
Thanks again!
Hi @alarch,
We are preparing for 3.0 with above integration likely to be added. Would you be interested to test our Premium 3.0 Beta release?
If so, please leave your contact information at complianz.io/contact. If not, Free 3.0 will be released when our Beta release is bugfree in a couple of weeks.
Let me know!
Hi @alarch your suggestions is added to our next release (3.0). Thank you! We appreciate any feedback we can get to improve our plugin. If you still want to join our Beta Release. Let us know.
For now I’m closing this topic, because we have added the solution!
Regards Aert
