General working mechanism 

The Secure Privacy Scanner scans your website and identifies all cookies and plugins setting them. You can view a detailed report of your cookies and plugins inside the Scan Report.

Based on the Scan Report, we generate a JavaScript file. This file is unique for each domain. It has all the information regarding the plugins and the origin of the cookies, (domains from which the cookies are inserted) With Automatic Cookie Blocking Secure Privacy will block all cookies except the essential ones from being set until a user has given their consent.

Based on their consent and the categories consented, Secure Privacy will enable those plugins and cookies. By default, all the cookies except essential will be blocked for any website, however, the webmasters can control this behavior by turning on/off the Auto blocking switch.

Every time we scan your website, the JavaScript file is updated with the latest list of plugins and cookies found on your website.


Technical working mechanism

The way it technically works is that each cookie setting script is identified and saved in a unique JavaScript file. The most 'advanced' JavaScript feature that Secure Privacy uses is MutationObserver, which is compatible with all major browsers as well as IE11. The observers registered with Secure Privacy checks the script loading pattern and blocks them until consent is given.

Right now, Auto-Blocking will only work for IFrames created dynamically on the page, such as advertising IFrames that are injected by a JavaScript file. For IFrames embedded directly on the page, for example, some YouTube videos, we recommend following the manual steps to block those IFrames.


Prerequisites

Secure Privacy Auto-Blocking uses your scan results and cookie categorizations to know what to block. If a cookie has not been detected by the website scanner or is not categorized, it will not be controlled by the auto-blocking script.

To ensure a successful implementation of the auto-blocking script, re-scan your site before beginning the implementation and ensure all cookies are categorized.


Blocking mechanism


Pixels - Secure Privacy will automatically block all pixel trackers if the automatic blocking is turned on.
Only upon receiving positive consent from the user, the pixels will be injected into the HTML DOM. For example, a Facebook Pixel will not work until the user accepts the respective consents for it.


Scripts - Similar to pixels, Secure Privacy will also block the scripts to be injected inside the HTML DOM. For example, Google Analytics will not be inserted into your HTML until the user provides consent. This can cause a significant drop in your analytics and tracking of users.


Cookies - Tracking cookies are placed by pixels and scripts. If blocking is turned on, the cookies will not be placed on the user's browser until they have consented. On receiving a consent, Secure Privacy will allow the scripts to place cookies on the user's browsers. Initially, these pixels and scripts will place cookies. Depending on the type of scripts, some more cookies can be placed on users' browsers during their journey of the website. For example, if a user navigates from page A to B, some scripts/pixels may place extra cookies.