PrivacyShield GDPR+

• Cookie banner with equally prominent Accept and Reject buttons.
• The visitor’s choice is remembered (about 6 months) and can be changed at any time through the “Cookie settings” button or the Cookie settings shortcode.
• Consent log kept as evidence (choice, rule version, plugin version, pseudonymous visitor hash) and pruned automatically (default 18 months).
• Data request form (

Important limitations (please read)
• This plugin automatically holds back a specific, known list of trackers — Google Analytics (gtag.js/analytics.js/ga.js), Meta Pixel, and Google Ads/doubleclick — wherever they appear in the rendered page, with no template edits needed. It does not scan or block arbitrary third-party scripts in general: anything it doesn’t recognise (a tracker not on that list) still loads immediately unless you mark it up yourself as described in the FAQ below. Turn auto-blocking off, or extend the recognised list, under PrivacyShield → Settings / the ps_auto_blocker_patterns filter.
• Tags inside a Google Tag Manager container are not blocked. The gtm.js loader is deliberately left alone, because a container can mix tags that need consent with tags that don’t. A Meta Pixel added as a Custom HTML tag in GTM, for example, will still fire. Give such tags a consent requirement inside GTM itself (the tag’s Consent Settings), alongside the Consent Mode v2 signals this plugin sends.
• Scripts added by JavaScript after the page has loaded are not intercepted. Automatic blocking rewrites the HTML your server sends, so it cannot catch a tracker whose loader is created at runtime by other JavaScript (an external script file, a tag manager). Scripts that are already held back (type=”text/plain” with data-ps-category) do run later, once the visitor consents, including ones inserted after load.
• Embeds are not blocked. YouTube, Google Maps and other iframes/embeds load immediately and there is no click-to-load placeholder yet. Compatibility with individual page-cache plugins has not been tested one by one; the banner itself is written to work behind a page cache.
• It is not a Google-certified CMP and does not implement IAB TCF. If you serve Google ads (AdSense, Ad Manager) to users in the EEA, UK or Switzerland, use a certified CMP.
• The generated privacy policy text is a starting point, not legal advice.