Table of Contents |
---|
Overview
...
In order to have full compliance, please link Snigel in your privacy policy page. This closes the chain in terms of data flow.
...
We use a third-party to provide monetization technologies for our site. You can review their privacy and cookie policy
here
Html tag example:
Code Block |
---|
<p> We use a third-party to provide monetization technologies for our site. You can review their privacy and cookie policy <a href="https://www.snigel.com/privacy-policy/">here</a>. </p> |
...
To be fully compliant with GDPR and CCPA, the publisher must provide a way for the user to change the current privacy settings in the CMP. The recommended way is to add a small section in their own privacy policy page with a button linking to the CMP API call showGUI. This means that when a user wants to change their privacy settings, he must head up to the privacy policy page and click the button to reopen the CMP GUI.
...
CCPA is by default a button floating on the side of the screen. Snigel recommends implementation with a link instead. To implement the link the only thing that's required is to create a new div, on an already existent element of the page (eg: footer), with the message that should be associated with the CCPA opt-out (eg: "Do not share my Personal Information."). The style of the div can be changed as needed, but the id="ccpa"
is required. The id can be changed by the account manager on request.
...
Add an explicit notice to the privacy policy for the California Consumer Privacy Act
Note
The display:none style needs to be applied inline to the element, otherwise it will not be visible when the CCPA is triggered.