georgelane2

UK GDPR Compliance Checker helps UK businesses identify data protection compliance gaps on their WordPress websites. The plugin scans for missing legal documents and common GDPR issues, providing actionable guidance.
What This Plugin Checks:
<ul>
<li>Privacy Policy – Detects if you have a privacy policy page</li>
<li>Terms of Service – Checks for terms and conditions pages</li>
<li>Cookie Policy – Identifies cookie policy pages</li>
<li>WordPress Privacy Settings – Verifies your privacy page is configured</li>
<li>Cookie Consent – Detects cookie consent banner plugins</li>
<li>Form Consent – Checks contact form plugins for GDPR features</li>
<li>SSL/HTTPS – Confirms your site uses encryption</li>
</ul>
Why You Need This:
UK businesses that collect personal data must comply with the UK GDPR, PECR (cookie regulations), and the Data Protection Act 2018. The Information Commissioner’s Office (ICO) can issue fines up to £17.5 million for serious breaches.
This plugin gives you a clear compliance score and identifies exactly what’s missing from your site.
Features:
<ul>
<li>One-click compliance scan</li>
<li>Clear pass/warning/fail status for each check</li>
<li>Compliance score percentage</li>
<li>Dashboard widget for at-a-glance status</li>
<li>Admin notices for critical issues</li>
<li>Links to generate missing documents</li>
<li>No account required</li>
<li>Completely free</li>
</ul>
Built for UK Businesses:
This plugin specifically checks for UK GDPR and PECR compliance requirements, not US or EU regulations. The guidance and legal requirements referenced are specific to United Kingdom law.

UK GDPR Compliance Checker

Scans your WordPress site for GDPR compliance issues and missing legal documents. Built for UK businesses.

Javi Moncayo

This is the long description. No limit, and you can use Markdown (as well as in the following sections).
For backwards compatibility, if this section is missing, the full length of the short description will be used, and 
Markdown parsed.
A few notes about the sections above:
<ul>
<li>“Contributors” is a comma separated list of wp.org/wp-plugins.org usernames</li>
<li>“Tags” is a comma separated list of tags that apply to the plugin</li>
<li>“Requires at least” is the lowest version that the plugin will work on</li>
<li>“Tested up to” is the highest version that you’ve successfully used to test the plugin. Note that it might work on 
higher versions… this is just the highest one you’ve verified.</li>
<li>
Stable tag should indicate the Subversion “tag” of the latest stable version, or “trunk,” if you use <code>/trunk/</code> for 
stable.
Note that the <code>readme.txt</code> of the stable tag is the one that is considered the defining one for the plugin, so 
if the <code>/trunk/readme.txt</code> file says that the stable tag is <code>4.3</code>, then it is <code>/tags/4.3/readme.txt</code> that’ll be used 
for displaying information about the plugin. In this situation, the only thing considered from the trunk <code>readme.txt</code> 
is the stable tag pointer. Thus, if you develop in trunk, you can update the trunk <code>readme.txt</code> to reflect changes in 
your in-development version, without having that information incorrectly disclosed about the current stable version 
that lacks those changes — as long as the trunk’s <code>readme.txt</code> points to the correct stable tag.
If no stable tag is provided, it is assumed that trunk is stable, but you should specify “trunk” if that’s where 
you put the stable version, in order to eliminate any doubt.
</li>
</ul>
<h3>Arbitrary section</h3>
You may provide arbitrary sections, in the same format as the ones above. This may be of use for extremely complicated 
plugins where more information needs to be conveyed that doesn’t fit into the categories of “description” or 
“installation.” Arbitrary sections will be shown below the built-in sections outlined above.
<h3>A brief Markdown Example</h3>
Ordered list:
<ol>
<li>Some feature</li>
<li>Another feature</li>
<li>Something else about the plugin</li>
</ol>
Unordered list:
<ul>
<li>something</li>
<li>something else</li>
<li>third thing</li>
</ul>
Here’s a link to <a href="https://wordpress.org/" title="Your favorite software" rel="ugc">WordPress</a> and one to <a href="http://daringfireball.net/projects/markdown/syntax" title="Markdown is what the parser uses to process much of the readme file" rel="nofollow ugc">Markdown’s Syntax Documentation</a>. 
Titles are optional, naturally.
Markdown uses email style notation for blockquotes and I’ve been told:
<blockquote>
Asterisks for emphasis. Double it up for strong.
</blockquote>
<pre><code><?php code(); // goes in backticks ?>
</code></pre>

Metawash

Metadata clean as heaven

Here is a short description of the plugin.  This should be no more than 150 characters.  No markup here.

UK GDPR Compliance Checker vs Metawash