Ago lab

aGo Legal gives WordPress sites building blocks for data protection: a configurable cookie consent banner, auto-generated privacy and cookie policies, a consent log and a registry of processing activities.
Features
<ul>
<li>Cookie consent banner with Accept / Reject (bar, modal or floating styles) and four categories (necessary, analytics, marketing, functional).</li>
<li>Auto-generated Privacy Policy based on company and DPO data and the law of your jurisdiction (GDPR, Chilean Law 21.719, LGPD or global).</li>
<li>Auto-generated Cookie Policy with the cookies present on your site (populated by the built-in scanner).</li>
<li>Consent log: every Accept/Reject is timestamped and stored locally. Each row carries a SHA-256 hash of the canonical record. Export the full log to CSV or to a self-contained HTML audit report.</li>
<li>Cookie scanner: visits your home URL and lists the cookies that get set, classifying them heuristically (necessary / analytics / marketing / functional) so the policy table reflects them.</li>
<li>RAT (Registry of Processing Activities, GDPR art. 30 / Chilean Law 21.719 art. 17): add, edit and delete activities, export them to CSV. Three common activities are seeded on activation as a starting point.</li>
<li>DPO (Data Protection Officer) name, email and phone propagate into the generated policies.</li>
<li>Shortcodes: <code>[agolegal_privacy_policy]</code>, <code>[agolegal_cookie_policy]</code>.</li>
<li>No remote calls. Everything is stored in your own database.</li>
</ul>
<h3>External services</h3>
This plugin does not connect to any external service.
<h3>Disclaimer</h3>
This plugin provides tools to help you implement data protection measures. It does not constitute legal advice and does not guarantee compliance with any law. As the site owner you are the data controller responsible for compliance. Consult a qualified professional.

aGo Legal

Cookie consent banner, privacy and cookie policy generators, audit-ready consent log, cookie scanner and processing registry (RAT).

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.

aGo Legal vs Metawash