GDPR Pro

VIDEO WALKTHROUGH

GDPR Pro: setup guide

2:39

Recorded on version 1.0.2 · Narrated walkthrough · English captions

Jump to a chapter 8 chapters

Read the full video transcript

GDPR Pro 1.0.2 — Magento Admin setup

00:00:00 — Set up GDPR Pro
Welcome to the Agentic Ecom G D P R Pro Admin guide. We'll walk through the main setup screens and the checks to make before using the module. This guide assumes the extension is already installed.

00:00:12 — Open settings and choose scope
Start in Magento Admin and open Stores, Configuration. Choose GDPR & Privacy. Check the Scope selector before editing. Use the appropriate website or store view where the setting supports it. The screen values here are a demonstration; enter the settings and service details that belong to your own store.

00:00:32 — Set privacy contact details
Enable the privacy tools and choose your privacy policy page and contact email. These settings must reflect your own store's data-handling process. Review the public notice and the people responsible for responding to customer requests before enabling the customer-facing tools.

00:00:51 — Configure the cookie banner
Enable the banner and review its position, theme, title, message and buttons. The module records choices for necessary, analytics, marketing and preference categories. It does not automatically stop third-party tags from loading; connect your storefront or tag manager to the saved choices before relying on consent-based loading.

00:01:13 — Review consent records and retention
Review consent logging and the retention period. A value of zero disables automatic cleanup. Changing Consent Version labels new records, but does not automatically show the banner again to previous visitors. Check actual stored records and your retention policy rather than assuming a setting alone completes the process.

00:01:34 — Plan customer data requests
Review Data Export and Data Deletion settings with the staff handling requests. Verify the customer's identity and understand what data each workflow includes before processing a live request. Test the workflow with a disposable account, and keep your own privacy notice and operating process aligned with the configured tools.

00:01:55 — Save and verify your setup
When your required settings are complete, use the screen's Save control and wait for Magento's confirmation. Then reopen the record or configuration and check the saved values at the intended scope. If the storefront still shows earlier settings, refresh the relevant caches. Test your own configuration before using it with customers.

00:02:17 — Your setup checklist
That's the Admin setup walkthrough for G D P R Pro. Check permissions and scope, review the module-specific settings, then save and verify a small staging example. Use the written guide at user guides dot Agentic Ecom dot net for installation details, complete field references and any separate storefront integration steps.

Download video English captions Download transcript

GDPR Pro 1.0.2 adds a configurable cookie banner, records consent choices, provides customer data request workflows, and includes an optional command-line PII scanner. It supports Luma and exposes GraphQL operations for a headless storefront. Magento Open Source 2.4.9 with PHP 8.5.10 is the tested baseline. Merchants must configure their own privacy notice, tag loading and data-handling process.

Install

For a direct AgenticEcom purchase, use your licence key from My Licences:

composer config repositories.agenticecom composer https://repo.agenticecom.net
composer config --global --auth http-basic.repo.agenticecom.net <YOUR-LICENCE-KEY> x
composer require agenticecom/module-gdprpro:^1.0.3
php bin/magento setup:upgrade
php bin/magento setup:di:compile
php bin/magento cache:flush

For an Adobe Commerce Marketplace purchase, install the purchased package through repo.magento.com using your Marketplace access keys. A Marketplace purchase does not require a second direct-store licence.

Go to Stores → Configuration → General → GDPR & Privacy. In General, enable the privacy tools and set the privacy policy page and contact email. In Cookie Consent Banner, enable the banner and set its position, theme, title, message and buttons. The banner records choices for necessary, analytics, marketing and preferences categories. Test it on your storefront after clearing the Magento full-page cache.

Enable Log All Consent Decisions to attempt an audit record for each choice. Check records under Customers → GDPR Compliance → Consent Logs. Records include a timestamp and may include IP address and user-agent when logging and storage succeed. Data Retention Period (Days) controls cleanup of old consent logs and completed or rejected requests; 0 disables automatic cleanup. Changing Consent Version labels new records but does not automatically show the banner again to previous visitors.

Customer data requests

Customers can submit export, deletion and rectification requests. Review them under Customers → GDPR Compliance → Data Requests. Requests move through pending, approved, processing and complete as an administrator reviews and processes them. The grid offers approval, processing, completion and protected export download actions.

Export: The module gathers supported customer information into a download for an authorised administrator. Review it before sharing it through your own verified customer support process.
Deletion: Keep Require Admin Approval enabled. Review open orders and retention duties before processing. The module can anonymise order information instead of deleting orders.
Rectification: The customer describes the correction needed; an administrator must review and make the correction. A request does not edit account data automatically.

These tools support a merchant’s process; they do not establish legal compliance by themselves.

Headless GraphQL

A headless storefront can read the banner configuration and save choices:

query {
  gdprConsentConfig {
    enabled
    privacy_policy_url
    consent_categories { code label is_required default_enabled }
  }
}

mutation {
  saveCookieConsent(
    necessary: true
    analytics: false
    marketing: false
    preferences: false
  ) { success message }
}

The customer data request mutations requestGdprDataExport, requestGdprDataDeletion and requestGdprDataRectification(details: "..."), and the customerGdprData query, require customer authentication. Process resulting requests in Magento Admin. The consent mutation also accepts guest visitors.

Optional PII scanner

Run the local scanner with:

php bin/magento agenticecom:gdpr:pii-scan

Under PII Scanner, optional AI Verification of Findings is off by default. Local findings remain visible even if an AI provider labels one a likely false positive. The optional review supports OpenAI and Google Gemini. Auto chooses GPT-6 Luna when an OpenAI key is configured, or Gemini 3.8 Flash for a Gemini-only setup; specific models are selectable in Admin. Keys use Magento’s encrypted config backend.

Enabling AI sends masked excerpts to the selected external provider. Surrounding words may still contain personal data. OpenAI or Google API use can incur separate charges. Review your privacy notice and processor arrangements before enabling it. Leave the setting off for local-only scanning.

Version and scope

This guide describes the released 1.0.2 package. It was installed and upgraded on Magento Open Source 2.4.9 with PHP 8.5.10; other versions and editions need separate qualification. The module’s Composer constraint allows PHP 8.3, 8.4 and 8.5.