Santiago Alonso

Técnico RGPD

marinabrocca

<p>Adapt your e-commerce to the GDPR rules.</p>
<p>This plugin allows you to easily add a check box to the woocommerce checkout to obtain the consent of the users before sending them promotions.</p>
<p>In addition, you can add the first layer of privacy before completing the checkout, as required by the RGPD.</p>
<h3>GDPR Promo consent</h3>
<p>With RGPD/GPDR Settings for WooCommerce you can include an optional checkbox in your checkout to obtain your user’s consent for send news and promotions later.</p>
<p>You can check the user consent in the admin order details and also in the admin new order email.</p>
<h3>GDPR top privacy layer</h3>
<p>According GDPR rules you need to include a simple extract about your privacy policies near to your place order button.</p>
<p>With RGPD/GPDR Settings for WC you can customize this first privacy layer easily too.</p>
<h3>GDPR Settings tab</h3>
<p>You can customize your GDPR texts under a new setting tab in the WooCommerce settings page</p>
<h3>Plugin compatibility</h3>
<p>RGPD/GPDR Settings for WC will work with WooCommerce and all WordPress themes or any visual builder like Divi, Elementor, WPBakery, etc.</p>
<p>This plugin use native WooCommerce hooks for total compatibility.</p>


GDPR Settings for WooCommerce

Adapt your e-commerce to the GDPR rules. This plugin allows you to easily add a check box to the woocommerce checkout to obtain the consent of the us …

arena

<p>GDPress is providing tools for privacy and more.</p>
<p>Major features in GDPress include :</p>
<ul>
<li>a privacy request form</li>
<li>a menu in the admin_bar to see at once confirmed privacy requests</li>
</ul>
<p>and since version 2.0 a set of tools to help you comply with GDPR<br />
* a set of protection and wellness tools, because protecting personal data starts with a healthy and protected installation to prevent potential data breach.<br />
* a RoPA assistant to help you building your Records of Processing Activities – a GDPR obligation (Article 30).<br />
* a logging of all events related to export/erase requests by/for the data subject (see settings page).<br />
* a specific wp role for dpo.<br />
* and a dedicated Privacy/GDPR/ISO27701 dashboard for your d.p.o. !</p>
<p>GDPR compliancy is a never ending process.</p>
<h3>Technical Details</h3>
<p>n/a</p>
<h3>Privacy</h3>
<p>GDPress is not calling any external web services<br />
and is not using any external software other than WordPress core.</p>
<p>GDPress stores events related to the data subject and core privacy processes if archive setting is set.<br />
Archives are under the authority of the Data Protection Officer for legal purpose ONLY.<br />
They are retrieved to the data subject, but not deleted.</p>
<h4>Accountability/Auditability</h4>
<p>These are legal obligations in GDPR. In front of your local data protection authority or a judge :<br />
* You are accountable of your actions to reach GDPR compliancy and must prove it (activating this plugin is not enough).<br />
* If sued, you will have to provide some evidence : you acted lawfully and replied to the request of the data subject (archive all activities for Legal Purpose is allowed in GDPR and must be declared in your Records of Processing Activities).</p>
<h4>Other Major Obligations</h4>
<ul>
<li>Records of Processing Activities, expecting WordPress team to publish it for core. And for any theme or plugin, adding a new Privacy Section in readme.txt is a must do.</li>
<li>Communication of a personal data breach to the data subject (and to your local D.P.A.)</li>
</ul>
<h4>Privacy by design</h4>
<p>This concept is in GDPR too. In wp, Privacy is a component like Gutenberg, Admin, wp-cron …<br />
Privacy by design is or should be declined and included in ALL wp components. Should all components publish their “Privacy Section” just like the above recommandation for themes and plugins ?</p>
<h4>Pending Questions</h4>
<ul>
<li>Privacy settings in core : only one setting on a unique page that cannot be amended (no hook) : the privacy policy page</li>
<li>any privacy request is a personal data and should be retrieved to the data subject</li>
<li>removing an export request do not delete the export file (security issue, potential data breach)</li>
<li>external processors to be identified (privacy by design)</li>
<li>Gutenberg blocks coherence with embed handlers and oembed providers as set on the server side (privacy by design)</li>
<li>oEmbed responses cached in transients (no more postmeta html cached) for blog posts or oembed providers (privacy by design)</li>
<li>ability to remove blocks in Gutenberg such as “/map” for Mapbox (privacy by design)</li>
<li>future “Icon” component : from Dashicons to svg  (privacy by design)</li>
<li>Nowadays, emails such as “θσερ@εχαμπλε.ψομ” are valid but rejected by wp function is_email() (privacy requests rejected)<br />
Web standards should apply and this can be a legal issue : one of the “variety of privacy issues around the world” !</li>
</ul>


GDPR Settings for WooCommerce vs GDPress