Title: Izini Consent Banner Author: izini Published: نوومبر 7, 2026 Last modified: نوومبر 7, 2026 --- Search plugins ![](https://ps.w.org/izini/assets/banner-772x250.png?rev=3790107) ![](https://ps.w.org/izini/assets/icon-256x256.png?rev=3789845) # Izini Consent Banner By [izini](https://profiles.wordpress.org/izini/) [Download](https://downloads.wordpress.org/plugin/izini.1.4.0.zip) * [Details](https://ps.wordpress.org/plugins/izini/#description) * [Reviews](https://ps.wordpress.org/plugins/izini/#reviews) * [Installation](https://ps.wordpress.org/plugins/izini/#installation) * [Development](https://ps.wordpress.org/plugins/izini/#developers) [Support](https://wordpress.org/support/plugin/izini/) ## Description Izini is a data protection compliance service for Nigerian organisations. This plugin connects your WordPress site to your Izini project: * the Izini consent banner on every public page, loaded first, with Google Consent Mode defaults set to “denied” until the visitor chooses; * scripts you choose (from your theme, plugins or pasted snippets such as a Facebook Pixel or Google tag) held back until the visitor accepts their category: scan your home page, pick a category for each script, done (WordPress 6.9 or later); * a “Privacy choices” link (a block, the shortcode `[izini_privacy_choices]`, or a menu link to `#izini-preferences`) that reopens the banner’s preferences; * an Izini menu in wp-admin with the connection, links into your Izini dashboard( banner design, cookie scanner, consent statistics, requests from visitors) and the settings; * if the WP Consent API plugin is active, the visitor’s choice is passed to it, so plugins that read it wait for consent; * when an Izini admin, owner or Privacy Engineer connects the site: consent totals for the last 30 days (counts only) on the Izini page and the WordPress dashboard, a cookie scan of this site you can start from WordPress, and your scripts and rules on your project’s Cookies page in Izini, with the cookies well-known trackers’ vendors document for them. The banner’s wording, categories, languages and colours are set in your Izini dashboard, not in WordPress. You need an Izini account and a project. The plugin’s main setting is the project code, which is public: it appears in your pages’ source anyway. It stores no password. When the site is connected for statistics and scans, it also keeps a site token: a setting that is not loaded on public pages and is only ever sent to Izini, from this site’s server. The token reaches counts and scans of this site, never personal data; requests from people stay in Izini, behind its sign-in. The banner also holds back scripts it recognises from your project’s cookie categories( set in Izini, Consent › Cookies). Scripts you have not given a category, and that the banner does not recognise, are not held back; Google tags and plugins that read the WP Consent API wait for the choice on their own. ### External service This plugin relies on Izini, a third-party service run by Izini RegTech Ltd (Lagos, Nigeria). Nothing is loaded or sent until a site administrator saves a project code. * **On every public page**, the visitor’s browser loads the banner from https:// cdn.izini.ng and fetches the project’s banner settings from it. Like any web request, this reveals the visitor’s IP address to Izini; it is used to limit abuse and is kept only in hashed form for that. * **When the visitor makes or changes a choice**, Izini records: a random ID the banner keeps in the visitor’s browser (the `izini_user_id` cookie and local storage), the choices, the time, the language, the browser family and operating system, and the country and region worked out from the connection. No name or email address. * **From the banner’s preferences**, a visitor can download the consent choices recorded for their browser, or delete them. * **At most once a day per browser**, the banner sends Izini the names (never the contents) of cookies on your site that your project’s cookie list does not have yet, so you can review them in Izini. Nothing about the visitor is sent with them. * **When an administrator presses “Connect with Izini”**, their browser goes to https://app.izini.ng with this site’s address, a one-time code the plugin keeps for 20 minutes and a check value (the SHA-256 of a secret this site keeps). They sign in to Izini, choose a project, and come back with that project’s public code. If they are an Izini admin, owner or Privacy Engineer, a one-time grant comes back too, and this site’s server exchanges it with the secret at https:// app.izini.ng/api/v1/site/token for the site token. No password reaches this site. * **With a site token**, this site’s server calls https://app.izini.ng/api/v1/site/ with it: for the project’s consent totals and where the banner was last seen ( when an administrator opens the Izini page or the WordPress dashboard, at most every ten minutes), for the latest cookie scan (on the Izini page), and to start a scan when an administrator presses “Scan this site now” (Izini then visits this site’s home page). A token unused for 90 days stops working. * **With a site token, this site also sends Izini its scripts and rules**: the file addresses (host and path, no query string) of the scripts seen on the site or found by “Scan the home page”, the start of any inline script an administrator gave a rule, and the category each waits for. It sends them when a rule changes, after a scan, when the site is connected, and otherwise at most once a day when an administrator opens the Scripts tab. Izini drops anything that looks like a personal detail before storing it. * **When an administrator turns statistics off, connects another project, or deletes the plugin**, this site asks Izini to revoke its token. * **When an administrator connects a project, presses “Check the connection” or opens the Scripts tab**, this site asks https://cdn.izini.ng for the project’s name and categories. * **“Scan the home page”** reads this site’s own home page; nothing is sent to Izini. Izini Terms: https://app.izini.ng/legal/terms Izini privacy policy: https://www. izini.ng/privacy ## Blocks This plugin provides 1 block. * Privacy choices ## Installation 1. Install and activate the plugin. 2. In WordPress, open the Izini menu and press “Connect with Izini”: sign in to Izini, choose the project, and you are sent back with it connected. Or paste the project code from Izini (Consent › Installation) and press Save. 3. On the Scripts tab, scan your home page and give each tracking script a category. 4. Add a “Privacy choices” link to your footer or menu. ## FAQ ### Does it work with WooCommerce? Yes. The banner loads on shop, cart and checkout pages like any other page. ### I already set Google Consent Mode defaults myself Switch them off in Izini › Advanced (or with `add_filter( 'izini_consent_mode_defaults',' __return_false' );`), and the plugin will not print its own. ### How do I remove the banner? Empty the project code and save, or deactivate the plugin. Deleting the plugin revokes its site token in Izini and removes its settings. ### Why do I not see statistics in WordPress? They need the site to be connected by an Izini admin, owner or Privacy Engineer. Press “Connect with Izini” on the Overview tab and sign in as one of them. Anyone else connects the banner only. ## Reviews There are no reviews for this plugin. ## Contributors & Developers “Izini Consent Banner” is open source software. The following people have contributed to this plugin. Contributors * [ izini ](https://profiles.wordpress.org/izini/) [Translate “Izini Consent Banner” into your language.](https://translate.wordpress.org/projects/wp-plugins/izini) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/izini/), check out the [SVN repository](https://plugins.svn.wordpress.org/izini/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/izini/) by [RSS](https://plugins.trac.wordpress.org/log/izini/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 1.4.0 * With statistics and scans on, the plugin also sends Izini its scripts and rules, so your project’s Cookies page shows each script, the category it waits for, and for well-known trackers the cookies their vendors document. Izini flags a known tracker that runs before the visitor chooses, and a cookie listed in another category than its script waits for. #### 1.3.0 * Consent totals for the last 30 days on the Izini page and the WordPress dashboard, and a cookie scan of this site you can start from WordPress, once an Izini admin, owner or Privacy Engineer connects the site. The site keeps a token for this, obtained without it ever passing through the browser; it reaches counts and scans only. * Turning statistics off, connecting another project or deleting the plugin revokes the token in Izini. * Deleting the plugin now removes all its settings, not only the project code. #### 1.2.2 * Holding back scripts now filters WordPress’s own template output buffer and reads tags with the HTML API; the plugin opens no output buffer of its own. This needs WordPress 6.9 or later: on older versions the banner works as before, scripts are not held back, and the Scripts tab says so. #### 1.2.1 * Code review: the settings redirect checks the settings form’s nonce; notes on the checks that need none (the redirect from the old Settings page, the Connect with Izini return, which has its own one-time state, and WordPress’s own loopback filter). #### 1.2.0 * Privacy link tab: what the link is for and why, how it differs from a privacy policy, step-by-step guides for menus, block themes, Elementor and widget areas( the one matching your site opens first), Copy buttons, and how to check it works. * Advanced tab: Google Consent Mode explained in plain words, with what starts denied and when to switch it off; the WP Consent API status; what to do when a change does not show (caches, private windows); notes for developers. * Scripts tab: “Which category should I choose?” with examples for your project’s categories. #### 1.1.2 * Fix: a rule for inline code now holds back scripts written over several lines. The Scripts tab shows them on one line, and the rule saved from that line did not match the script as the page prints it. #### 1.1.1 * The Izini look: the Izini logo and colours, a header with the connection status, cards and tiles, and the Izini mark in the admin menu. * The Scripts list leaves out WordPress’s own admin-bar scripts. #### 1.1.0 * Its own Izini menu (Settings › Izini still works), and a notice after activation. * Scripts tab: scan the home page and hold back the scripts you choose until visitors accept their category. * Links into the Izini dashboard for this project. * Advanced tab: switch the Google Consent Mode defaults on or off. #### 1.0.0 * First release: the banner on every page, Settings › Izini with “Connect with Izini” or a pasted code, the “Privacy choices” block, shortcode and menu link, and the WP Consent API bridge. ## Meta * Version **1.4.0** * Last updated **6 ساعتونه ago** * Active installations **Fewer than 10** * WordPress version ** 6.2 or higher ** * Tested up to **7.1.4** * PHP version ** 7.4 or higher ** * Language * [English (US)](https://wordpress.org/plugins/izini/) * Tags * [consent](https://ps.wordpress.org/plugins/tags/consent/)[cookie banner](https://ps.wordpress.org/plugins/tags/cookie-banner/) [nigeria](https://ps.wordpress.org/plugins/tags/nigeria/)[privacy](https://ps.wordpress.org/plugins/tags/privacy/) * [Advanced View](https://ps.wordpress.org/plugins/izini/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/izini/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/izini/reviews/) ## Contributors * [ izini ](https://profiles.wordpress.org/izini/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/izini/)