Omea Consent

Description

This plugin adds a configurable cookie consent banner and consent manager. Tracking snippets can be grouped by consent category, blocked before consent, and managed from the WordPress admin. The WP Consent API feature plugin is bundled via Composer.

Features

• Configurable consent banner and preferences modal.
• Header, body, and footer script injection by consent category.
• Cookie and storage scanner with editable cookie table output.
• Optional autoblocking for known scripts, cookies, storage, iframes, and inline code.
• Google Consent Mode support.

Privacy

Omea Consent stores the visitor’s consent choices in a first-party consent cookie and matching browser storage key so choices can persist across page loads. Site administrators control any tracking snippets added through the plugin settings.

External services

Omea Consent ships with a local Open Cookie Database catalog for cookie matching. By default, the scanner uses this bundled local catalog and does not contact a remote cookie database service.

Site administrators can enable optional CookieDatabase.org lookups in the plugin settings. When enabled, Omea Consent may send detected cookie or browser storage names to CookieDatabase.org during an admin-initiated scan so the plugin can retrieve cookie classification metadata such as category, purpose, provider, and retention. This service is provided by Complianz B.V. Terms: https://cookiedatabase.org/terms-of-use-api/. Privacy: https://cookiedatabase.org/plugin-use-of-cookiedatabase-org-privacy-terms/.

The scanner includes local pattern matching for common script providers such as Google Tag Manager, Google Analytics, Meta Pixel, and HubSpot. These patterns are used only to detect scripts already present on the scanned site. Omea Consent does not send data to those providers as part of the scan.