I guess that makes too much sense.
I guess that makes too much sense.
I recommend enabling the EasyList Cookie blocking list in the adblocker of choice (i.e. uBlock Origin). Its not enabled by default, so check your settings (Edit: This will block the consent popups, not the cookies).
I personally would prefer to accept all cookies, and take responsibility for keeping separate cookie jars as needed.
I'd rather something that auto-rejected, so I don't use it, but it exists.
This bit is actually the opposite. All tracking _must_ be opt-in, therefore by blocking the pop-up and not opting-in the website cannot track you.
It's only for the websites which are broken when not opting-in that it accepts the policy (which AIUI is itself a violation of the GDPR).
The lack of the header should indicate that the user denied consent to be tracked.
How should a Transparency & Consent String be stored?
In version 1 of the TCF Specifications the consent string was specified to be stored as either a 1st party cookie for service-specific consent or a 3rd party cookie for global consent. In version 2 of the TCF Specifications, the storage mechanism used for service-specific TC Strings is up to a CMP, including any non-cookie storage mechanism. However, global TC Strings must still be stored as cookies under the consensu.org domain.[0]
Pretty much no website uses it.
[0] https://github.com/InteractiveAdvertisingBureau/GDPR-Transpa...