Block Until Consent? Good.
Block Forever? Sometimes Better.
Extensions shouldn’t phone home by default. v2.0.2 lets you say “no” - for good.
Most of us install plugins to solve problems. Fewer of us expect them to quietly call back to third-party servers - counting every page view, fingerprinting devices, or dropping pixels that don’t serve our users. That’s the “phone-home” problem.
The law is clear about the before part: no access to a user’s device without prior, informed consent (ePrivacy Directive 5(3)). But the spirit goes further: collect less. Favor the first-party path. Keep only what you need.
That’s why today we’re releasing Permanent Block. It’s a tiny control with a big message: if a third-party isn’t essential - and if sending data off-site isn’t in your users’ interests - you can stop it completely. Not “until consent.” Not “maybe later.” Completely.
Missed our last update?
What’s New in CMP v2.0.2?
Permanent Block in Privacy Shield
Until now, Consent Shield let you block third-party scripts “until consent.” That remains the default. But sometimes, “never” is the right answer. Permanent Block allows you to mark specific plugins, domains, or path rules so they will never load – even if a user clicks “Accept All.”
How it works:
- In Consent Shield, select a plugin or add a domain/path rule.
- Choose Block permanently.
- Save your setting. From that moment, the target never loads.
- Optional: Run a post-consent scan to confirm no data leaks remain.
It’s simpe, deliberate, and logged with clear UI badges, confirmation dialogs, and admin audit entries so policy changes are visible.
Why It Matters:
- Data minimization by design
If a third-party isn’t essential, you can keep your users’ data where it belongs: with you. This aligns directly with GDPR principles and ePrivacy Directive 5(3). - First-party strategy
Rely less on external vendors, reduce cross-border transfer risks, and strengthen your data independence. - Real enforcement, not theatre
Too many sites still initialize third-party stacks before consent. Permanent Block, combined with pre- and post-scans, prevents these silent leaks and keeps you audit-ready.
Use it For:
- Telemetry scripts bundled into otherwise useful plugins.
- Analytics beacons you’ve replaced with first-party analytics.
- Embeds that set identifiers by default.
Pair it with our Privacy AI Advisor configuration with pre/post scanning and first-party Analytics to run a site that respects people, reduces risk, and still learns what matters. That’s the web we’re building: privacy-first, first-party by default.
How to Get AesirX CMP for WordPress
Get AesirX CMP for WordPress (14-day trial) and start marking the noisy stuff Permanent. Your users - and your future audits - will thank you.
➡ Download here: AesirX CMP for WordPress – GitHub Releases
Explore our ecosystem at: https://www.aesirx.io
