Install the module

Usage

Account deletion and anonymization can be done in 'My Account > Privacy Settings'.

Customers can use their 'right to be forgotten'. The password is required to ensure the customer legibility.
The account will be erased within 1 hour, or as specified in configuration. The customer can undo the action in this time span.

Cookie Policy in a disclosure popup are shown at the first time customer visit.

Settings

The configuration for this module is located in 'Stores > Configuration > Customers > Customer Configuration > Privacy (GDPR)'.
The settings are divided as following:

General Settings

Enable the module

GDPR Information CMS Page

GDPR Information CMS Block

Erasure Settings

Enable the feature

Erasure Strategy (Anonymize or Delete)

Erasure Time Laps

Cron Scheduler

Right to Erasure Information CMS Block

Anonymization Information CMS Block

Remove Customer if no Orders

Apply Deletion Strategy to specific components

Export Settings

Enable the feature

Export Personal Data Information CMS Block

Export Renderer option

Customer Attributes to export

Customer Address Attributes to export

Cookie Settings

Enable the cookie disclosure

Cookie Policy Information CMS Block

Developers

The following documentation explains how to add your own processors to the workflow.

Extends Export

In order to export your custom component, you must create a new processor.
To create a new processor, you must implement the following interface: \Opengento\Gdpr\Service\Export\ProcessorInterface.
Then, register your processor to the following pool \Opengento\Gdpr\Service\Export\ProcessorPool, as described:

You can also create your custom export renderer to make it as be like you want to be.
To achieve this, you must implement the following interface: \Opengento\Gdpr\Service\Export\RendererInterface
Then, register your renderer to the following pool \Opengento\Gdpr\Service\Export\RendererPool, as described:

Extends Deletion

In order to delete your custom component, you must create a new processor.
To create a new processor, you must implement the following interface: \Opengento\Gdpr\Service\Delete\ProcessorInterface.
Then, register your processor to the following pool \Opengento\Gdpr\Service\Delete\ProcessorPool, as described:

Extends Anonymization

In order to anonymize your custom component, you must create a new processor.
To create a new processor, you must implement the following interface: \Opengento\Gdpr\Service\Anonymize\ProcessorInterface.
Then, register your processor to the following pool \Opengento\Gdpr\Service\Anonymize\ProcessorPool, as described:

Erasure Strategy

This module allows you to define the strategy to apply for the different processors.
You can configure it thanks to the admin system configuration, but you can also cheat and
define the strategy to apply for them via the etc/di.xml file. Be careful, the settings from the configuration
are always checked in top priority. To make it via the code, add your preferences as following:

Warning, if you want to implement your own strategy type, you must create your own strategy class object, but you will be able to use the Opengento\Gdpr\Model\Config\ErasureComponentStrategy to serve your components by strategy.
Do not forget to use the right services managers, but you are free to use yours:

Opengento\Gdpr\Service\AnonymizeManagement

Opengento\Gdpr\Service\DeleteManagement

Support

Raise a new request to the issue tracker.
Please provide your Magento 2 version and the module version. Explain how to reproduce your issue and what's expected.