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. This file has detailed information on what scripts, pixels, and iframes to block. The list is editable and configurable in the dashboard using the Blocking Configuration screen. You can use this screen to add or remove any custom script that you want to block/unblock. Every time you save this list, the JavaScript file is updated with the latest list of scripts, iframes, and pixels.
NOTE: Automatic Cookie Blocking Secure Privacy will block all cookies except the essential ones from being set until a user has given their consent.
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.
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.
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.
Iframes - The list of blocked iframes can be managed using the Iframe tab on the blocking configuration screen. On all the blocked iframes, SP will automatically block and add an overlay showing that the iframe is blocked. This overlay will also contain a message and a button so that the user can consent to that particular iframe.
How to switch to Auto blocking v2?
You can switch easily from blocking version 1 / 2 by clicking the upgrade button as shown in the image, or alternatively by selecting "Version 2" from the dropdown. You can also choose to do manual blocking using the same dropdown. Note that blocking version 1 supports script blocking only, however in locking version 2 we support scripts, pixels and iframes.
In case sometimes you need to block a new script, you can do it easily using the add configuration wizard. Using this wizard, you can specify the size of the script that you want to block. This type of custom configuration can be useful in situations where our scanning engine correctly identify the source of the script.
