Magento Module AVG/GDPR/RTBF

Product Description

Available for version: 1.x,2.x (other versions are available on request)

This AVG / GPDR module ensures that you can comply with the AVG (General Data Protection Regulation) rule "right to be forgotten" (GPDR: Right To Be Forgotten (RTBF)). Normally your customer can view and modify all his data in the My Account environment of Magento. With this Magento module of Vicus your customer can also delete his data.

For the one-time license fee per Magento installation, you can fill out the 'The Right to be Forgotten' section very easily GDPR compliant.

Vicus installs this module in your own Magento and sets it up to 1 storefront/1 language for you. If you have more storefronts/languages in your shop you can use the manual provided to set up the configurations for the other shops yourself, or you can contact the service desk of Vicus to do so. You only have to supply the texts that you want to show to your customers.

Global operation:

• the customer logs into their account;
• the customer indicates that he wants to delete his data and agrees with the displayed text;
• additional click;
• data will be deleted;
• Customer is logged out and sent to confirmation screen of the web shop.

You decide which data is deleted via configuration:

• account/contact;
• quotes;
• orders *;
• Bills *;
• credit notes *;
• news-letters etc. (multi/select);
• note/status archive.

* Orders, credit notes and invoices must be configurable for the merchant. After all, there is a legal obligation to retain and this is only possible if the official files are in an ERP system or copy archive.

This AVG/GDPR Magento plug-in has 3 purposes:

1. give the customer the opportunity to communicate about the topic from the shop with the merchant;
2. Give the merchant the information (now through an email) that the customer has made a request for information or deletion;
3. Give the merchant the option to have the data automatically removed or anonymized from the web shop(!) immediately.

These three goals can be achieved.

Your accounting, ERP, social medio (Facebook, LinkedIn), mailing, crm programs will probably also contain information that should be the deleted. This cannot be controlled directly from the plug-in. That's where the privacy policy comes into play in conjunction with the BCC email. The recipient of the internal email will then have to initiate actions from the policy (and perhaps eventually delete the email in question).

For your back-office, this means that for that customer, you need to make the debtor or contact web-client-ready. (And may also need to remove from MailChimp, Facebook and LinkedIn friends)

Because of the flexible set-up, you can actually decide exactly what you do and what you communicate to your client.

Global operation

• Create email and cms templates
• Set up the configuration as desired

It depends on your own internal privacy policy as to how the customer's request will be dealt with. To share that policy with the customer you can use Magento's standard content blocks and email templates to communicate with the customer about it.

• Choose the desired cms block and email template;
• Make sure the texts in cms block and email template match the other settings and your own privacy policy;
• Important choices are whether to delete the customer's data or still keep it anonymized;
• Set which customer data you delete or anonymize;
• Set whether the account should be deleted.

So you can decide for yourself how to organize your privacy policy. This module is not dependent on any changed legislation or jurisprudence. You can simply adjust the texts and the configuration.