WordPress plugin intelligence profile

Lexiscript Consent & Privacy

Blocks non-essential trackers until your visitor consents, applying the consent model of their own region. Free for one website.

WP PlugIndex snapshot

Current directory snapshot

Tested up to WordPress 7.1
Current version1.0.1
WordPress coverageTested up to WordPress 7.1
Minimum stackWP 6.0 · PHP 7.4
Directory statusactive
Last directory update29 Oct 20265d ago
Active installationsNewAdoption metric — not a quality score
WordPress.org ratingNo WordPress.org ratings yet
Official packageDirect from WordPress.org

Repository metrics are context, not quality scores. Active installations measure adoption and can strongly reflect a plugin’s age and historical popularity. Ratings, recent updates and “Tested up to” metadata also do not guarantee modern code, error-free operation, security, feature completeness or suitability for a particular site. Why active installs don’t tell the whole story →

WP PlugIndex currently records Lexiscript Consent & Privacy version 1.0.1 as active, updated 5d ago and tested up to WordPress 7.1.

Overview

About this plugin

Most consent banners describe what a site does. This one changes it.

The Lexiscript widget intercepts the browser APIs that scripts use to insert themselves, so a

tracker is caught at the moment it tries to load rather than disclosed after it has already run.

Non-essential scripts do not execute until the visitor has agreed — and what counts as agreement

depends on where that visitor is.

Region-aware by default. A visitor in Germany, one in California and one in Kenya get

different behaviour from the same installation. The widget applies one of three consent models

according to the visitor’s location:

  • Opt-in, where nothing runs until consent is given: EU, UK, Kenya, Nigeria, Brazil
  • Opt-out, presented as “Do Not Sell or Share”: California
  • Notice-only: South Africa, Canada

These groupings reflect how Lexiscript reads the published rules for each region. They are a

product configuration, not a legal determination about your site — see “Not legal advice” below.

What the widget does on your site

  • Blocks non-essential scripts before they run, rather than describing them afterwards
  • Shows a preference centre with per-category choices, not all-or-nothing
  • Gives “Reject all” the same prominence as “Accept”
  • Pre-ticks nothing under an opt-in model
  • Honours the Global Privacy Control signal automatically
  • Treats a stored decision as expired after the configured lifetime
  • Invalidates previous consent when the tracker set changes, because the visitor never agreed

to the new ones

  • Never blocks the page itself — the scripts are blocked, not your content
  • Fails closed: if the configuration cannot be reached, it serves deny-all rather than letting

everything through

  • One small vanilla JavaScript file, no framework, no dependencies

Why this plugin exists

The widget is one script, and the only thing that is easy to get wrong is where it goes — it must

run before every other script on the page or it has nothing left to intercept. This plugin

registers it with WordPress’s script loader and prints it at the top of the document head, ahead

of the tags that themes and other plugins add, and keeps it there through theme changes.

Plans and pricing

A Lexiscript account is free, and so is scanning your site and reading the findings. The

free plan also runs the consent widget on one website, which is all most sites need.

If your Lexiscript account holds more than one website, the free widget serves the first one you

added. The others will not return a configuration, and no banner will appear on them, until you

move to a paid plan.

A paid plan adds unlimited websites, an automatic monthly re-scan of each, and a generated

privacy notice per region supplied as an unreviewed template for your own sign-off.

Nothing stops working after a trial period. Current pricing is on

com/lexiscript.

External service

This plugin requires a Lexiscript account and loads a script from Lexiscript, a service operated

by Jaydee Innovation Hub (Nairobi, Kenya). The plugin does not function without it.

  • The plugin registers and prints one script, served from https://widget.jaytechkenya.com,

with your site key as a query parameter. This is Lexiscript’s own service endpoint, not a

general-purpose third-party CDN, and the script is the service.

  • That script runs in your visitors’ browsers. It requests your site’s consent configuration

from Lexiscript, and the visitor’s IP address is used at the edge to resolve their country —

and US state where relevant — in order to decide which consent model applies. The IP address

is used for that lookup and is not retained as part of a visitor profile.

  • The visitor’s own consent choices are stored in their browser. They are not sent to

Lexiscript.

  • This plugin itself makes no requests to Lexiscript from your server, and reads or transmits

nothing from your WordPress database.

  • Service terms: https://jaytechkenya.com/terms
  • Privacy policy: https://jaytechkenya.com/privacy
  • About the service: https://jaytechkenya.com/lexiscript

Not legal advice

Lexiscript reports what your website does and which published rules are relevant to it. It does

not determine whether your site is lawful, it does not make your site compliant with any law,

and nothing it produces is legal advice. Whether your use of this plugin meets your obligations

is a question for your own adviser.

WordPress.org metadata

Plugin tags

Topics listed for this plugin in the WordPress.org directory.

  • ccpa
  • consent
  • cookies
  • gdpr
  • privacy
Compatibility & maintenance

Compatibility & maintenance

Tested with WP 7.1

Marked as tested with the current WordPress 7.1 release.

Current WordPress releaseWordPress 7.1
WordPress.org Tested up to7.1
Minimum requirementsWordPress 6.0 · PHP 7.4
Update activity29 Oct 20265d ago

“Tested up to” is directory metadata supplied by the plugin author. WP PlugIndex does not turn an older declaration into a claim that the plugin is incompatible.

Changes recorded by WP PlugIndex

Recent tracked changes

WordPress compatibility7.1.37.1.4
Version1.0.01.0.1
Tracking & source

WP PlugIndex tracks public WordPress.org directory metadata and records selected version, compatibility and availability changes as they are detected.

Plugin watchlist

Watch this plugin

Sign in to your WP PlugIndex account or create a free account. Free accounts can watch up to 5 plugins and see what changed.

Watch limit

Watchlist limit reached

You have reached your current active watch limit.