Compliance by Hu-manity.co vs FAZ Cookie Manager

Compliance by Hu-manity.co (formerly known as Cookie Notice) provides a simple, customizable website banner that can be used to help your website comply with cookie consent requirements under the EU GDPR, CCPA, and other data privacy laws — with seamless integration with Cookie Compliance to help your site comply with the latest updates to existing consent laws. Cookie Compliance is a fully featured Consent Management Platform (CMP) that provides automated compliance features and enhanced design controls in a state-of-the-art web application. Cookie Compliance enables websites to take a proactive approach to data protection and consent laws. It is the first solution to offer Intentional Consent, a new consent framework that incorporates the latest guidelines from over 100+ countries, and emerging standards from leading international organizations like the IEEE and European Center for Digital Rights (noyb.eu). Cookie Compliance provides a beautiful, multi-level experience and includes new choices and controls for site visitors to better understand and engage in data privacy decisions. Our Cookie Compliance web application introduces a more ethical, proactive way to capture and manage consent. This early version of the emerging Intentional Consent framework is a result of Hu-manity.co’s ongoing work with top Fortune 500 companies, governments, and standards organizations, who believe that the imbalanced relationship between consumers and corporations is unsustainable when it comes to data privacy and consent online. We are making it available for all website owners and operators who share this belief and support our mission to eliminate the dark patterns in online consent. Matt Sinderbrand – Chief Platform Officer, Hu-manity.co Compliance (plugin only) Compliance by Hu-manity.co provides a simple, customizable website banner to help your website comply with certain cookie consent requirements. Banner features: Customizable notice message Consent on click, scroll or close Multiple cookie expiry options Link to Privacy Policy page WordPress Privacy Policy page synchronization WPML and Polylang compatible SEO friendly Cookie Compliance (plugin + web application) Cookie Compliance gives you access to the most up-to-date formatting guidelines and technical compliance requirements for over 100 countries and legal jurisdictions. Banner features: Intentional Consent provides 3 equal buttons to give site visitors the ability to accept none, some, or all cookies through packaged choices called Data Access Levels. Data Access Levels improve consent conversion and eliminate the dark pattern of deceptive, non-equal choices in the first layer. Complies with equal choice principle prescribed under GDPR and other data protection laws. Consent duration selector gives visitor control over how long their consent remains valid for your site. Enables your site to align with recent guidelines from EU Data Protection Authorities, which state that cookie consent should be valid for no longer than a period of 6 months. Cookie purpose categories make it easy for website visitors to customize their consent by category. Complies with affirmative, opt-in consent requirements prescribed under GDPR and other data protection laws. Consent metrics displays the visitor’s consent record and a list of blocked / allowed 3rd parties directly in the expanded level of the banner. Complies with latest guidance from EU Data Protection Authorities like CNIL (France) and ICO (UK). Customizable Privacy Paper provides helpful information to improve visitor comprehension and understanding of the data sharing risks and benefits. Allows you to summarize core components of your sites privacy notice and aligns with the informed principle prescribed by GDPR rules for valid consent capture. Configurable Privacy Contact allows you to provide contact information for a business’ data privacy admin, as well as helpful links to data subject request forms and other data privacy resources. Aligns with the informed principle prescribed by GDPR rules for valid consent capture. Web Application features: Consent analytics dashboard shows event data for number of visits and provides a “trust score” to help you track how site visitors are setting their consent. Make adjustments to your banner to improve your cookie acceptance rate and monitor progress via the consent activity graph. Default configurations for GDPR, CCPA and more help to remove dark patterns and allow for quick and easy deployment of the consent banner without any guesswork. Customize the design of any default configuration to match the look and feel of your site. Automatic script blocking blocks all non-essential cookie scripts and iFrames by default and complies with valid consent rules under GDPR and other data protection laws; in order to be compliant, your site must record visitor consent before setting or sending cookies. Google Consent Mode ensures that your website can still gather valuable insights and perform effectively while respecting users’ privacy preferences by dynamically adjusting the behavior of Google services according to user consent. Facebook Consent Mode allows your website to measure the impact of your ads on Facebook, track website activities and conversions and automatically deliver ads to Facebook if the user has agreed to. Consent record storage automatically stores a record of each consent and makes these records available for export. Complies with proof-of-consent requirements prescribed under GDPR and other data protection laws. Multilingual support automatically translates all banner text strings and allows you to provide custom translations for every text field to ensure visitors get a consistent consent experience. Multidomain management allows you to manage additional Free or Professional domains under a single account and enables you to customize banner configuration and design for each domain independently. Cookie Compliance proactive approach: For all businesses, the resources required to stay ahead of the latest regulations increases with the passage of each new law. With enforcement of compliance violations increasing daily, we believe it is critical for us as a trusted consent vendor to do everything in our power to help you stay ahead of these laws and remove the risk to your business Cookie Compliance covers all current and upcoming regulations: GDPR (EU) ePrivacy Directive (EU) ePrivacy Regulation (EU) PECR (UK) LGPD (Brazil) PIPEDA (Canada) PDPB (India) CCPA (California, US) VCDPA (Virginia, US) Colorado Privacy Act (US) CPRA (California, US) Cookie Compliance incorporates all recent formatting guidance: European Data Protection Supervisor (EDPS) ICO (United Kingdom) CNIL (France) GPDP (Italy) BfDl (Germany) AEPD (Spain) European Center for Digital Rights (noyb.eu) Cookie Compliance targets dark patterns Dark Patterns are user interface (UI) techniques that push site visitors to make decisions (such as agreeing to the installation of cookies on their devices) that they might not otherwise make. The most common Dark Pattern is the lack of an equal “reject all” button on the first layer of the consent notice. Dark Patterns are explicitly banned under GDPR and other data protection laws. As a part of our proactive approach, Cookie Compliance is configured by default to prevent Dark Patterns through our unique Intentional Consent design. Privacy Compliance by Hu-manity.co is a Consent Management Platform client. Depending on how you use it, the plugin may send data to Hu-manity.co services on your behalf. This section describes what data leaves your WordPress server and when. It is kept up to date as the plugin evolves; material changes are noted in the changelog. Plugin-only mode (Banner Only / Basic) If you install the plugin and choose “Banner Only” in the Welcome screen — or never open the Welcome screen at all — the plugin operates entirely on your WordPress site. No account is created and the plugin does not initiate calls to Hu-manity.co services. Connected mode (Free or Professional) If you create a Cookie Compliance account from the Welcome screen (or log into an existing one), the plugin connects your site to the Hu-manity.co platform. While connected, the plugin sends data over HTTPS to Hu-manity.co’s platform services (hosted under *-api.hu-manity.co) for the following purposes: Account sign-up and sign-in, and registering your site as an application. Fetching and updating your banner configuration. Fetching consent analytics and individual consent records shown in the Audit Trail. Processing subscription payments (Professional plans only). The data sent depends on the feature you are using and typically includes: Account-identifying data such as the email address and password used for sign-up or sign-in. Site-identifying data such as your site’s URL, title, description, and language. Application credentials (App ID and Secret Key) issued to your site at registration, included with subsequent platform requests. Subscription and billing data for Professional plans, such as the selected plan identifier and a one-time payment token described below. Integration telemetry such as the plugin version and which admin interface (React or Legacy) you are using, sent as HTTP headers so we can understand integration adoption and support the plugin. Operational metadata such as the timestamp and locale of a request, as is normal for HTTPS API calls. As the plugin evolves, additional non-personal fields of the same categories listed above may be sent to support new features. Material changes are noted in the changelog. Payments (Professional plans only) Payment card details are collected by Braintree’s hosted-fields SDK running in your browser and are tokenized there. The plugin and Hu-manity.co servers do not receive raw card data. A one-time, non-replayable Braintree token is sent to Hu-manity.co’s platform to create the subscription. Deactivation feedback If you deactivate the plugin and fill in the optional deactivation feedback form, the reason you select, any free-text comment you type, and your site URL are sent once to Hu-manity.co so we can improve the product. Submitting the form is optional; clicking “Skip” sends nothing. This applies to both Plugin-only and Connected modes. The banner shown to your site visitors The consent banner shown to your site visitors is served from cdn.hu-manity.co/hu-banner.min.js. When a visitor interacts with the banner, the banner script (running in the visitor’s browser, not the plugin) communicates directly with Hu-manity.co services to record the consent decision — this is what makes consent records available to you in the Audit Trail. This data flow is between the visitor’s browser and Hu-manity.co and does not pass through your WordPress server. Because these requests originate in the visitor’s browser, the visitor’s IP address is visible to Hu-manity.co as part of standard HTTPS network handling. Local state set by the plugin The plugin stores operational state in three places. None of this is transmitted to Hu-manity.co: On your WordPress server (options and transients) — for example, a welcome-modal dismissal timestamp (cookie_notice_welcome_dismissed) and short-lived caches of API tokens and configuration. In the admin user’s browser (localStorage) — for example, first-run setup flags such as cn_setup_wizard_complete_* and cn_has_platform_config_*. In visitor browsers (a short-lived hu-form cookie, 5 minutes) — set when forms with consent integration are submitted. Used locally by the form-consent flow. As the plugin evolves, additional keys may be stored in any of these locations. They remain local state on your site or in the user’s browser — not data sent to Hu-manity.co. Material changes to this pattern would be noted in the changelog. Data the plugin does not send The plugin does not transmit visitor IP addresses, cookies, page URLs, or page content as data fields. IP addresses are, as with any HTTPS request, visible to the receiving server as part of standard network handling. The plugin does not transmit the content of your posts, pages, users, or WordPress database. The plugin does not send data to third parties other than Hu-manity.co and, for Professional plan payments, Braintree (a PayPal service). Service providers Hu-manity.co / Cookie Compliance — primary service provider. Terms of Service: https://cookie-compliance.co/terms-of-service/ Privacy contact: https://cookie-compliance.co/documentation/privacy-contact/ Braintree (a PayPal service) — processes Professional plan signups initiated from the plugin (not invoked for Basic or Free). When you manage your subscription from the Cookie Compliance web application, additional payment gateway providers may process your billing information. Hu-manity.co’s email subscription service — receives your account email address and name to manage newsletter and operational email preferences. You can unsubscribe at any time via the email footer or by deleting your account. Account and consent data is processed in the European Union (AWS Ireland region). Hu-manity.co’s public marketing websites (hu-manity.co, cookie-compliance.co) are hosted separately in the United States. How long we retain your data Plugin-side caches on your WordPress server (API tokens, subscription data, configuration) are short-lived, with TTLs typically up to 24 hours. The visitor hu-form cookie expires after 5 minutes. On the Hu-manity.co platform, account information and consent records are retained as long as your Cookie Compliance account is active, and are removed when the account is deleted or via an erasure request. What rights you have over your data Stop further sends. Deactivate the plugin from the Plugins screen — no further plugin-initiated API calls will be made. Export consent records. Site owners can export cookie-consent and privacy-consent logs as CSV from the Cookie Compliance web application. Delete your account and all associated data. The Cookie Compliance web application has an account-deletion flow. Triggering it cancels active subscriptions, deletes your apps and banner configuration, removes your consent records from the platform, and nullifies free-text personal data before deleting the account. Erasure of visitor data (GDPR Article 17 / CCPA Delete). To request erasure of a specific visitor’s records (by email, session ID, IP, or consent ID), contact Hu-manity.co via the privacy contact page above. Hu-manity.co processes the request and erases the matching records from its storage systems within 30 days, in line with GDPR Article 12. Manage consent (visitors). Site visitors can adjust their consent at any time through the consent banner.

Tired of cookie consent plugins that lock essential features behind paywalls, require cloud accounts, or send your visitors’ data to third-party servers? FAZ Cookie Manager is a WordPress plugin that helps you implement cookie consent and privacy workflows for international regulations — completely free, with no strings attached. No account to create. The plugin requires no cloud service connection. Basic features like consent logging and geo-targeting are included — no premium plan needed. Core consent features run on your own server, and you own all your data. Why FAZ Cookie Manager? Most cookie consent plugins follow the same pattern: a free version with crippled features, and a paid tier starting at $10-50/month that unlocks what you actually need (cookie scanning, consent logs, Google Consent Mode, IAB TCF). FAZ Cookie Manager breaks that model: Cookie scanner — Scans your site directly from your browser. No external service, no API limits, no waiting. Cookie Policy generator (NEW in 1.16.0) — Build a jurisdiction-aware Cookie Policy page directly from your admin. Pick GDPR / CCPA / LGPD, fill in your company details, and publish via the [faz_cookie_policy_complete] shortcode. Output is multilingual (en, it, fr, de, es, pt-BR, bg), pulls the live cookie inventory from the scanner, and ships with a non-removable disclaimer that the templates are starting points, not legal advice. The standalone [faz_cookie_table] shortcode (and the matching Gutenberg block) still works for embedding just the cookie list. Consent logging with CSV export — Every consent is recorded locally in your database. Export anytime for audits. Google Consent Mode v2 — Sends all 7 consent signals to Google tags. No premium required. IAB TCF v2.3 — Full Transparency and Consent Framework API and UI, built in. To operate as a recognised CMP in the IAB framework you must enter your own registered IAB Europe CMP ID; without one the TCF interface stays inactive (no TC string is produced) so invalid signals are never broadcast to vendors. Geo-targeting — Show banners only to visitors from regulated regions (EU, California, etc.). 180+ languages — Translate every string in the banner, or use one of the built-in translations. Script blocking — Tag any script with data-faz-tag to block it until the right category is accepted. Microsoft UET/Clarity — Consent integration for Microsoft advertising and analytics tools. Revisit consent widget — Floating button lets visitors change their preferences anytime. Accessibility-focused — Keyboard navigation (Tab, Enter, Escape), screen-reader support, mobile responsive. Helps with these frameworks This plugin assists consent and privacy workflows. It does not itself create, provide, or guarantee legal compliance, and you remain responsible for the final configuration for your site and jurisdiction. GDPR (EU General Data Protection Regulation) — Opt-in consent, granular categories, right to withdraw CCPA / CPRA (California Consumer Privacy Act) — “Do Not Sell or Share” opt-out link ePrivacy Directive (EU Cookie Law) — Consent-based script blocking support Italian Garante Privacy — 6-month consent expiry setting and consent logging controls EDPB Guidelines — No scroll-as-consent, no pre-checked categories, equal button prominence options LGPD (Brazil General Data Protection Law) — Consent-based model POPIA (South Africa Protection of Personal Information Act) — Opt-in consent Try it Live Try FAZ Cookie Manager in WordPress Playground — no account, no install, runs entirely in your browser. How it works Install and activate — the cookie banner appears immediately with sensible defaults Scan your site to detect cookies automatically Customize the banner design, text, and colors to match your brand Enable Google Consent Mode or IAB TCF if you use advertising tools Monitor consent analytics on the dashboard Core banner functionality runs on your WordPress site. Optional update/download features may contact GitHub, IAB Europe, MaxMind, ip-api.com, ipinfo.io (opt-in VPN detection), or the AMP CDN depending on which features you enable and use. Cookie Policy generator (1.16.0+) Need a Cookie Policy page that explains the cookies your site sets, the jurisdiction it operates under, and who the visitor should contact about their data? FAZ Cookie Manager 1.16.0 ships a dedicated Cookie Policy admin tab plus the [faz_cookie_policy_complete] shortcode. Jurisdiction-aware — pick GDPR (EU/EEA/UK), CCPA/CPRA (California), or LGPD (Brazil). Each jurisdiction ships its own template scaffold with the legal references and required sections for that framework. Multilingual (7 languages out of the box) — en, it, fr, de, es, pt-BR, bg. Override per render with [faz_cookie_policy_complete lang="it"] or let the visitor’s browser language pick. Auto-populated cookie inventory — the rendered policy pulls live from wp_faz_cookies, so any cookie discovered by the scanner shows up at the next render with its category, duration and description, in the active language. Filled with your company data — name, address, DPO email, third-party services, retention period: stored in faz_cookie_policy_data option, edited via the admin form, never seeded from admin_email or blogname (PII protection). Non-removable legal disclaimer — every generated policy ends with a footer making explicit that the templates are starting points, not legal advice. The disclaimer is hardcoded in the renderer (not in the template files) so section overrides cannot suppress it. Versioning hash — a data-faz-policy-version attribute on the rendered article tracks template + data drift over time. Display-only fields (the visible “Last updated” date) are excluded so the hash doesn’t change daily. Filter for site builders — faz_cookie_policy_data lets you inject custom placeholders before template substitution. Backwards compatible — the long-standing [faz_cookie_policy] shortcode (with site_name / contact / show_table attributes from 1.7.0) is unchanged. The standalone [faz_cookie_table] shortcode and matching faz/cookie-table Gutenberg block still work for embedding just the cookie inventory table. Multi-banner geo-routing vs multilingual content (1.14.0+) These are two orthogonal features that combine freely — multi-banner is per country, multilingual content is per language inside each banner. Multi-banner geo-routing picks WHICH banner profile to serve based on the visitor’s country. Typical setup: a strict GDPR banner for EU/EEA/UK and a CCPA opt-out banner for California (or any other per-region compliance profile). Country resolution chain: Cloudflare CF-IPCountry header (opt-in via the faz_trust_cf_ipcountry_header filter) → MaxMind GeoLite2 → ip-api.com fallback. Each banner row carries its own target_countries list and a priority integer for overlap resolution. Multilingual content lives INSIDE each banner. A single banner stores translations of its title, description and button labels for as many languages as you enable on the Languages page. The language displayed to the visitor is resolved CLIENT-SIDE from navigator.languages so a country-targeted banner can still be served from a full-page cache (LiteSpeed / WP Rocket / Cloudflare APO) and the right language renders on hydration. Practical example: an install needs only TWO banner rows, not eight. One EU-targeted GDPR banner with English + Italian + German + French + Polish translations inside, and one US-targeted CCPA banner with English + Spanish translations inside. The country selects the banner; the browser selects the translation inside the banner. Visitors hitting the right cache key get the right banner + the right language. External Services GitHub / Raw GitHubusercontent (Open Cookie Database) Used to refresh the built-in cookie definitions snapshot for the optional auto-categorize feature. Triggered when: you click the definitions update action in the Cookies screen. Data sent: your server IP address and standard HTTP request headers. Service URLs: * https://raw.githubusercontent.com/fabiodalez-dev/Open-Cookie-Database/master/open-cookie-database.json Terms of Service / Privacy Policy: * https://docs.github.com/en/site-policy/github-terms/github-terms-of-service * https://docs.github.com/en/site-policy/privacy-policies/github-privacy-statement IAB Europe / vendor-list.consensu.org Used to download the Global Vendor List and purpose translations for the optional IAB TCF feature. Triggered when: you manually update the vendor list, and weekly while IAB TCF is enabled. Data sent: your server IP address and standard HTTP request headers. Service URLs: * https://vendor-list.consensu.org/v3/vendor-list.json * https://vendor-list.consensu.org/v3/purposes-en.json Privacy Policy: * https://iabeurope.eu/privacy-policy/ MaxMind Used to download a GeoLite2 database for optional geo-targeting. You choose the edition in Settings → GeoIP Database: the smaller Country edition (default, country-level only) or the larger City edition (adds region/subdivision data for sub-national province/state routing such as Quebec Law 25). City is a much larger download; pick it only if you rely on region-level routing. Triggered when: you enter a MaxMind license key in Settings and start the database download. Data sent: your server IP address, the license key you provide, and standard HTTP request headers. Service URL: * https://download.maxmind.com/app/geoip_download Terms of Service / Privacy Policy: * https://www.maxmind.com/en/terms-of-use * https://www.maxmind.com/en/privacy-policy ip-api.com Used as a fallback geolocation lookup for the optional geo-targeting and multi-banner geo-routing features, only when MaxMind is unavailable. Triggered when: a frontend page renders the banner while geo-targeting / multi-banner geo-routing is enabled AND neither the Cloudflare CF-IPCountry header (opt-in) nor the MaxMind GeoLite2 database produces a result. The visitor’s IP is sent to ip-api.com for country resolution; the resolved country code is cached in a transient (hash-keyed by IP) for one hour to avoid repeating the lookup. Data sent: the visitor’s IP address and standard HTTP request headers. Service URL: * http://ip-api.com/json/{ip}?fields=countryCode Terms of Service / Privacy Policy: * https://ip-api.com/docs/legal ipinfo.io (geo-routing v2 only) Used for VPN/proxy/Tor detection when the admin opts in to enhanced geo detection via Settings → Geo-routing → ipinfo settings. The plugin sends the visitor IP to ipinfo.io to determine whether the visitor is masking their location; when VPN is detected, the most-protective rule-set is applied regardless of the visitor’s apparent country. Triggered when: a frontend page renders the banner AND the admin has configured an ipinfo API key AND has explicitly attested to having a DPF / SCC / DPA agreement with ipinfo.io for cross-border data transfer of EU/UK visitor IPs. Without the admin opt-in, ipinfo is NEVER called. Data sent: the visitor’s IP address (in cleartext, as required by ipinfo’s lookup contract), the configured API key, and standard HTTP request headers. The plugin caches the VPN classification locally for 24 hours hash-keyed by the IP (with monthly salt rotation) so repeat visitors do not trigger fresh calls. Service URL: * https://ipinfo.io/{ip}/privacy Terms of Service / Privacy Policy: * https://ipinfo.io/terms-of-service * https://ipinfo.io/privacy-policy * DPA (Data Processing Agreement) available on request: https://ipinfo.io/contact Plugin REST endpoint /faz/v1/banner (public) Used by the plugin’s own front-end JavaScript (script.js) to fetch the per-language / per-country banner payload after the page has loaded. This is an INTERNAL endpoint hosted by the plugin on the same WordPress install — no third-party network call leaves the visitor’s browser to a remote service. It is documented here only because the response carries bannerSlug and activeLaw, two strings that describe which banner profile and which legal regime (gdpr / ccpa) currently applies to the visitor. Triggered when: the front-end banner script bootstraps on a page that has multi-banner geo-routing active. Data sent: only what the visitor’s browser already sends with any page request to the same origin. The plugin does not forward the request to any remote service. Service URL: * https://{your-site}/wp-json/faz/v1/banner AMP Project CDN Used only on AMP pages when the AMP consent integration is active, to load the official amp-consent component required by AMP. Triggered when: an AMP page renders the AMP consent banner. Data sent: the visitor IP address and standard browser request data to the AMP CDN. Service URL: * https://cdn.ampproject.org/v0/amp-consent-0.1.js Documentation / Privacy: * https://amp.dev/documentation/components/amp-consent * https://policies.google.com/privacy Note on third-party domain strings inside the plugin codebase The plugin source includes several third-party domain names (e.g. js.stripe.com, connect.facebook.net, cdn.jsdelivr.net, unpkg.com, googletagmanager.com, etc.) as string patterns for two purposes: Script-blocking detection patterns — used to identify analytics, advertising, and tracking scripts that the site administrator’s other plugins may inject, so we can block them until the visitor has given consent. The plugin itself does not load any of these scripts. Whitelist defaults — domains such as unpkg.com/, cdn.jsdelivr.net/, fonts.googleapis.com/, www.google.com/recaptcha/api, etc. are seeded as default whitelist entries so the script blocker leaves them alone unless the admin explicitly removes them. They are configuration data, not outbound HTTP calls. The only outbound HTTP requests this plugin makes are the six documented above (Open Cookie Database, IAB GVL, MaxMind, ip-api.com fallback, ipinfo.io VPN detection (opt-in), AMP CDN). All six are gated behind explicit administrator action or an enabled feature. The internal /faz/v1/banner endpoint described above is hosted by this plugin on the same site — no third-party network call leaves the visitor’s browser to a remote service. Cache Plugin Compatibility When multi-banner geo-routing (1.14.0+) is active, the rendered HTML can legitimately vary by visitor country. This plugin asks the page-cache layer to bypass caching on those requests by emitting: Cache-Control: no-store, no-cache, must-revalidate, max-age=0 Pragma: no-cache X-LiteSpeed-Cache-Control: no-cache Vary: CF-IPCountry (when the trust filter faz_trust_cf_ipcountry_header is enabled) DONOTCACHEPAGE, DONOTCACHEOBJECT, DONOTCACHEDB PHP constants (industry-standard bypass hints) do_action( 'litespeed_control_set_nocache', ... ) when LiteSpeed Cache is installed Verified compatible (no extra configuration needed) LiteSpeed Cache — uses the explicit litespeed_control_set_nocache action + X-LiteSpeed-Cache-Control header. WP Rocket — honors DONOTCACHEPAGE natively. W3 Total Cache — honors DONOTCACHEPAGE / DONOTCACHEOBJECT natively. WP Super Cache — honors DONOTCACHEPAGE natively. Hummingbird (WPMU DEV) — honors DONOTCACHEPAGE natively. Cloudflare APO — honors the Cache-Control: no-store header. With CF in front, also enable the trust filter so the Vary: CF-IPCountry header is emitted and CF caches per-country variants instead of bypassing entirely. Known limitations CDNs without origin Cache-Control honoring (e.g. some legacy CloudFront configurations) — verify the response Cache-Control header reaches the edge. If not, add a CF-IPCountry or country-based cache key rule at the CDN level. Minor / regional cache plugins (Comet Cache, Cachify, Swift Performance Lite) — not formally tested. Most still honor DONOTCACHEPAGE; verify by inspecting the response Cache-Control on a country-targeted page. Override the bypass logic per request via the faz_country_dependent_banner_output filter (return false to force the cache to ignore the country dimension on a specific URL).