zubi.ai

Consent Management

Based on the principle of privacy by design, Zubi utilize a consent framework to determine what data to collect, cookies to write and the use of the data collected.

Overview

Zubi operates with active or inactive data storage and on three different privacy modes. By default, data storage is turned off which means that Zubi do not store or process any data. This is useful for customers that are only using client side integrations, but Zubi in general require data storage and processing to be useful beyond this. In addition to the data storage settings, the privacy modes determine most around data capture, use and retention within the Zubi platform.

Privacy mode: Off

The Zubi consent management and privacy mode can be turned off. While not recommended there are occasions when our customers manage consent and privacy using some external service that do not require the consent and privacy features to run within Zubi.

Privacy mode: On (Default)

By default, the privacy mode is turned on to prevent cookies from being set, PII data from being collected and client side integrations from running if there is no consent given by the user. When no consent is provided this mode runs exactly as the Strict mode described below, and when consent is provided it runs according to the consent given.

Zubi runs on two consent categories, Analytics and Marketing . The Zubi platform itself requires consent for Analytics, and some of the integrations, like Google Analytics, requires consent for Marketing in addition to the Analytics consent.

Privacy mode: Strict

When Zubi operates in Strict mode, it does not set cookies (other than a consent cookie and a ping cookie, read more about them here ) and it does not collect and store any PII data. In addition, client side integrations do not run in Strict mode as they generally utilize cookies to run. The Strict mode is generally used by customers that use Zubi for website analytics without requirements on insights into returning visitors or statistics based on aggregation per individual visitor, as such statistics require the use of cookies and UUIDs.

There are currently three ways to provide and manage consent in Zubi. You can either use one of the available integrations to automatically inherit consent status from an external tool, or setup Zubi using a manual control in one of the many consent managers that support custom scripts. And for developers, you can set consent using javascript events.

Zubi integrates with many of the leading consent management tools to simplify the privacy work for our customers. Use the tool you already use and ask Zubi to simply hop on the train.

A popular consent management platform that contains all the tools you need to make your website comply with the latest privacy regulations. Zubi automatically adheres to the platform when the integration is activated. Read all about Cookie Script here .

Generate a fully customizable cookie banner, record user consent and manage all your cookie compliance needs in one place. Zubi automatically adheres to the platform when the integration is activated. Read all about Cookie Yes here .

Cookiebot

Check if your website’s use of cookies and online tracking is compliant with GDPR and the ePrivacy Directive (ePR). Cookiebot CMP helps make your use of cookies and online tracking compliant. Zubi automatically adheres to the platform when the integration is activated. Read all about Cookiebot here .

CookieFirst

CookieFirst offers automated cookie consent, periodic cookie scans, an automated cookie policy generator in 40+ languages, integrations with Google Tag Manager and Google Consent Mode and much more. Zubi automatically adheres to the platform when the integration is activated. Read all about CookieFirst here .

The Customer Privacy API is a browser-based, JavaScript API that you can use to register consent and query data processing permission in Shopify. Read all about it here .

Cookie Notice provides a simple, customizable website banner that can be used to help your website comply with certain cookie consent requirements under the EU GDPR cookie law and CCPA regulations and includes seamless integration with Cookie Compliance to help your site comply with the latest updates to existing consent laws. You may easily include the Zubi script in this plugin to only run Zubi when proper consent is given. See the General section below for more information.

Prepare your website for cookie consent requirements related to GDPR, CCPA, DSGVO, EU cookie law and notice requirements with this incredibly powerful, easy-to-use, well supported and 100% free WordPress plugin. You may easily include the Zubi script in this plugin to only run Zubi when proper consent is given. See the General section below for more information.

General

Many consent managers on platforms such as Wordpress enables you to manually add scripts that should run only when consent is given (or better yet, when certain consents are given). Zubi can be added to such solutions making it run on the same consent as the tool itself.

For example, Zubi can be added to many consent plugins for wordpress by adding the below script to the custom script section.

      

        

  /* Consent to both Analytics and Marketing */

<script type="text/javascript" src="https://assets.zubitracker.io/v1/tracker/latest/consent/remote_consent.js"></script>


  /* Consent to Analytics only */

<script type="text/javascript" src="https://assets.zubitracker.io/v1/tracker/latest/consent/remote_consent_analytics.js"></script>


  /* Consent to Marketing only */

<script type="text/javascript" src="https://assets.zubitracker.io/v1/tracker/latest/consent/remote_consent_marketing.js"></script>

Javascript Events

You may control the Zubi consent settings using Javascript Events that dispatch when the user updates their consent. Zubi will store the consent sent in a cookie and will update it as needed when new events are received.

      

        

  /* Consent to both Analytics and Marketing */

window.dispatchEvent(new Event("zlConsent"));


  /* Consent to Analytics only */

window.dispatchEvent(new Event("zlConsentAnalytics"));


  /* Consent to Marketing only */

window.dispatchEvent(new Event("zlConsentMarketing"));


  /* Reject consent to both Analytics and Marketing */

window.dispatchEvent(new Event("zlReject"));


  /* Reject consent to Analytics only */

window.dispatchEvent(new Event("zlRejectAnalytics"));


  /* Reject consent to Marketing only */

window.dispatchEvent(new Event("zlRejectMarketing"));