How to block cookies and trackers with JavaScript rewrite
This guide explains you how to block cookies and plugins with Secure Privacy using Javascript rewrite.
To block cookies and trackers you need to change the attributes of the script tags on your website. Follow these steps to change the attributes.
- Apply the attribute sp-consent="PLUGIN NAME" to the script/image tags on your website. Depending on where you have installed the plugins, this may be inside a module, plugin or directly on your website. Make sure that you write the exact plugin name, which appears on your Scan Report.
- On script tags change the attribute 'type' from 'text/javascript' to 'text/plain'.
- If you are using a pixel tracker (image trackers), then change the attribute “src” from “src” to “data-src”.
Here is an example of how it would look after you have modified a Google Analytics script.
Normal script tags look like this:
<script type="text/javascript"> code…
</script>
Using script type re-writing, you need to change the scripts to:
<script type="text/plain" sp-consent="Google Analytics"> code…
</script>
ISO 42001 Implementation: A Practical Guide to Building an AI Management System (AIMS)
Your organization deploys AI for credit scoring, customer service automation, and predictive analytics. Your data science team builds models. Your security team secures infrastructure. Your legal team reviews contracts. And yet, when a regulator asks "how do you govern AI risk across its lifecycle?" or "demonstrate your controls for algorithmic bias," no single team owns the answer — because AI governance exists in fragments, not as an integrated management system.
NIST Privacy Framework: The Complete Enterprise Guide to Privacy Risk Management
Your organization collects customer data across web, mobile, and IoT platforms. Your cybersecurity team secures that data against external threats. Your legal team drafts privacy policies. And yet, when a hospital employee with authorized system access shares a celebrity patient's records with media, or when a properly secured billing system merges two patients' data due to a configuration error, no existing control prevented the privacy harm—because the risk came from authorized data processing, not a security breach.
California DROP Act (CPRA) 2026: Compliance Requirements and DSAR Automation
California just made consumer privacy deletion requests unavoidable at scale. Starting August 1, 2026, every registered data broker must connect to a state-operated platform, retrieve consumer deletion requests every 45 days, and process them—automatically, verifiably, and repeatedly. Miss a deadline and face $200 per-request daily penalties. Fail to propagate deletions to vendors and face enforcement scrutiny that has already produced settlements exceeding $1.5 million.
- Data Protection
- Privacy Governance