Title: OrioleOne Easy Cookies Author: OrioleOne Published: September 14, 2026 Last modified: September 26, 2026 --- Search plugins ![](https://ps.w.org/oriole-one-easy-cookies/assets/icon-256x256.gif?rev=3695898) # OrioleOne Easy Cookies By [OrioleOne](https://profiles.wordpress.org/orioleone/) [Download](https://downloads.wordpress.org/plugin/oriole-one-easy-cookies.1.0.1.zip) * [Details](https://wordpress.org/plugins/oriole-one-easy-cookies/#description) * [Reviews](https://wordpress.org/plugins/oriole-one-easy-cookies/#reviews) * [Installation](https://wordpress.org/plugins/oriole-one-easy-cookies/#installation) * [Development](https://wordpress.org/plugins/oriole-one-easy-cookies/#developers) [Support](https://wordpress.org/support/plugin/oriole-one-easy-cookies/) ## Description OrioleOne Easy Cookies is a local-first consent and cookie-management plugin for WordPress. It provides an accessible consent banner, WP Consent API integration, Google Consent Mode and Microsoft Clarity consent signalling, strict script controls, local service discovery, and optional aggregate consent statistics. No external account is required. OrioleOne Easy Cookies provides technical tools that help website owners manage consent and cookie disclosures. Website owners remain responsible for configuration and legal compliance. #### Features * Accept All, Reject All, and granular preferences. * Necessary, Functional, Preferences, Analytics, Performance, and Advertisement categories. * Strict prior blocking or consent signalling. * WP Consent API provider integration for compatible plugins such as Site Kit. * Google Consent Mode v2 signals without installing a Google tag. * Microsoft Clarity Consent API v2 signals without installing Clarity. * Explicit reviewed-service registry, existing WordPress script-handle controls, and accessible embed placeholders. * Local same-origin discovery scanner with administrator review. * Optional local aggregate consent-interaction statistics. * Strict global, European/UK, US-oriented, and custom regional templates. * Global Privacy Control support for Advertisement/targeted-advertising preferences. * No plugin telemetry, affiliate links, promotional backlinks, remote admin assets, or required SaaS account. #### Local-first design and privacy Consent choices are stored in the first-party necessary `ooec_consent` cookie. OrioleOne does not send consent, scan, analytics, configuration, domain, or visitor data to the plugin developer. Optional statistics remain in the site’s own WordPress database and represent interactions, not guaranteed unique people. The local scanner requests only administrator-selected same-origin URLs and stores findings locally. It does not use a remote scanning or geolocation service. ### Setup Strict global opt-in is the default. Every optional category starts denied. European/ UK mode uses opt-in behavior; US-oriented mode changes the notice template and WP Consent API consent type but does not silently grant optional storage. Custom mode uses administrator-configured text and category visibility. OrioleOne does not infer legal jurisdiction or use IP geolocation. A trusted site- owned mechanism may select an explicit mode through the `oriole_one_easy_cookies_regional_mode` filter. Increase the policy/configuration version after material changes that should invalidate an existing choice. ### WP Consent API integration WP Consent API must be installed and activated separately. OrioleOne registers through documented public interfaces and communicates its validated source-of-truth choice. It does not modify WP Consent API internals or Site Kit options. Mappings include Necessary to the essential functional API category, Preferences to preferences, Analytics to statistics, Advertisement to marketing, and configurable Performance mapping. Optional Functional remains controlled locally. ### Google Consent Mode OrioleOne can send documented Consent Mode v2 defaults and updates to an existing Google integration. Optional storage defaults to denied and `security_storage` remains granted. The plugin does not install Google Analytics, Google Tag Manager, Google Ads, Site Kit, or measurement IDs. The denied default is emitted as a synchronous, local, critical inline script before ordinary head scripts. Use Google Tag Assistant to verify ordering, values, and duplicate-default warnings. Exclude the script IDs `oriole-one-easy-cookies-consent- bootstrap` and `oriole-one-easy-cookies-wp-consent-type` from delay, defer, combine, or relocation features in caching/optimization tools. Site Kit can consume the WP Consent API mapping. If Site Kit’s own Consent Mode feature is enabled, disable OrioleOne’s direct Google Consent Mode signalling to avoid two default initializers; continue using OrioleOne as the stored-choice provider through WP Consent API. ### Microsoft Clarity OrioleOne can call the documented Clarity `consentv2` interface for an independently installed Clarity integration. It does not install Clarity, set a project ID, create Clarity cookies, or load Clarity assets. ### Strict script blocking Strict mode activates only reviewed and enabled service definitions after the assigned category is granted. It supports existing WordPress script handles and their dependents, associated inline blocks, and registered iframe placeholders. The registry does not accept JavaScript, PHP, CSS, or external script URLs, and the plugin does not download or insert vendor scripts. It intentionally avoids broad page output rewriting. Strict mode cannot block an undeclared tag inserted directly by another plugin, a tag manager, or cached HTML; every optional service must be reviewed and explicitly registered. Withdrawal prevents future registered loads and attempts configured first-party cookie/storage cleanup. Code already executed cannot reliably be unloaded, and data already transmitted cannot be recalled. ### Scanner The local scanner inspects selected same-origin pages, response headers, browser- visible resources, known local service signatures, and browser-visible storage when an administrator initiates browser assistance. Findings require human review. Scanner results are not legal advice and are not guaranteed complete. ### Statistics Statistics are disabled by default. When enabled, minimized local interactions are retained briefly, aggregated into daily counts in bounded transactional batches, and deleted according to separate raw and aggregate retention settings. Optional path collection removes query strings and fragments and redacts identifier-like segments. Full IP addresses, user agents, referrers, and browser fingerprints are not stored. CSV export contains paginated grouped counts only. ### Regional modes * Strict global opt-in: default privacy-protective template. * European/UK opt-in: opt-in template for administrator configuration. * US-oriented notice/opt-out: notice template and opt-out consent type without a compliance claim. * Custom/manual: administrator-controlled wording and visibility. Regional templates are technical starting points, not legal determinations. ### Global Privacy Control When enabled, `Sec-GPC: 1` and `navigator.globalPrivacyControl` hold Advertisement consent at denied and withdraw a prior advertising grant. GPC does not infer a choice for Functional, Preferences, Analytics, or Performance. This feature does not guarantee compliance with US state privacy laws. ### External services OrioleOne itself does not contact the plugin developer or a remote API. All plugin CSS and JavaScript assets are bundled locally. Domain names in the scanner signatures and service templates are inert detection metadata: the plugin compares locally observed resource names with those strings, but it does not request those domains. The following optional interoperability can cause a connection only when the website owner has separately installed/configured the named service or deliberately places a supported embed: * Google services (Google Analytics, Tag Manager, Ads, Site Kit, Consent Mode, Maps, reCAPTCHA, or YouTube): OrioleOne can send consent-state commands to an existing Google integration and can reveal an administrator-configured Google/ YouTube embed after the visitor grants its category. OrioleOne sends no measurement ID and installs no Google tag. The independently configured Google service may receive the visitor’s IP address, browser/device data, requested page or embed URL, consent state, and any data that the website owner configured it to collect when that integration or embed loads. Google terms: https://policies.google.com/ terms ; Google privacy policy: https://policies.google.com/privacy * Microsoft Clarity: OrioleOne can call the local `clarity('consentv2', ...)` interface only when the website owner has independently installed Clarity. OrioleOne does not load Clarity or send a project ID. Once installed by the website owner, Clarity may receive consent state and the visitor/browser data covered by the owner’s Clarity configuration. Microsoft Services Agreement: https://www.microsoft.com/ servicesagreement ; Microsoft Privacy Statement: https://www.microsoft.com/privacy/ privacystatement * Meta Pixel: the bundled template and scanner can identify an independently installed Meta Pixel; OrioleOne does not install or contact Meta Pixel. If the website owner independently loads it after consent, Meta may receive consent state and the visitor/browser and event data configured by that owner. Meta terms: https:// www.facebook.com/terms ; Meta privacy policy: https://www.facebook.com/privacy/ policy/ * Vimeo: the optional `[ooec_embed]` shortcode can reveal an administrator-supplied Vimeo player URL after consent. Loading that player can send the visitor’s IP address, browser/device data, requested video URL, and player interactions to Vimeo. Vimeo terms: https://vimeo.com/legal ; Vimeo privacy policy: https://vimeo. com/legal/privacy WP Consent API is a separate WordPress plugin, but communication with it occurs locally inside the WordPress site and does not itself transmit data to an external service. ### Scanner limitations Scans can miss HttpOnly cookies, cross-origin or partitioned storage, dynamically generated resources, authenticated routes, interaction-triggered services, and behavior hidden by consent or caching. Suggested provider, purpose, duration, confidence, and category values require administrator review. ### Developer documentation Public helpers and hooks include service/script registration, consent-state access, consent events, `ooec:gpc-applied`, and the trusted-local `oriole_one_easy_cookies_regional_mode` filter. Human-readable documentation is included in the `docs` directory. No compilation is required. Distributed PHP, JavaScript, and CSS are the human-readable source. Development-only PHPCS and PHPUnit dependencies are described by `composer. json` and are excluded from the release ZIP. ### Legal disclaimer OrioleOne Easy Cookies provides technical tools to help website owners manage consent and cookie disclosures. Website owners remain responsible for configuration and legal compliance. The plugin is not a legally certified or Google-certified consent management platform and does not guarantee compliance in any jurisdiction. ## Installation 1. Upload the `oriole-one-easy-cookies` folder to `/wp-content/plugins/`, or install the release ZIP through Plugins > Add New > Upload Plugin. 2. Activate OrioleOne Easy Cookies. 3. Open Easy Cookies > Setup. 4. Select policy pages, regional behavior, blocking/signalling mode, integrations, categories, and banner appearance. 5. Review registered services before enabling strict blocking rules. 6. Test in a private browser before production deployment. ## FAQ ### Does the plugin guarantee GDPR, UK GDPR, US state-law, or worldwide compliance? No. It provides technical tools. Website owners remain responsible for configuration, disclosures, vendor contracts, and legal compliance. ### Is an external account required? No. Core banner, blocking, scanner, registry, and statistics features are local. ### Does OrioleOne install Google or Microsoft tracking? No. Integrations signal consent to services independently configured by the website owner. ### Does the scanner discover everything? No. Server scans cannot see every JavaScript-created value; JavaScript cannot read HttpOnly cookies or cross-origin storage; services may load only after consent, login, or interaction. ### Are statistics unique-visitor counts? No. They count consent interactions. ### What happens on uninstall? The administrator can keep all data, remove settings only, or remove all plugin data. Normal deactivation does not delete stored data. ## Reviews There are no reviews for this plugin. ## Contributors & Developers “OrioleOne Easy Cookies” is open source software. The following people have contributed to this plugin. Contributors * [ OrioleOne ](https://profiles.wordpress.org/orioleone/) [Translate “OrioleOne Easy Cookies” into your language.](https://translate.wordpress.org/projects/wp-plugins/oriole-one-easy-cookies) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/oriole-one-easy-cookies/), check out the [SVN repository](https://plugins.svn.wordpress.org/oriole-one-easy-cookies/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/oriole-one-easy-cookies/) by [RSS](https://plugins.trac.wordpress.org/log/oriole-one-easy-cookies/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 1.0.1 * Security: Enforced wp_unslash() on statistics request filter inputs before sanitization. * Standards: Formatted and linted public JavaScript and CSS assets against WordPress core standards. * Maintenance: Pruned obsolete legacy JS scripts and aligned workspace tooling configurations. * WordPress Core: Verified compatibility with WordPress 7.1. #### 1.0.0 * Initial release. * Added task-based setup, isolated desktop/mobile preview, visual layout controls, contrast feedback, structured service/disclosure editors, and accessible save feedback. * Repaired GPC startup, WP Consent API service synchronization, modal focus, dependency consent requirements, scan delivery/progress, statistics credentials, and multisite traversal. * Added the accessible consent banner, preference centre, local consent storage, regional templates, and Global Privacy Control handling. * Added WP Consent API, Google Consent Mode v2, and Microsoft Clarity consent signalling without installing third-party measurement scripts. * Added explicit strict script and embed controls, the evidence-based local scanner, and optional privacy-minimized aggregate consent statistics. * Added multisite lifecycle handling, local documentation, privacy disclosures, security hardening, and WordPress.org-ready packaging. ## Meta * Version **1.0.1** * Last updated **4 weeks ago** * Active installations **Fewer than 10** * WordPress version ** 6.5 or higher ** * Tested up to **7.1.3** * PHP version ** 7.4 or higher ** * Tags * [accessibility](https://wordpress.org/plugins/tags/accessibility/)[consent](https://wordpress.org/plugins/tags/consent/) [cookie banner](https://wordpress.org/plugins/tags/cookie-banner/)[cookies](https://wordpress.org/plugins/tags/cookies/) [privacy](https://wordpress.org/plugins/tags/privacy/) * [Advanced View](https://wordpress.org/plugins/oriole-one-easy-cookies/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/oriole-one-easy-cookies/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/oriole-one-easy-cookies/reviews/) ## Contributors * [ OrioleOne ](https://profiles.wordpress.org/orioleone/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/oriole-one-easy-cookies/)