GDPR for Magento 2
Strengthen data security and privacy by giving customers full control of their personal data.
- Dedicated functionality allows you to comply with GDPR, specifically the right to be informed, access, erasure, and data portability rights
- Data protection policy consents are collected on registration, checkout, and other pages
- Improved customer accounts allow customers to ask to delete or copy their personal data
- Allow customers to download their personal data automatically in PDF or XML formats
- Customer verification mechanism protects data against fraudulent activity
- Extension grids segment customers by their statuses and intentions
How Magento 2 GDPR works
Solution. The main requirements of GDPR imply the following rights for customers:
- The storage of personal data and its use have to be approved by customers consciously and unambiguously;
- The module records consent date and time;
- Customers are able to access and obtain their data both in human- and machine-readable formats (pdf and xml);
- Customers can demand data removals if they do not want it to be further used and processed.
Although, the requirements are quite simple it can be difficult to keep big or external databases and services compliant with them, which is the main purpose of the GDPR extension for Magento 2.
It allows you to closely track the status of customers with or without consent, delete personal data of customers; it allows customers to request a copy of the stored data, and ask to delete the information.
First of all, the module ensures that all the customers, including guests, provide their consent on registration and checkout pages.
Second, you can track the status of your customers in one place in the backend, export the lists of customers with no consents and follow them by any means.
Third, you can receive and process the requests to obtain and erase personal data from multiple customers.
Goal. Provide your customers with the access to their personal data according to the GDPR requirements.
Solution. Even several extra tickets submitted to your help desk set an unwanted tension in the support department. So, if you start receiving dozens of personal data access requests a day, it may cause overstrain and totally stop the whole process.
Another thing is if shoppers ask for their personal data directly from their accounts and do not affect the work of your customer service. Then, you can easily filter out all that kind requests, export them in one list, in order to use it in some third-party solutions to follow customers, download the corresponding data, and send it to customers at a time.
Personal data can be delivered in two ways:
- Right of access - customers can request request a copy of their personal data in PDF;
- Right of data portability - data can be obtained in the machine readable format (XML).
Data access requests are verified by email, so you could weed out malicious requests. Besides, the provided API, makes it possible to take data from some third-party applications involved.
Result. The result is that the customer service is not overloaded with irrelevant inquiries and is able to provide the same high level of services. Meanwhile, you can organize the work of your support department to satisfy requests of your customers within a legitimate timeframe defined by GDPR (30 calendar days).
Goal. Allow customers to delete their information stored in your databases according to the GDPR requirements.
Solution. Art. 17 of GDPR is clear about the right to erase someone's personal data wherever it is stored: “The data subject shall have the right to obtain from the controller the erasure of personal data concerning him or her without undue delay and the controller shall have the obligation to erase personal data without undue delay..”
There are several reasons for the erasure, but the opportunity to withdraw the consent makes this case applicable to almost any situation. So, in order to successfully resolve the issue, you need to collect and process erasure requests effectively, which is the very functionality provided by the GDPR extension.
In order to use the “right to be forgotten” customers can use the Delete My Account button in their accounts. The Removal Requests grid in the backend contains all the submitted delete requests. Magento admins are able to delete the corresponding data right here (except the order information as it's a subject to local legislation) and export the list of requests to be processed in other third-party systems, where the personal information can be additionally stored.
The same as with the right to access and data portability right all the submitted requests are verified by email, while the API allows extracting data from the engaged third-party solutions.
Result. This way, you can erase the personal data requested to be deleted or any other customer information you don’t want to be stored. The whole process takes only several minutes and is not going to be irksome for your staff.
So, now the given consents are not valid anymore and you need to get them again, which is very embarrassing. However, the GDPR extension is able to make the process much faster and simpler.
The status of customers related to the new policy terms is tracked via the Consent Relevance grid, which also contains the date when the latest consent was provided by customers.
Result. The process of getting compliant with the latest legislation changes becomes much simpler, consciously manageable and trackable.
Magento 2 GDPR Detailed Feature List
Customer Account Area
Customer Base Management
Data Protection Policy Consent
Change Data Protection Policy
* Fixed issue for Magento Marketplace
* Fixed issue with ACL
* Fixed issue for Magento Marketplace
+ Allow customers to download their personal data automatically
+ Email template for data access request
+ UI, UX improvements
+ Web API update
* When new Store View is enabled, "Consent Relevance" page isn't opened
* Welcome message is present on Storefront after removal request is complete
* Fixed issue when Consent Popup does not appear on checkout
+ Compatibility with mpdf version 8
* Error occurs on an attempt to open the "Consent Relevance" grid (Magento Commerce 2.3.2)
* Fixed issue with 'PayPal Express Checkout'
* Fixed issue when data are not entirely removed
+ Magento 2.3 compatibility