
Nivaj Cookie Consent provides a complete cookie consent management solution for WordPress. It helps you comply with GDPR, CCPA, and other privacy regulations by giving visitors full control over cookie categories.
[nivaj_cookie_preferences] to place a cookie preferences button anywhereUse [nivaj_cookie_preferences] to add a “Cookie Preferences” button anywhere on your site.
Attributes:
text – Button label (default: “Cookie Preferences”)class – Additional CSS classExample: [nivaj_cookie_preferences text="Manage Cookies" class="my-btn"]
This plugin stores consent preferences in a browser cookie on the visitor’s device. When consent logging is active, IP addresses and user agents are stored as one-way SHA-256 hashes combined with the WordPress salt, making them non-reversible. No personal data is shared with external services by this plugin itself. See the “External services” section below for details on optional Google integrations.
This plugin optionally connects to external services when the site administrator explicitly enables them. No external connections are made by default.
When the administrator enables Google Tag Manager under Cookie Consent > Settings and provides a GTM container ID, this plugin loads the Google Tag Manager script from Google’s servers.
What it does: Loads a tag management container that can manage analytics, marketing, and other scripts on the site.
When it connects: On every frontend page load, only when GTM is enabled and a valid container ID (GTM-XXXXXXX) is configured.
Data sent: The GTM container ID is sent to Google’s servers to retrieve the container script. No personal visitor data is sent by this plugin directly; however, the loaded GTM container may collect data based on its own configuration.
When the administrator enables Google Consent Mode under Cookie Consent > Settings, this plugin sends consent signals to Google services via the browser’s dataLayer.
What it does: Communicates the visitor’s consent status (granted or denied) for ad storage, analytics storage, and personalization to Google services already running on the site.
When it connects: Consent default signals are set on page load. Consent update signals are sent when a visitor interacts with the cookie banner. This does not load any additional external scripts.
Data sent: Consent status values (granted/denied) for: ad_storage, ad_user_data, ad_personalization, analytics_storage, functionality_storage, personalization_storage, security_storage.
The Cookie Scanner feature makes an HTTP request to your own site’s homepage to detect cookies and scripts. It does not connect to any external service.