The Cookiebot CMP Privacy trigger

<script
  type="text/javascript"
  id="Cookiebot"
  src="https://consent.cookiebot.com/uc.js"
  data-cbid="01234567-89ab-cdef-0123-456789abcdef"
  data-widget-enabled="false"
  async
></script>

[{"q":"Is it mandatory to enable the Privacy trigger on my website according to GDPR?", "a":"<p><href='https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32016R0679&from=EN#d1e2001-1-1' target='_blank'>Article 7(3) GDPR</a> states that your website visitors should have the right to withdraw consent at any time and this withdrawal should be just as easy as it was to give consent in the first place. The Privacy trigger allows you to offer this possibility with minimal effort, offering a plug 'n play solution that can be enabled easily by checking the \"Activate Privacy Trigger\" box on your Cookiebot CMP account.</p><p>If you prefer not to activate the Privacy trigger on your website, the possibility to withdraw and/or change consent is still included in the <a href='https://support.cookiebot.com/hc/en-us/articles/360004374474' target='_blank'>Cookie Declaration</a>. Alternatively, you can construct your own mechanism for allowing users to withdraw consent: <a href='https://support.cookiebot.com/hc/en-us/articles/360003798814' taget='blank'>How can the user change or withdraw a cookie consent?</a></p>" },{ "q":"Will there be a CCPA version of the widget?", "a":"<p>The CCPA version of the Privacy trigger is still in development and will be released at a later time. This will include the extra \"do not sell my personal information\" option. You can find more information on CCPA here: <a href='https://www.cookiebot.com/en/ccpa-compliance/' taget='_blank'>California Consumer Privacy Act</a> and <a href='https://support.cookiebot.com/hc/en-us/articles/360010952259' taget='_blank'>How to set up your CCPA configuration</a>.</p>" },{ "q":"Do I still need the cookie declaration on my website, if I activate the Privacy trigger?", "a":"<p>The Privacy trigger can replace the cookie declaration as a means of complying with these key parts of <a href='https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32016R0679&from=EN#d1e5663-1-1' target='_blank'>GDPR art. 7(3)</a>: <i>\"The data subject shall have the right to withdraw his or her consent at any time\"</i> and <i>\"It shall be as easy to withdraw as to give consent.\"</i></p>" },{ "q":"Why is the date and consent key hidden?", "a":"<p>To check the exact date and time and consent ID of the provided consent, you can click the \"show details\" link in the widget. These have been hidden behind a link in order not to clutter the users' view of the current consent state.</p>" },{ "q":"Mobile design: can we make the Privacy trigger smaller?", "a":"<p>The size on mobile is full width, but only takes up the screen size it needs to show the content in its height. On older phones with smaller screens, this might end up in taking up the whole screen and your users having to scroll within. We can not really make it any smaller than it already is, because of usability.</p>" },{ "q":"Why is the preview not available in the manager?", "a":"<p>The preview is not enabled for the Privacy trigger at this time, but will be enabled with a future release.</p>" },{ "q":"Why is it not possible to change consent from <i>within</i> the Privacy trigger?", "a":"<p>In order to change an original consent state, users are presented with the cookie banner again, which provides the full overview of cookies and trackers in use. As users should be able to make a fully informed consent choice every time, the full cookie banner will re-appear upon clicking the \"change consent\" button in the Privacy trigger.</p>" },{ "q":"Is the Privacy trigger available for Free plans?", "a":"<p>Yes, the Privacy trigger is also included in our Free plans, although customization options are only available in Premium accounts.</p>" },{ "q":"Will the Privacy trigger automatically be enabled for new domains groups?", "a":"<p>The Privacy trigger will not be enabled automatically on existing domain groups. It will however be enabled by default on newly created domain groups. Disabling the Privacy trigger again can easily be done: <a href='https://support.cookiebot.com/hc/en-us/articles/4406571299346' target='_blank'>How to enable/disable the Privacy trigger</a>.</p>" },{ "q":"Can I remove the Cookiebot CMP branding from the Privacy trigger?", "a":"<p>It is not possible to hide the Cookiebot CMP branding via your account' settings, but you can use CSS overrides in order to accomplish this. See also the Swift banner guide on how to do this: <a href='https://cookiebot.zendesk.com/hc/en-us/articles/4403482346514' taget='_blank'>Remove Cookiebot CMP branding from Swift banner</a>.</p>" },{"q":"What Content Security Policy (CSP) directives are required to enable the Privacy trigger?", "a":"<p>We retrieve the configuration for the Privacy trigger using XMLHttpRequests to https://consentcdn.cookiebot.com/, so you'll need to allow <code>connect-src 'self'</code> <code>https://consentcdn.cookiebot.com</code>. Please see our article on <a href='https://support.cookiebot.com/hc/en-us/articles/360018907220' target='_blank'>Cookiebot and CSP</a> for more information.</p>"}]