FlexyConsent - Cookie Consent Management (GDPR, CCPA)
| 开发者 | flexyconsent |
|---|---|
| 更新时间 | 2026年7月26日 20:41 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
FlexyConsent is an IAB-registered Consent Management Platform (CMP) for WordPress. It adds a customizable consent banner to your site, records what every visitor agreed to, and gives you the reporting you need to show it — all configurable from the WordPress admin, with no coding.
The plugin supports IAB TCF v2.3, Google Consent Mode v2 and the IAB Global Privacy Platform (GPP), so it covers the EU/EEA and Switzerland, the United Kingdom, the United States (national and the California, Virginia, Colorado, Utah and Connecticut state sections), Canada, Türkiye, Brazil, South Africa, Japan, Australia, South Korea, Thailand and India.
The admin interface is available in 41 languages, including Turkish, German, French, Spanish, Italian, Portuguese, Dutch, Polish, Russian, Japanese, Korean and Simplified Chinese.
安装:
Recommended Installation
- In your WordPress dashboard, choose Plugins >Add New
- Search for "FlexyConsent" with the search bar in the top right corner.
- After finding our plugin in the results, click Install Now
- Download our plugin as a .zip file from this link: FlexyConsent.
- From your WordPress dashboard, choose Plugins > Add New
- Click Upload Plugin at the top of the page.
- Click Choose File , locate the plugin .zip file, then click Install Now
- After the installation is complete, click Activate Plugin
屏幕截图:
常见问题:
What is a CMP and what does it do?
A CMP, Consent Management Platform, is a tool used by websites to manage permissions for collecting and processing data from visitors. It informs visitors about data usage and obtains necessary permissions. IAB-approved CMPs facilitate the collection and processing of personal data in compliance with Transparency and Consent Framework (TCF) standards.
What is TCF and why is it important?
The Transparency and Consent Framework is a standard used in the digital advertising industry to comply with data protection laws in Europe. This framework provides internet users with more transparency and control over the digital advertising ecosystem.
What are the advantages of using an IAB-approved CMP?
An IAB-approved CMP manages data collection and processing processes in compliance with TCF standards. This is important to protect user privacy rights and ensure advertisers comply with legal requirements. Additionally, it provides the advantage of adhering to a trusted industry standard.
Why should I, as a website owner, use an IAB-approved CMP?
Using an IAB-approved CMP ensures compliance with data protection laws in Europe and helps you better manage your visitors' privacy preferences. It also provides a reliable solution for regulating your relationships with advertisers. = Can I turn off your plugin at any time? =\ Yes. There is no commitment that binds you to FlexyConsent. From the dashboard, you can turn it on/off at any time.
How can I follow up on stats?
We provide you with a dashboard to follow up on your stats.
How can I contact you?
You can contact us via our website FlexyConsent or by email at support@flexyconsent.com.
更新日志:
1.5.0
- IAB TCF support updated to v2.3.
- Fixed 26 of the 42 bundled translations, which never loaded because their files used locale codes WordPress does not recognise (for example ja_JA instead of ja, ko_KO instead of ko_KR, zh_ZH instead of zh_CN, pt_br instead of pt_BR). Turkish, German, French, Spanish, Italian and ten other locales were unaffected.
- Completed every bundled translation. The 184 strings added by the Cookie Manager, Consent Logs, Geo Preview and tabbed settings screens were previously shown in English in all languages; all 41 languages WordPress can load are now fully translated.
- Rebuilt the translation template (flexyconsent.pot) from the current source, so external translators see the real string set. It had last been generated before the 1.2.0 interface changes.
- The download no longer contains the 42 .po translation sources, which WordPress never reads — about 2.7 MB smaller. The compiled .mo files and flexyconsent.pot still ship.
- Bundled translations now act as a per-string fallback behind translations from translate.wordpress.org, instead of being ignored entirely as soon as one exists there. Previously the first community-translated string would have switched the whole bundled catalogue off, reverting every other string to English.
- Lowered the WordPress requirement to 5.9, so sites that were held back from the 1.2.0 security fixes by a stricter requirement can now update. The oldest WordPress API the plugin actually calls dates from 4.7.
- Updated the plugin description and tested-up-to version.
- Reorganised the Website Settings page into tabs — General, Consent & Privacy, Layout Properties and Geo Preview — matching the FlexyConsent web panel. All settings still save together with one Save button.
- Fixed checkboxes on the settings pages appearing blank when ticked (a white checkmark on a white background, caused by a conflict with WordPress admin styles). Checked boxes now show a clear blue box with a checkmark.
- Fixed the plugin disconnecting itself (account information lost, returning to the Welcome screen) after visiting an admin page. The account identifier was being wiped because it was validated as an e-mail address, which it is not for WordPress accounts.
- Fixed a related issue where the stored API key could be dropped when the settings were re-saved.
- Fixed sign-up being blocked on a brand-new install: the connection request was refused because the site was not yet connected.
- Added Geo Preview to Website Settings: see how the consent message appears to a visitor from a specific region, country, US state and language, based on your current settings.
- Fixed the settings preview not refreshing when you change an option (it tried to reload a cross-origin frame).
- The Website Settings page no longer stops setting up its controls when an account has an unusual project shape (missing subscription or consent-mode data), which could leave some checkboxes unresponsive.
- Websites: cookie and privacy policy links are now set per domain instead of once for the whole account, so sites with several domains can point each one at its own policies.
- Added a Consent Logs page: sortable, paginated, with CSV export.
- Cookie Manager: added Storage Type (HTTP cookie, local storage, session storage, tracking pixel) and import/export of cookies as JSON.
- Dashboard: added CSV export of the statistics currently on screen.
- Consent: IAB TCF now covers all 13 regions (adds Türkiye, Brazil, South Africa, Japan, Switzerland, Australia, South Korea, Thailand and India), up from 4.
- Consent: added browser storage consent, with per-region control over when visitors are asked before data is stored in their browser.
- Consent: added United States Section Preferences for US National, California, Virginia, Colorado, Utah and Connecticut, plus an "apply US National to all states" shortcut.
- Consent: Google Consent Mode is now enabled automatically whenever a browser storage region is selected, instead of being a separate switch. "Wait for update" now defaults to 1000ms.
- Design: added banner theme (19 presets), banner position, custom icon and an allow-page-interaction option. Theme, logo, icon and position are no longer hidden behind "Enable customization".
- Added "Show Reject all on the first layer" and "Hide empty cookie categories".
- Security: the API key is no longer sent to the browser. All calls to the FlexyConsent API now go through a server-side proxy, and the key is stored encrypted.
- Security: the API key and account email were previously readable on every wp-admin page by any logged-in user, including Subscribers. Fixed.
- Security: the settings REST endpoint now accepts only known keys and validates every value. The front-end script URL is restricted to flexyconsent.com.
- Removed the loader that was installed into wp-content/mu-plugins. It hardcoded the plugin folder name, so renaming the folder caused a site-wide fatal error that could not be cleared from the admin. Existing installs are cleaned up automatically on upgrade.
- Fixed the settings registration, which sanitized an array with sanitize_text_field() and so discarded saved settings.
- Requires PHP 7.4. Fixed a call to str_starts_with() that fataled on PHP below 8.0.
- Translations now load on init, avoiding the WordPress 6.7 notice about early loading.
- Admin page templates are no longer loaded on front-end requests.
- Updated Bootstrap to 5.3.3 and removed unused vendor files, reducing the plugin by about 6.4 MB.
- Added uninstall cleanup so deleting the plugin removes its options.
- Initial version
- Added Cookie Manager