PHPackages adexos/module-gdpr - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Utility & Helpers](/categories/utility) 4. / 5. adexos/module-gdpr ActiveMagento2-module[Utility & Helpers](/categories/utility) adexos/module-gdpr ================== Gdpr Compliance Module for Magento 2 3.0.0-beta2(7y ago)02MITPHP Since Jun 29Pushed 7y ago2 watchersCompare [ Source](https://github.com/adexos/magento2-gdpr)[ Packagist](https://packagist.org/packages/adexos/module-gdpr)[ Docs](https://github.com/adexos/magento2-gdpr)[ RSS](/packages/adexos-module-gdpr/feed)WikiDiscussions master Synced 2mo ago READMEChangelogDependencies (12)Versions (20)Used By (0) GDPR Module for Magento 2 ========================= [](#gdpr-module-for-magento-2) [![Latest Stable Version](https://camo.githubusercontent.com/6f9c8e5ba7f4ebf213643cdb968643a141a6c78181ebad898eceac3783c2ca3a/68747470733a2f2f696d672e736869656c64732e696f2f7061636b61676973742f762f6f70656e67656e746f2f6d6f64756c652d676470722e7376673f7374796c653d666c61742d737175617265)](https://packagist.org/packages/opengento/module-gdpr)[![License: MIT](https://camo.githubusercontent.com/3d3085450c989d258218b2bc1bdeb484cf160352143c0fcfdf6521a3c5e72030/68747470733a2f2f696d672e736869656c64732e696f2f6769746875622f6c6963656e73652f6f70656e67656e746f2f6d6167656e746f322d676470722e7376673f7374796c653d666c61742d737175617265)](./LICENSE) This extension allows customers to delete, anonymize, and export their personal data. - [Setup](#setup) - [Get the package](#get-the-package) - [Install the module](#install-the-module) - [Usage](#usage) - [Settings](#settings) - [Developers](#developers) - [Extends Export](#extends-export) - [Extends Deletion](#extends-deletion) - [Extends Anonymization](#extends-anonymization) - [Erasure Strategy](#erasure-strategy) - [How to override class and methods](#how-to-override-class-and-methods) - [Support](#support) - [Authors](#authors) - [License](#license) Setup ----- [](#setup) Magento 2 Open Source or Commerce edition is required. The Version `3.x` is compliant with Magento `2.3.x`. The Version `2.x` is compliant with Magento `2.2.x`. The Version `1.x` is compliant with Magento `2.1.x`. This module does not support Magento `2.0.x`, as this version is not anymore maintained. ### Get the package [](#get-the-package) **Zip Package:** Unzip the package in app/code/Opengento/Gdpr. **Composer Package:** ``` composer require opengento/module-gdpr ``` ### Install the module [](#install-the-module) Then, run the following magento command: ``` bin/magento setup:upgrade ``` **If you are in production mode, do not forget to recompile and redeploy the static resources.** Usage ----- [](#usage) - **[Art. 17 GDPR](https://gdpr-info.eu/art-17-gdpr/)** - 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. - **[Art. 20 GDPR](https://gdpr-info.eu/art-20-gdpr/)** - Personal data export can be done in 'My Account > Privacy Settings'. - Customers can export their data in `.zip` archive containing file, `.html` (many others are available), with personal data. - Cookie Policy in a disclosure popup are shown at the first time customer visit. Settings -------- [](#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 ---------- [](#developers) The following documentation explains how to add your own processors to the workflow. ### Extends Export [](#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: ``` \Vendor\Module\ExportProcessor ``` 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: ``` \Vendor\Module\ExportRenderer ``` ### Extends Deletion [](#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: ``` \Vendor\Module\DeleteProcessor ``` ### Extends Anonymization [](#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: ``` \Vendor\Module\AnonymizeProcessor ``` ### Erasure Strategy [](#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: ``` Opengento\Gdpr\Service\ErasureStrategy::STRATEGY_ANONYMIZE Opengento\Gdpr\Service\ErasureStrategy::STRATEGY_DELETE custom_strategy_code ``` 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` ### How to override class and methods [](#how-to-override-class-and-methods) Plugins and preferences are not needed here to override and extends the GDPR module core code. Actually, you should apply patterns to achieve it. The pool pattern already allows you to override the class of your choice. However you wont be able to extends the existing class, because of the "final" keyword. Indeed, you need to create your own class which implements the same interface. Then, simply add the class you want to "extends" as a composition. You will be able to exploit the result and override it in your method. Eg: ``` interface I { public function execute(array $data): array; } final class A implements I { public function execute(array $data): array { //process $data } } final class B implements I { private $a; public function __construct(A $a) { $this->a = $a; } public function execute(array $data): array { $resultA = $this->a->execute($data); $resultB = $resultA; // transform $resultA return $resultB; } } ``` Then: ``` A ``` Override by: ``` B ``` Congrats! You have overridden class A without extending it! Support ------- [](#support) Raise a new [request](https://github.com/opengento/magento2-gdpr/issues) to the issue tracker. Please provide your Magento 2 version and the module version. Explain how to reproduce your issue and what's expected. Authors ------- [](#authors) - **Initial Inspiration** - *`Cookie PopUp` sources* - [flurrybox](https://github.com/flurrybox) - **Opengento Community** - *Lead* - [They're awesome!](https://github.com/opengento) - **Contributors** - *Contributor* - [Many thanks!](https://github.com/opengento/magento2-gdpr/graphs/contributors) Similar Magento 2 GDPR Module ----------------------------- [](#similar-magento-2-gdpr-module) - - - - License ------- [](#license) This project is licensed under the MIT License - see the [LICENSE](./LICENSE) details. ***That's all folks!*** ### Health Score 25 — LowBetter than 37% of packages Maintenance20 Infrequent updates — may be unmaintained Popularity2 Limited adoption so far Community13 Small or concentrated contributor base Maturity57 Maturing project, gaining track record Bus Factor1 Top contributor holds 79.4% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~18 days Recently: every ~58 days Total 16 Last Release 2606d ago Major Versions 1.0.0-beta → 2.0.0-beta2018-07-20 1.0.0-beta3 → 2.0.0-beta32018-07-31 1.0.0-beta4 → 2.0.0-beta42018-07-31 1.0.0-beta5 → 2.0.0-beta52018-09-25 2.0.0-beta5 → 3.0.0-Beta12019-03-21 ### Community Maintainers ![](https://www.gravatar.com/avatar/c3fb9d3ea026a8b82c77a87154891c884e63d2ac4819ffbfd431aa42fe7b4b52?d=identicon)[Adexos](/maintainers/Adexos) --- Top Contributors [![thomas-kl1](https://avatars.githubusercontent.com/u/20971693?v=4)](https://github.com/thomas-kl1 "thomas-kl1 (81 commits)")[![anthony-blackbird](https://avatars.githubusercontent.com/u/12445118?v=4)](https://github.com/anthony-blackbird "anthony-blackbird (13 commits)")[![Kiwikoti](https://avatars.githubusercontent.com/u/111362284?v=4)](https://github.com/Kiwikoti "Kiwikoti (6 commits)")[![adaudenthun](https://avatars.githubusercontent.com/u/15668948?v=4)](https://github.com/adaudenthun "adaudenthun (1 commits)")[![herman-aka-wouter](https://avatars.githubusercontent.com/u/40226924?v=4)](https://github.com/herman-aka-wouter "herman-aka-wouter (1 commits)") --- Tags phpmagentogdprmagento2rgpd ### Embed Badge ![Health badge](/badges/adexos-module-gdpr/health.svg) ``` [![Health](https://phpackages.com/badges/adexos-module-gdpr/health.svg)](https://phpackages.com/packages/adexos-module-gdpr) ``` ### Alternatives [opengento/module-gdpr Gdpr Compliance Module for Magento 2 14481.5k](/packages/opengento-module-gdpr)[dotdigital/dotdigital-magento2-extension Dotdigital for Magento 2 50374.2k18](/packages/dotdigital-dotdigital-magento2-extension)[mollie/magento2 Mollie Payment Module for Magento 2 1121.6M10](/packages/mollie-magento2)[yireo/magento2-googletagmanager2 Add Google Tag Manager to Magento 167930.4k5](/packages/yireo-magento2-googletagmanager2)[opengento/module-saleable This extension allows to set if a product is saleable and can show its price by scope and customer group. 136.9k](/packages/opengento-module-saleable)[o2ti/sigep-web-carrier O2TI - Sigep Web Carrier 141.5k](/packages/o2ti-sigep-web-carrier) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)