Data443 Risk Mitigation, Inc.

The easiest way to make your Gravity Forms GDPR compliant!
This plugin is a service of <a href="https://data443.com" rel="nofollow ugc">Data443</a>.
Data443 is a Data Security and Compliance company traded on the OTCMarkets as <a href="https://www.otcmarkets.com/stock/ATDS/overview" rel="nofollow ugc">ATDS</a>. We have been providing leading GDPR compliance products such as Global Privacy Manager (<a href="https://www.data443.com/global-privacy-manager/" rel="nofollow ugc">Data443™ Global Privacy Manager</a>), Blockchain privacy, and enterprise cloud eDiscovery tools.
This plugin adds new privacy features to Gravity Forms. Your visitors can download or delete their form submissions automatically or submit a request for the site admin to do so.
Until WordPress releases their own GDPR compliance update, this plugin requires <a href="https://wordpress.org/plugins/gdpr-framework/" rel="ugc">The GDPR Framework</a> to function (it’s free!)
Make sure to also read the guide! You don’t need to drown your customers in pointless acceptance checkboxes if you know what you’re doing!
<h3>Disclaimer</h3>
Using Gravity Forms: GDPR Add-On does NOT guarantee compliance to GDPR. This plugin gives you general information and tools, but is NOT meant to serve as complete compliance package. Compliance to GDPR is risk-based ongoing process that involves your whole business. Data443 is not eligible for any claim or action based on any information or functionality provided by this plugin.
<h3>Documentation</h3>
How to use this plugin (practical guide): <a href="https://data443.atlassian.net/servicedesk/customer/portal/2/article/28246137" rel="nofollow ugc">Making your Gravity Forms GDPR-compliant</a> 
How to use this plugin (the legal stuff explained): <a href="https://data443.atlassian.net/servicedesk/customer/portal/2/article/2079293576" rel="nofollow ugc">Legal grounds for processing data</a> 
Full documentation: <a href="https://data443.atlassian.net/servicedesk/customer/portal/2/article/2078998660" rel="nofollow ugc">The WordPress Site Owner’s Guide to GDPR</a> 
For developers: <a href="https://data443.atlassian.net/servicedesk/customer/portal/2/article/2082439194" rel="nofollow ugc">Developer Docs</a> 
Knowledge Base: <a href="https://data443.atlassian.net/servicedesk/customer/portal/2/article/192708653" rel="nofollow ugc">Knowledge Base</a>
<h3>Features</h3>
☑ Allow both users and visitors without an account to view, export and delete their form submissions or request the site admin to do so; 
☑ Configure forms to be excluded from viewing, exporting or deleting. 
☑ Support for anonymization: allow admin to select which fields must be anonymized; 
☑ Track, manage and withdraw consent.

Gravity Forms: GDPR Framework Add-On

The easiest way to make your Gravity Forms GDPR-compliant. Fully documented, extendable and developer-friendly.

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.

Gravity Forms: GDPR Framework Add-On vs Metawash