Consent Withdrawal in the TCF Framework

Context

According to TCF 2.2 policy,  a link to resurface the notice should be easily accessible, and users must be able to make a choice just as easily when the notice reappears as they could upon its first display.

POLICY REFERENCES: Appendix B: Policy (C)(f). If a call to action for the user to express their consent for all Purposes and Vendors was provided in the Initial Layer of the Framework UIs used to request the user’s consent (for example “Consent to all”), an equivalent call to action for the user to withdraw their consent for all Purposes and Vendors must be provided in the Framework UI that the user resurfaces (for example “Withdraw consent to all”).

In the first layer of our notice, users can make a choice in one click using:

  • "Agree and close" to accept all, or
  • One of the options to deny consent, such as "Disagree and close", the cross button, or the "Continue without agreeing" link.

To maintain consistency when resurfacing the CMP, users should also be able to update their choices in a single click.

Default behavior for TCF-enabled notices

To fulfill this requirement, we enforce the following behavior for TCF-enabled notices:

  • The option “Enable the 'Agree to all' and 'Disagree to all' buttons” is enabled by default and cannot be disabled.
  • As a result, these two buttons are always present in the second layer of the notice, typically the one displayed when resurfacing the notice to review choices.
  • Clicking either button will apply the selected choices to both purposes and vendors.

 

The save button remains available for users who prefer to make granular choices or update only purpose statuses using the bulk action buttons at the top of the purposes list.

 

The option “Enable bulk actions on top of the purpose list” alone is not sufficient, as the buttons added with this option only update purpose statuses (not vendors). A second click is still required to save the choices.