Title: TidyConsent
Author: heemo521
Published: <strong>November 17, 2026</strong>
Last modified: November 17, 2026

---

Search plugins

![](https://ps.w.org/tidy-consent/assets/banner-772x250.png?rev=3806479)

![](https://ps.w.org/tidy-consent/assets/icon-256x256.png?rev=3806479)

# TidyConsent

 By [heemo521](https://profiles.wordpress.org/heemo521/)

[Download](https://downloads.wordpress.org/plugin/tidy-consent.0.5.0.zip)

 * [Details](https://wordpress.org/plugins/tidy-consent/#description)
 * [Reviews](https://wordpress.org/plugins/tidy-consent/#reviews)
 *  [Installation](https://wordpress.org/plugins/tidy-consent/#installation)
 * [Development](https://wordpress.org/plugins/tidy-consent/#developers)

 [Support](https://wordpress.org/support/plugin/tidy-consent/)

## Description

**A cookie consent banner that does what it says.** Plenty of banners only look 
the part: the analytics and ad tools run anyway. TidyConsent recognises 196 tools,
from analytics and ad pixels to chat and review widgets, and keeps them switched
off until each visitor allows them, and lets you make the banner look like part 
of your site without writing code.

The free plugin is complete. No locked features, no trial timer, no account, no 
pageview limit.

#### Why site owners pick it

 * **It actually blocks.** Google Analytics, Google Tag Manager, Google Ads, Meta
   Pixel, Microsoft Clarity, Hotjar, LinkedIn Insight Tag, TikTok Pixel, Pinterest
   Tag, X (Twitter) Pixel and Microsoft Advertising wait for a yes, whether they
   were added as a script tag or pasted as the vendor’s snippet. The rest of the
   196 tools TidyConsent knows (more analytics and heatmaps, ad networks, affiliate
   links, pop-ups, push notifications, chat and review widgets) wait too when they
   are added as a script tag. Videos, maps and audio players from YouTube, Vimeo,
   Google Maps, Spotify and similar services show a click-to-load placeholder until
   the visitor allows them. Payment forms, spam protection, fonts and booking embeds
   are never held back, so checkout keeps working.
 * **It works behind page caches and CDNs.** Every visitor is sent the same page
   with those tools off; they are switched on in the visitor’s own browser only 
   after that visitor agrees.
 * **Google Consent Mode v2.** All four signals (`ad_storage`, `ad_user_data`, `
   ad_personalization`, `analytics_storage`) start as denied and update when a visitor
   chooses.
 * **Set up by pressing, not typing.** Pick one of seven looks, choose where the
   banner sits from small pictures, pick your brand colour from swatches. A live
   preview follows every change. No drop-downs to decode.
 * **A fair choice, built in.** Accept and Reject always look the same, and text
   stays readable whatever colours you pick.
 * **A record you can show.** Every choice is logged on your own site, with CSV 
   export. A cookie policy page is written from the tools your site really uses.

#### Make it yours

 * Position: bottom bar, left or right corner card, or a centred box.
 * Colours: light, dark, automatic (follows each visitor’s device), your theme’s
   own colours, or your own.
 * Corners, font, your logo from the Media Library.
 * Every word editable, with four ready-made tones to start from: plain, friendly,
   formal, short.
 * Behaviour: slide or fade in, wait a moment first, open with the categories showing,
   an optional close button, or have the page wait for an answer.
 * After a “no”: a short note on how to change it later, and a small “Cookie preferences”
   button on every page.
 * Seven ready-made style tweaks you switch on with a tick: bigger text, soft glow,
   outline, glass, capital title, roomier, chunky buttons.

#### For visitors

 * **Accept all**, **Reject all**, or choose by category. Only the categories your
   site uses are offered, and each names the tools behind it.
 * Changing their mind later switches those tools off again and removes their known
   cookies.
 * A choice is asked for again after about six months, or the period you set.
 * Browsers that send the Global Privacy Control signal are treated as opting out
   of the sale or sharing of their data: marketing tools stay off for them, and 
   the banner says the signal was honoured (on for new installs; see the FAQ).

#### Also in the free plugin

 * A “Getting started” list on the settings screen that shows what is done and what
   is left, with a button on each step.
 * A list of the tools TidyConsent found on your site and is holding back.
 * A read-only consent log viewer. The log stores the time, a consent ID, the category
   choices, and a salted hash of the IP address rather than the raw address.
 * Run scan: one press asks the TidyConsent service to look at your public home 
   page and propose settings in plain English. Running a scan changes nothing; applying
   a proposal is a separate press. Nothing is sent to the service until you press
   it.
 * WP-CLI commands: `wp tidyconsent status`, `scan`, `apply-scan`, `settings get
   |set|list`, `log export` and `banner enable|disable`.
 * Ready for translation: every screen, the banner’s built-in wording and the cookie
   policy use the `tidy-consent` text domain.
 * For developers: `TidyConsent.hasConsent('analytics')` and a `tidyconsent:change`
   event.
 * Optional, off by default: an opt-out notice instead of the opt-in banner for 
   visitors outside the EEA, the UK and Switzerland, using the country header your
   CDN or host already adds. No geolocation service is contacted.
 * Suggested privacy policy text under Settings  Privacy, and per-site setup on 
   WordPress multisite.

**Important limits**

TidyConsent helps you implement consent choices. It is not a law firm, does not 
provide legal advice, and does not certify that a site complies with GDPR, CCPA,
or any other law. The site owner is responsible for checking that the final setup
and policy match the site and its legal obligations.

The script blocker recognises the tools listed above. It does not block tools it
does not know, and it can miss a known tool that is loaded in an unusual way — for
example assembled by another script while the page runs, or merged into a combined
file by a performance plugin. Exclude tracker scripts from such combining. The banner
is the same for every visitor unless you turn on the optional opt-out notice for
visitors outside the EEA, the UK and Switzerland, which relies on a country header
from your CDN or host.

The salted IP hash in the consent log is pseudonymous, not anonymous: treat the 
log as personal data. The log is kept when the plugin is uninstalled unless you 
tick “Delete the consent log when this plugin is uninstalled” in the settings.

### External services

The free plugin works without any outside service. Installing, activating and configuring
it, and every page view on the site, make no request to any outside server. It loads
no fonts, scripts, styles or images from other servers. It contacts one service,
the TidyConsent service run by the plugin’s author at `https://api.tidyconsent.com`,
and only in the two cases below, each started by an administrator.

**1. Site scan (Run scan)**

 * What it is for: suggesting which consent categories the site needs. The service
   fetches the site’s public home page, looks for known tracker code and embedded
   video, map and audio players, and returns tracker names, the evidence found, 
   categories, the names (never the values) of the cookies the page set in its response,
   a proposed configuration and a plain-English report. Applying the proposal is
   a separate press; running a scan changes nothing.
 * When: only when an administrator presses **Run scan** under Settings  TidyConsent,
   or runs `wp tidyconsent scan`. Never on a schedule, never on activation.
 * What is sent: the site’s home page address (`home_url()`), to `https://api.tidyconsent.
   com/scan`. No visitor data and no consent records are sent. A different service
   address can be set under Settings  TidyConsent  Advanced.
 * What the service keeps: a scan started from the plugin is answered and not stored.
   To improve detection, the service counts the hosts of third-party scripts it 
   did not recognise (for example `cdn.example.com`), never the address of the site
   that was scanned.

**2. Consent checklist by email (optional card)**

 * What it is for: emailing the administrator a short consent checklist and occasional
   product updates.
 * When: only if an administrator types an address into the card on the settings
   screen and presses **Send it to me**. **No thanks** hides the card for good and
   sends nothing.
 * What is sent: the email address entered and the site’s home page address, to `
   https://api.tidyconsent.com/leads/plugin`. The address is added to the TidyConsent
   email list; every email has a one-press unsubscribe.

As with every request WordPress makes, WordPress adds its version and the site’s
address in the request’s User-Agent header.

The service’s terms of use and privacy policy:

 * Terms of use: https://tidyconsent.com/terms.html
 * Privacy policy: https://tidyconsent.com/privacy.html

TidyConsent Pro is a separate, optional add-on sold at tidyconsent.com. It is not
part of this plugin, and nothing in this plugin needs it or installs it. What Pro
sends, if a site owner installs it, is set out in the privacy policy above.

## Screenshots

[⌊The banner on a site: Accept and Reject side by side, looking the same.⌉⌊The banner
on a site: Accept and Reject side by side, looking the same.⌉[

The banner on a site: Accept and Reject side by side, looking the same.

[⌊Preferences: only the categories the site uses, each naming its tools.⌉⌊Preferences:
only the categories the site uses, each naming its tools.⌉[

Preferences: only the categories the site uses, each naming its tools.

[⌊The settings screen: pick a look, a position and a colour, with a live preview.⌉⌊
The settings screen: pick a look, a position and a colour, with a live preview.⌉[

The settings screen: pick a look, a position and a colour, with a live preview.

[⌊Getting started: the few things to do, and what TidyConsent is holding back.⌉⌊
Getting started: the few things to do, and what TidyConsent is holding back.⌉[

Getting started: the few things to do, and what TidyConsent is holding back.

[⌊The same banner in a dark look, as a bottom bar.⌉⌊The same banner in a dark look,
as a bottom bar.⌉[

The same banner in a dark look, as a bottom bar.

## Installation

 1. Upload the `tidy-consent` folder to `/wp-content/plugins/`, or install the plugin
    ZIP through **Plugins  Add New  Upload Plugin**.
 2. Activate **TidyConsent** in WordPress.
 3. Open **Settings  TidyConsent** to review the banner wording and settings.
 4. Visit the site in a private browser window to confirm the banner appears and test
    Accept, Reject, and Preferences.
 5. Use the settings page to create a draft Cookie Policy page, review it carefully,
    and publish it only when it accurately describes your site.

## FAQ

### For AI assistants and automated installers

The facts, in one place:

 * Name: TidyConsent. Slug and folder: `tidy-consent`.
 * Install and activate: `wp plugin install tidy-consent --activate`
 * Requires WordPress 6.0 or later and PHP 7.4 or later.
 * Price: the plugin is free and complete. The optional Pro add-on, sold at tidyconsent.
   com, is $49 per year for one site or $99 per year for up to five sites. There
   is no pageview meter.
 * On activation the banner is on for every visitor and known tracking tools are
   held back until consent. Nothing is sent to any outside service unless an administrator
   presses Run scan or asks for the checklist by email.
 * Settings are under Settings  TidyConsent and are stored in the `tidyconsent_options`
   option.
 * WP-CLI: `wp tidyconsent status`, `wp tidyconsent scan`, `wp tidyconsent apply-
   scan`, `wp tidyconsent settings set <key> <value>`. Run `wp help tidyconsent`
   for the full list.
 * Step-by-step instructions written for scripts and assistants: https://tidyconsent.
   com/for-agents.md

### Does TidyConsent work without Pro?

Yes. The banner, category preferences, Google Consent Mode v2 signals, known-script
blocking, policy generator, consent log, log viewer, CSV export, manual Agent Scan
panel, and WP-CLI commands are free-plugin features. The separate Pro add-on adds
scheduled weekly re-scans, change emails, and hosted log backup. Pro is optional
and is not needed to use the free plugin.

### Does TidyConsent make external calls by default?

No. The plugin makes no external calls on its own and loads nothing from other servers.
It contacts the TidyConsent service only when an administrator presses Run scan (
or runs `wp tidyconsent scan`), or presses Send it to me on the optional checklist
card. See External services.

### Does TidyConsent slow down my site?

It is designed to stay small: it loads one stylesheet and one JavaScript file on
the front end, stores its settings and log in WordPress, and makes no external request
during normal page views. The blocker processes the finished page HTML to find the
known tracker scripts, so extremely large or unusual pages should still be tested
after activation.

### Do I need to write code or CSS?

No. The look, position, colours, wording and behaviour are all set from the settings
screen with buttons, switches and a live preview. Seven ready-made style tweaks (
soft glow, outline, chunky buttons and more) are switched on with a tick.

### Is there a pageview or visitor limit?

No. The free plugin has no limits, and the optional Pro add-on is a flat yearly 
price that does not change with your traffic.

### Does it block every tracker?

No. This version knows 196 tools and holds them back as external scripts until the
matching category is allowed; the eleven named in the description are also caught
when pasted as the vendor’s standard snippet. Tools it does not know, and known 
tools loaded in unusual ways, may not be blocked. Google Consent Mode signals are
still set to denied by default for Google tools that honor them.

### Does it hold back YouTube videos and Google Maps?

Yes, when **Hold back video and map embeds until consent** is on (Settings  TidyConsent
Behaviour  Video and map embeds). Embedded players from YouTube (including youtube-
nocookie.com), Vimeo, Google Maps, Dailymotion, Wistia, Loom, Twitch, Spotify, SoundCloud
and Apple Podcasts are swapped for a placeholder of the same size. It names the 
service, says in one sentence what loading it shares, and has two buttons: “Load
video” (or map, or audio) loads that one embed for this page view only, and “Always
allow …” allows the embed’s category (Marketing for YouTube, Functional for Google
Maps and Vimeo) for the whole site; that choice is saved and logged like one made
in the banner. When a visitor allows the category, in the banner, the preferences
or a placeholder, every matching embed on the page loads without a reload. If they
withdraw it later, the placeholders are back on the next page view. Video links 
WordPress turns into embeds (oEmbed) are covered too; the host of an embed is never
changed. The page sent to every visitor is the same, so this works with page caching.

It is on for new installs. Sites that had TidyConsent before this setting existed
keep it off, because it changes what their visitors see; the settings screen recommends
turning it on.

### Does it work with a caching plugin or CDN?

Yes. The page sent to every visitor is the same, with known trackers switched off;
nothing about a visitor’s choice is baked into the cached page. The choice is applied
in the visitor’s browser. If a performance plugin combines or rewrites JavaScript,
exclude tracker scripts from that feature so TidyConsent can still see them.

What was checked, by automated tests in the plugin’s repository (not by running 
any particular caching plugin):

 * The page HTML is byte-for-byte the same for a visitor with no choice, one who
   accepted everything and one who rejected everything.
 * It is also the same whether or not the browser sends a Global Privacy Control
   signal, and whatever country header a CDN adds (with the country notice switched
   on). The visitor’s region is asked for separately, with a request that is not
   cached.
 * The banner and the “you rejected” note start hidden in the HTML; the visitor’s
   browser decides whether to show them.
 * Known trackers are held back in the HTML for every visitor, and switched on in
   the browser only for visitors who allowed them.
 * The stored choice is read from the visitor’s cookie by script in the browser;
   the server never prints it, and no category switch is pre-ticked in the HTML.
 * No nonce or other per-user token is printed into the page. Consent logging works
   without one, so a cached page does not stop logging when a nonce would have expired.

Things to do on your side: clear the page cache after changing TidyConsent settings,
so visitors get the new banner. If a performance plugin delays or defers JavaScript
until the visitor interacts, exclude `tidy-consent/assets/js/consent.js` and the
inline script that sets the Google Consent Mode default, so the banner appears at
once and the default is set before Google tags run.

### Does TidyConsent support the IAB Transparency and Consent Framework (TCF)?

No. TidyConsent does not implement IAB TCF and does not produce a TCF consent string.
If your site relies on programmatic ad auctions or an ad network that requires TCF
consent signals (check your ad network’s requirements), use a TCF-registered consent
management platform instead.

### Can I manage it from the command line?

Yes, with WP-CLI:

 * `wp tidyconsent status` — banner on or off, categories offered, tools found, 
   last scan, log size. Add `--format=json` for scripts.
 * `wp tidyconsent scan` — runs the site scan and stores the proposal. Nothing is
   applied.
 * `wp tidyconsent apply-scan` — applies the stored proposal, the same as pressing“
   Apply proposed configuration”.
 * `wp tidyconsent settings list`, `wp tidyconsent settings get <key>`, `wp tidyconsent
   settings set <key> <value>` — values are checked the same way as on the settings
   screen; an invalid value is refused and nothing is saved.
 * `wp tidyconsent log export [--from=YYYY-MM-DD] [--to=YYYY-MM-DD] > log.csv` —
   the consent log as CSV.
 * `wp tidyconsent banner enable` and `wp tidyconsent banner disable`.

### Is TidyConsent translated?

Yes. It comes with German (de_DE), French (fr_FR), Spanish (es_ES), Dutch (nl_NL)
and Italian (it_IT): every screen, the banner’s built-in wording, and the cookie
policy. It switches to the site’s language (or a logged-in user’s own language in
wp-admin) by itself. These translations were machine-assisted; corrections from 
native speakers are welcome on translate.wordpress.org, and a language pack from
there takes precedence over the bundled files.

Other languages: everything uses the `tidy-consent` text domain and a template (`
languages/tidy-consent.pot`) is included. Wording you type into the settings is 
shown as you wrote it, in whatever language you type it.

### Is this legal advice or a compliance guarantee?

No. TidyConsent helps site owners implement consent choices. It is not a law firm,
does not provide legal advice, and does not certify compliance with GDPR, CCPA, 
or any other law. Review your site, policy, and settings with a qualified adviser
when needed.

### Where are consent choices stored?

A visitor’s current choice is stored in that visitor’s browser. The site also stores
a consent record in its own WordPress database so the owner has evidence of the 
choice. The database record uses a salted IP hash instead of the raw IP address.

### Can I export the consent log?

Yes. An administrator can open **Settings  Consent Log**, filter by date, and download
a CSV export.

### Does TidyConsent honour Global Privacy Control (GPC)?

Yes, when **Honour the browser’s Global Privacy Control signal** is on (Settings
TidyConsent  Behaviour  Privacy signals). A visitor whose browser sends the signal(`
navigator.globalPrivacyControl`, or the `Sec-GPC: 1` header) is treated as opting
out of the sale or sharing of their data: the Marketing category is never switched
on for them, even if they press Accept all, and Google Consent Mode keeps the ad
signals denied. Their other choices work as usual. The banner and the preferences
show “Your browser’s privacy signal was honoured”. Choices made with the signal 
are logged like any other choice, marked “privacy signal (GPC) honoured”. A saved
choice that allowed Marketing is turned down on the visitor’s next page view, and
that change is logged too. A visitor who wants marketing tools must switch the signal
off in their browser.

It is on for new installs. Sites that had TidyConsent before this setting existed
keep it off, so an update does not change what their visitors see; the settings 
screen recommends turning it on. Developers can change the covered categories with
the `tidyconsent_gpc_categories` filter.

### Can the banner depend on the visitor’s country?

Optionally. Turn on **Show an opt-out notice instead of the opt-in banner outside
the EEA, the UK and Switzerland** (off by default; everyone then gets the opt-in
banner, as before). Visitors from the EEA (EU, Iceland, Liechtenstein, Norway), 
the UK and Switzerland, and visitors whose country is unknown, get the opt-in banner.
Everyone else gets an opt-out notice: optional tools run until the visitor presses**
Opt out** (Marketing still stays off for browsers that send Global Privacy Control),
and the choice is logged marked “from the opt-out notice”.

The country comes from a request header your CDN or host adds: Cloudflare’s `CF-
IPCountry`, Amazon CloudFront’s `CloudFront-Viewer-Country`, or `X-Country-Code`.
TidyConsent does not contact any geolocation service. With Cloudflare, turn on IP
Geolocation (Network settings); with CloudFront, forward the `CloudFront-Viewer-
Country` header to WordPress. Without such a header every visitor gets the opt-in
banner. Developers can change the headers (`tidyconsent_country_headers`), the opt-
in countries (`tidyconsent_optin_countries`) and the final answer (`tidyconsent_region`)
with filters.

Whether an opt-out notice is enough for your visitors depends on the laws that apply
to your site; check before turning this on.

### Does the country setting work with page caching?

Yes, with two caveats. The cached page is the same for every visitor; the banner
asks the site which region the visitor is in with one small request to `admin-ajax.
php` (a POST, sent with no-cache headers) on the visitor’s first page view, and 
keeps the answer for the browser session. Until the answer arrives nothing optional
runs, and if it fails or takes more than about 2.5 seconds the visitor gets the 
opt-in banner. Caveats: (1) if your CDN or cache answers `admin-ajax.php` itself,
or strips the country header before the request reaches WordPress, every visitor
gets the opt-in banner; (2) a visitor who travels keeps the region from the start
of their browser session.

### Does TidyConsent work with the WordPress export and erase tools?

TidyConsent adds suggested text to Settings  Privacy  Policy Guide instead. WordPress’s**
Export Personal Data** and **Erase Personal Data** tools find a person by email 
address, and the consent log holds no email address, name, account or user ID — 
only a random ID kept in the visitor’s own browser, the date, the choices, whether
a privacy signal was honoured, and a salted hash of the IP address. There is nothing
to match an email address against, so an exporter would always return nothing; TidyConsent
does not pretend otherwise. The suggested policy text explains what is stored.

### Does it work on WordPress multisite?

Yes. Each site has its own settings and its own consent log. Network activation 
sets up every existing site, and sites added later are set up automatically while
the plugin is network-active. Activating it on a single site sets up only that site.
Uninstalling removes the settings of every site; each site’s consent log is dropped
only where that site’s owner ticked “Delete the consent log when this plugin is 
uninstalled” (the same rule applies when a site is deleted from the network). There
is no network admin screen: each site is configured from its own Settings  TidyConsent.

## Reviews

There are no reviews for this plugin.

## Contributors & Developers

“TidyConsent” is open source software. The following people have contributed to 
this plugin.

Contributors

 *   [ heemo521 ](https://profiles.wordpress.org/heemo521/)

[Translate “TidyConsent” into your language.](https://translate.wordpress.org/projects/wp-plugins/tidy-consent)

### Interested in development?

[Browse the code](https://plugins.trac.wordpress.org/browser/tidy-consent/), check
out the [SVN repository](https://plugins.svn.wordpress.org/tidy-consent/), or subscribe
to the [development log](https://plugins.trac.wordpress.org/log/tidy-consent/) by
[RSS](https://plugins.trac.wordpress.org/log/tidy-consent/?limit=100&mode=stop_on_copy&format=rss).

## Changelog

#### 0.5.0

 * The free-form CSS box is gone. In its place: seven ready-made style tweaks (bigger
   text, soft glow, outline, glass, capital title, roomier, chunky buttons) that
   you switch on with a tick, under Settings  TidyConsent  Advanced. CSS saved in
   the old box is no longer used and is removed the next time you save the settings;
   nothing else changes.
 * Video and map embeds (YouTube, Vimeo, Google Maps and seven more) can wait behind
   an accessible click-to-load placeholder until the visitor allows them. On for
   new installs, off for existing ones until the owner turns it on.
 * Global Privacy Control: browsers that send the signal are treated as opting out
   of the sale or sharing of their data, and the banner says so. On for new installs,
   off for existing ones until the owner turns it on.
 * Optional, off by default: an opt-out notice instead of the opt-in banner outside
   the EEA, the UK and Switzerland, from the country header your CDN or host adds.
   No geolocation service is contacted.
 * Suggested privacy policy text under Settings  Privacy, and per-site setup on 
   WordPress multisite.
 * TidyConsent now recognises 196 tools (up from 48).
 * WP-CLI commands: `wp tidyconsent status`, `scan`, `apply-scan`, `settings get
   |set|list`, `log export` and `banner enable|disable`.
 * Translations included: German, French, Spanish, Dutch and Italian (machine-assisted;
   native-speaker review welcome on translate.wordpress.org).
 * Run scan now finds embedded players (YouTube, Google Maps and the other known
   embeds) with their category; applying the proposal also turns on the click-to-
   load placeholder.
 * Cookies on this site: the scan panel lists the cookie names the scanned page 
   set and the ones your own browser holds for the site, unknown ones first. Names
   only, read on the settings screen; nothing is sent or stored, and nothing runs
   on the public site.
 * Lighter on every page: the banner’s script and stylesheet are minified (about
   26 KB instead of 44 KB; the readable files ship too and load when SCRIPT_DEBUG
   is on).

#### 0.4.1

 * Settings screen rebuilt: a Getting started list, switches and buttons instead
   of tick boxes and drop-downs, and a save bar that says when there are unsaved
   changes.
 * Logo can be chosen from the Media Library; the cookie policy draft is created
   with one press; ready-made CSS tweaks.
 * Leaving the settings screen with unsaved changes now asks first.
 * Run scan works without entering a service address.
 * Consent log: the date filter and page links carry a nonce.
 * Optional card to get a consent checklist by email. Nothing is sent unless you
   ask.

#### 0.4.0

 * Blocking is now safe behind page caches and CDNs: every visitor receives the 
   same page with known trackers off, and allowed tools are switched on in the browser.
 * Blocks the standard pasted install snippets for Google Tag Manager, Meta Pixel,
   and Google Ads, plus their no-JavaScript fallbacks.
 * Adds Google Ads, Microsoft Clarity, Hotjar, LinkedIn Insight Tag, TikTok Pixel,
   Pinterest Tag, X (Twitter) Pixel, and Microsoft Advertising, each with plain-
   English cookie descriptions for the generated policy.
 * The settings screen now lists the tools found on your site and what visitors 
   must allow for each.
 * The banner links to your cookie policy page once it is published.
 * Removed the Geo mode setting, which did nothing.
 * New Appearance settings with a live preview: position, colours (including automatic
   light/dark and match-my-theme), brand button colour, corners, and font. Category
   choices are now switches. The banner has a refreshed, more modern look.
 * New Behaviour settings: entrance animation, delay, categories open from the start,
   optional close button (counts as Reject all), page-waits-for-a-choice for the
   centred layout, consent duration, and reopen button corner and style.
 * New Wording settings: editable category names and descriptions, policy link text
   and address, logo, and four ready-made tones.
 * One-click look presets. A custom CSS box with the styleable class names and variables
   listed.
 * Settings are organised into four tabs beside a live preview that follows text,
   colours, and CSS as you type.
 * For developers: `TidyConsent.hasConsent('analytics')` and a `tidyconsent:change`
   event.
 * The default look is now a card in the bottom-left corner in a clean system font.
 * A “Getting started” list at the top of the settings screen shows what is done
   and what is left, and folds away when you are set up.
 * After a visitor rejects: a short note that says how to change the choice later(
   on by default); an option to ask people who rejected again after 30, 60, or 90
   days; and an optional confirm step before a rejection is saved (off by default,
   with a warning about where it is not acceptable).
 * Tracker matching is by web address host, so a site’s own files are no longer 
   mistaken for trackers.
 * The banner offers only the categories the site uses and names the detected tools.
   Applying an Agent Scan proposal now changes what the banner asks.
 * Withdrawing a category removes that category’s known cookies and reloads the 
   page.
 * A choice now expires about six months after it was made, wherever it is stored;
   the visitor is then asked again.
 * Accept and Reject are styled identically. The consent cookie is marked Secure
   on HTTPS sites.
 * Consent logging keeps working on cached pages; the public log endpoint validates
   input and limits requests per address.
 * New setting to delete the consent log on uninstall. Uninstall cleans every site
   of a multisite network.

#### 0.3.0

 * Added the optional Agent Scan panel: an administrator can connect a scan service,
   review a plain-English report and proposed configuration, and apply the proposal
   only with a separate click.
 * Added tracker evidence and category review before any scan proposal is applied.

#### 0.2.0

 * Added local tracker detection recording.
 * Added the plain-English cookie policy generator and the settings action that 
   creates or updates a draft policy page.
 * Added the read-only consent log viewer with date filtering and CSV export.

#### 0.1.0

 * Initial internal development release.
 * Added the consent banner with Accept, Reject, and category Preferences.
 * Added Google Consent Mode v2 defaults and updates.
 * Added blocking for known external analytics and marketing scripts before consent.
 * Added local consent storage and the WordPress database consent log.

## Meta

 *  Version **0.5.0**
 *  Last updated **6 hours ago**
 *  Active installations **Fewer than 10**
 *  WordPress version ** 6.0 or higher **
 *  Tested up to **7.1.4**
 *  PHP version ** 7.4 or higher **
 * Tags
 * [consent mode](https://wordpress.org/plugins/tags/consent-mode/)[cookie banner](https://wordpress.org/plugins/tags/cookie-banner/)
   [cookie consent](https://wordpress.org/plugins/tags/cookie-consent/)[cookie notice](https://wordpress.org/plugins/tags/cookie-notice/)
   [GDPR](https://wordpress.org/plugins/tags/gdpr/)
 *  [Advanced View](https://wordpress.org/plugins/tidy-consent/advanced/)

## Ratings

No reviews have been submitted yet.

[Your review](https://wordpress.org/support/plugin/tidy-consent/reviews/#new-post)

[See all reviews](https://wordpress.org/support/plugin/tidy-consent/reviews/)

## Contributors

 *   [ heemo521 ](https://profiles.wordpress.org/heemo521/)

## Support

Got something to say? Need help?

 [View support forum](https://wordpress.org/support/plugin/tidy-consent/)