Title: FAZ Cookie Manager
Author: fabiodalez
Published: 30 آوریل 2026
Last modified: 26 می 2026
---
جستجوی افزونهها
# FAZ Cookie Manager
توسط [fabiodalez](https://profiles.wordpress.org/fabiodalez/)
[دانلود](https://downloads.wordpress.org/plugin/faz-cookie-manager.1.16.2.zip)
[Live Preview](https://fa.wordpress.org/plugins/faz-cookie-manager/?preview=1)
* [جزئیات](https://fa.wordpress.org/plugins/faz-cookie-manager/#description)
* [نقد و بررسیها](https://fa.wordpress.org/plugins/faz-cookie-manager/#reviews)
* [نصب](https://fa.wordpress.org/plugins/faz-cookie-manager/#installation)
* [توسعه](https://fa.wordpress.org/plugins/faz-cookie-manager/#developers)
[پشتیبانی](https://wordpress.org/support/plugin/faz-cookie-manager/)
## توضیحات
**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), 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 support, built in.
* **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](https://playground.wordpress.net/?plugin=faz-cookie-manager)**—
no account, no install, runs entirely in your browser.
#### How it works
1. Install and activate — the cookie banner appears immediately with sensible defaults
2. Scan your site to detect cookies automatically
3. Customize the banner design, text, and colors to match your brand
4. Enable Google Consent Mode or IAB TCF if you use advertising tools
5. 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 (6 languages out of the box)** — en, it, fr, de, es, pt-BR. 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 the GeoLite2 Country database for optional geo-targeting.
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:
1. **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.
2. **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).
## عکسهای صفحه
* [[
* **Cookie consent banner on the frontend** — GDPR-ready banner in the bottom-left
corner with “Customize”, “Reject All” and equal-weight “Accept All” buttons.
Shown only on the first visit until the visitor makes a choice.
* [[
* **Preference center** — Category-level opt-in modal. Necessary cookies are always
active; every other category (Functional, Analytics, Uncategorized, Marketing)
is opt-in by default, with a clear description for each.
* [[
* **Admin dashboard** — Overview of pageviews, banner impressions, accept rate
and reject rate, with a 7/30/365-day pageviews chart and consent distribution.
* [[
* **Banner editor** — Configure layout, position, colours, copy and behaviour with
a live in-iframe preview. Ships with GDPR Strict, High Contrast and Light Minimal
design presets.
* [[
* **Cookies management** — Review and edit cookie categories, run the built-in
scanner, and browse the bundled Open Cookie Database with 1,000+ definitions.
* [[
* **IAB TCF v2.3 Global Vendor List** — Browse the bundled GVL, filter by purpose,
and select which vendors your site works with. Full Transparency and Consent
Framework v2.3 support, no cloud required.
* [[
* **Consent logs** — Local, tamper-resistant audit trail of every visitor consent:
status, categories, hashed IP, URL and timestamp. Filter, search and export to
CSV for DPIA / audits.
* [[
* **Google Consent Mode v2** — Default vs. granted state for `ad_storage`, `analytics_storage`,`
ad_user_data`, `ad_personalization`, `functionality_storage`, `personalization_storage`
and `security_storage`. Works with GTM and gtag.
* [[
* **Languages** — Manage active languages and the default banner language. Works
alongside WPML / Polylang; Italian, Dutch, German, French and Czech translations
ship out of the box.
* [[
* **Settings** — Global controls: enable/disable the banner, exclude specific pages,
cross-domain consent forwarding, hide from bots, GTM dataLayer events, consent
log retention and scanner limits.
## بلوکها
این افزونه 3 بلوک ارائه میدهد.
* Settings
* Settings
* Settings
## نصب
#### From the WordPress.org plugin directory (recommended)
1. In your WordPress dashboard go to **Plugins > Add New Plugin**
2. Search for **FAZ Cookie Manager**
3. Click **Install Now**, then **Activate**
4. Go to **FAZ Cookie** in the admin sidebar to configure your banner
#### Manual installation
1. Download the ZIP from [wordpress.org/plugins/faz-cookie-manager](https://wordpress.org/plugins/faz-cookie-manager/)
2. In your WordPress dashboard go to **Plugins > Add New Plugin > Upload Plugin**
3. Upload the ZIP and click **Install Now**, then **Activate**
4. Go to **FAZ Cookie** in the admin sidebar to configure your banner
## سوالات متداول
### Does this plugin require a cloud account or subscription?
No required cloud account or subscription is needed. Core consent features run locally,
while some optional refresh/download features can contact documented third-party
services such as GitHub, IAB Europe, MaxMind, or AMP infrastructure.
### Is it really free? What’s the catch?
It’s free and open source (GPL-3.0). There are no premium upgrades, no feature gates,
and no upsells. The plugin is based on the GPL-licensed CookieYes v3.4.0 codebase,
with cloud dependencies removed and all included features running locally.
### Is it compatible with Google Consent Mode v2?
Yes. The plugin sends all 7 consent signals (`ad_storage`, `analytics_storage`, `
ad_user_data`, `ad_personalization`, `functionality_storage`, `personalization_storage`,`
security_storage`) and supports Google Additional Consent Mode (GACM) for ad technology
providers.
### Does the banner block cookies before consent?
Yes. Any script tagged with `data-faz-tag="category-name"` is blocked until the
visitor grants consent for that category. This helps you implement consent-based
blocking for ePrivacy/GDPR workflows.
### How does the cookie scanner work?
Go to **FAZ Cookie > Cookies** and click **Scan Site**. The scanner runs in your
browser using iframes, crawling your site’s pages to detect all cookies. Choose
from quick scan (10 pages), standard (100), deep (1000), or full scan. No external
service involved.
### Can I log consent for GDPR accountability?
Yes. Every consent action (accept, reject, customize) is recorded in a local database
table with timestamp, consent ID, categories chosen, anonymized IP, and page URL.
Export to CSV anytime from the Consent Logs page.
### Does it support multiple languages?
Yes. The Languages page lets you select from 180+ available languages. Each banner
you create carries its own translations for every language you enable — the banner
text (title, description, button labels) is stored per-language inside the banner
row, and the language displayed to the visitor is resolved client-side from `navigator.
languages`. WPML / Polylang URL-based language switching is auto-detected and always
cache-safe.
### Does multi-banner mean one banner per language?
No — multi-banner routing is per visitor **country** (e.g. GDPR vs CCPA, EU vs US),
not per language. Each banner row carries its OWN multilingual content: title, description
and button labels translated for every language you support. The visitor’s country
selects the banner; the visitor’s browser language then selects which translated
strings to render inside that banner. So an install with one EU-targeted GDPR banner(
carrying English + Italian + German + French translations) and one US-targeted CCPA
banner (carrying English + Spanish translations) needs only TWO banner rows, not
eight. See the “Multi-banner geo-routing vs multilingual content” section in the
Description for the full architecture.
### Can users change their consent after accepting?
Yes. A floating revisit widget appears on every page, letting visitors reopen the
preference center and change their choices at any time.
### Is the banner accessible?
Yes. The banner supports full keyboard navigation (Tab, Enter, Escape), proper ARIA
labels, and is responsive down to 375px viewports. Buttons have equal visual prominence
to avoid dark patterns.
### Does it work with caching plugins?
Yes. The consent banner is rendered via JavaScript from a cached template, so it
works with all major caching plugins (WP Super Cache, W3 Total Cache, LiteSpeed
Cache, etc.).
### Does the plugin send any data home or collect telemetry?
No. The plugin contains no telemetry, no analytics beacon, and no “phone home”.
Dashboard numbers are computed locally from your own `wp_faz_pageviews` and `wp_faz_consent_logs`
tables. Every outbound request that _can_ happen is documented in the “External
services” section and is gated behind an explicit admin action.
### Where is the source of the bundled minified JavaScript?
The only minified files we ship are `frontend/js/gcm.min.js` and `frontend/js/tcf-
cmp.min.js`. The full, unminified sources live next to them as `gcm.js` and `tcf-
cmp.js`, and the build command `npm run build:min` rebuilds them with `terser`.
No obfuscation is used.
### Does uninstalling the plugin remove my data?
By default, no — your consent logs, banner configuration and categories stay in
the database so you can reinstall without losing work. To wipe everything on uninstall,
enable **Settings General Remove all data on uninstall** or define `FAZ_REMOVE_ALL_DATA`
as `true` in `wp-config.php` before deleting the plugin.
### Does the plugin include a CCPA “Do Not Sell” opt-out form?
Yes. Place `[faz_do_not_sell]` on any page (e.g. your Privacy Policy) to show a
California Consumer Privacy Act opt-out form. When a visitor submits the form, the
opt-out is logged in the local consent table with a hashed IP address, a long-lived
cookie is set so the visitor sees a confirmation on subsequent visits, and the site
admin receives a notification email. Optional attributes: `title` (heading text)
and `button` (submit label). No external service is involved.
### Does the plugin include a GDPR Data Subject Access Request (DSAR) form?
Yes. Place `[faz_dsar_form]` on any page to show a GDPR-compliant request form covering
six rights: Access (Art. 15), Erasure (Art. 17), Data Portability (Art. 20), Rectification(
Art. 16), Restriction (Art. 18), and the Right to Object (Art. 21). On submission,
the request is stored as a private post in the WordPress database (so it survives
email failures), a notification is sent to the admin with a direct link to the record,
and a confirmation is sent to the requester. The form includes a honeypot field
and nonce verification to block spam bots. Optional attributes: `button` (submit
label).
## نقد و بررسیها
### [Literally Perfect!](https://wordpress.org/support/topic/literally-perfect-6/)
[Niharika Verma](https://profiles.wordpress.org/niharikaverma95/) 25 می 2026 1
پاسخ
This is a gem. God bless to the person who put in all the efforts for this. Someone
recommended this in the Kadence FB group and when I looked for it on Google, I saw
the owner’s post on Reddit sharing about the plugin. This has literally everything
one needs in a cookie plugin. I was tired of juggling and experimenting with these
dozens of cookie plugins. I had to put on hold though because I am manually not
able to add all the ad vendors 😹 wish it had auto scan for ad vendors 🙉 but other
than that, this cookie plugin is the best. Finally someone understood the need of
individual publishers.
### [Just AWESOME!](https://wordpress.org/support/topic/just-awesome-351/)
[and4zej](https://profiles.wordpress.org/and4zej/) 21 می 2026 1 پاسخ
It is incredibly rare to find a plugin that delivers this much robust functionality
without immediately hitting you with a premium paywall. The FAZ Plugin is a masterclass
in clean development—it is lightning fast and handles everything I throw at it without
breaking a sweat. On top of that, the author is incredibly open, approachable, and
receptive to feedback. This isn’t just a great tool; it’s a project backed by an
awesome developer who actually cares about the community. Five stars all day long!
### [Everything you need in a cookie plugin](https://wordpress.org/support/topic/everything-you-need-in-a-cookie-plugin/)
[James](https://profiles.wordpress.org/james-feaver/) 21 می 2026 2 پاسخ
I’d been happily using one of the popular cookie plugins for years (over a million
downloads). In moving to the WooCommerce block-based cart and checkout and writing
some code, I hit an issue with 3 of my products repeatedly causing checkout errors.
I spent several days trying to work it out assuming my code was wrong. In the end
I found the cookie plugin was the problem for products with links to Instagram!
The problem was acknowledged 1 year and 8 months ago but not fixed, any support
suggestions from the time did not work. Requests in their current support forum
haven’t been responded to in the last month. Hence a search for a new cookie plugin.
I read various reviews and articles, and gave 4 or 5 other popular ones plugins
a go. For each I found that the free versions actually had constraints, such as
the number of pages you could scan or that you needed the pro version for a cookie
scanner or manually had to fill in all of the details on the cookies found. Somehow
I found this one and the documentation and reviews got my attention. Now I am so
pleased with my choice. I wholeheartedly recommend it, all the functionality you
need is there. When I found a shortcode for the content for my cookie policy page
I was delighted. Fabio Dalez (plugin author) you are a genius. Thank you so much.
### [looooove it](https://wordpress.org/support/topic/looooove-it-3/)
[angerav](https://profiles.wordpress.org/angerav/) 21 می 2026 1 پاسخ
great plugin with a lot of functionalities! looking forward to stop using cookieYes
once for all to use faz as my default cookies plugin 😎 also, the developer is super!
always on point, very recommended
### [We are witnessing history unfolding live](https://wordpress.org/support/topic/we-are-witnessing-history-unfolding-live/)
[ashrudral](https://profiles.wordpress.org/ashrudral/) 19 می 2026 2 پاسخ
Most of us discover great plugins like this after they’ve hit a million downloads.
I found this one fresh out of the oven. The era of cookie consent plugins presented
as bloated SaaS funnels packed with subscriptions, cloud lock-ins, upsells, telemetry,
continuous background processing scans sucking your server compute, unnecessary
cloud API calls is over. FAZ is a FOSS plugin that outperforms all the paid cookie
consent plugins while still being genuinely fully local. This probably is the CMP
SaaS industry killer. This gives the power back to the site owner for basic site
function such as Cookie consent. The developer have an unusually deep understanding
of how modern websites actually work. What impressed me most is not the feature
count, but the systems thinking behind the implementation. Every setting reflects
real-world operational understanding. Even small details like: Resource aware scan
frequency (daily/weekly/monthly), Cloudflare country-header support baked in for
geo targetting, public-suffix-aware cookie scoping, cross-domain consent syncing,
retention policies, and adblock-resistant script handles show that this was built
by someone who understands browser behavior, caching layers, SEO implications, and
runtime performance at a deep level. For users who want sovereign, transparent,
enterprise-grade consent infrastructure on your local server with such tiny footprint,
this is revolutionary.
### [Best free cookies plugin](https://wordpress.org/support/topic/best-free-cookies-plugin/)
[pascalminator](https://profiles.wordpress.org/pascalminator/) 12 می 2026
Well made plugin by a proactive developer, replacing cookiebot for several websites
now. Entirely free and no account needed.
[ خواندن تمامی 12 نقد و بررسی ](https://wordpress.org/support/plugin/faz-cookie-manager/reviews/)
## توسعه دهندگان و همکاران
“FAZ Cookie Manager” نرم افزار متن باز است. افراد زیر در این افزونه مشارکت کردهاند.
مشارکت کنندگان
* [ fabiodalez ](https://profiles.wordpress.org/fabiodalez/)
[ترجمه “FAZ Cookie Manager” به زبان شما.](https://translate.wordpress.org/projects/wp-plugins/faz-cookie-manager)
### علاقه مند به توسعه هستید؟
[Browse the code](https://plugins.trac.wordpress.org/browser/faz-cookie-manager/),
check out the [SVN repository](https://plugins.svn.wordpress.org/faz-cookie-manager/),
or subscribe to the [development log](https://plugins.trac.wordpress.org/log/faz-cookie-manager/)
by [RSS](https://plugins.trac.wordpress.org/log/faz-cookie-manager/?limit=100&mode=stop_on_copy&format=rss).
## گزارش تغییرات
The full changelog (every release back to 1.0.0) lives at:
https://github.com/fabiodalez-
dev/FAZ-Cookie-Manager/blob/main/CHANGELOG.md and on the GitHub Releases page: https://
github.com/fabiodalez-dev/FAZ-Cookie-Manager/releases
#### 1.16.2
* Fix: Cookie Policy generator `[faz_cookie_policy_complete]` — Gooloo feedback
round. (1) `{{COOKIE_POLICY_URL}}` no longer leaks `?preview_id=&preview_nonce
=` query strings from the WordPress preview flow into the public policy text.(
2) Cookie inventory now renders as collapsible HTML5 accordion (`/`) with a real `
` per category — previously a flat `
` produced a
700+-line wall of definition pairs. (3) Footer disclaimer is now admin-configurable(
toggle + custom text) and wrapped in `