Izini Consent Banner

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.

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.