GDPR Data Rights for Magento 2

No module can do that on its own. GDPR Data Rights gives you the tools to collect and log consent, publish and version your privacy policy, answer requests on time and remove personal data you no longer need. Your policy texts, consent wording and retention periods are your decision; check them with your legal adviser.

No. Cookies are covered by our Cookie Consent module. When it is installed, the privacy tab in My Account shows the cookie categories the visitor accepted in that browser and a button that opens the cookie preferences window. Nothing else is needed to connect the two.

Registration, account information, contact us, every newsletter sign-up form (including the footer form) and the checkout. You can add any number of boxes, make each one required or optional, link it to the current privacy policy, a CMS page or another URL, and choose the store views. Boxes are never ticked in advance.

The form is refused on the server as well as in the browser, so a script or an old cached page cannot bypass it. At checkout the order is not placed and the customer sees which box to tick.

The checkbox code and the exact text shown, where it was given (form, privacy tab, policy window or admin), given or withdrawn, the policy version, the customer or e-mail address, website, store view, date, the order number for checkout consents and a SHA-256 hash of the IP address. The IP address itself is not stored.

Yes. Orders, invoices, credit memos and shipments are kept with all amounts, items and tax. Only personal details (names, e-mail, street, phone, company, VAT number, date of birth, IP address) are replaced. You can keep chosen address fields such as country and region, for example for tax reports by country.

No. Anonymisation and deletion wait while the customer has an order in one of the statuses you choose (by default the open ones), so the order can still be shipped or refunded.

On the guest page (link: /privacy/guest) a guest enters the e-mail address and an order number. If they match a guest order, the guest receives a one-time link that is valid for a time you set (1 to 168 hours). The page gives the same answer whether the details match or not, and requests are limited per IP address.

The reply-by date is one calendar month after the request was received (you can enter the date for requests that arrived by e-mail or post). While you wait for identity details you can pause the clock; the paused time is added to the deadline. You can extend the deadline once by one or two months, with an e-mail to the customer.

Retention rules start in Dry run mode, which only reports what would happen. Live mode can only be chosen after a dry run in the last seven days, and each night only a set number of records per rule is handled. For inactive accounts you can also choose to create deletion requests, so you check every account in the request desk first.

Yes. Pages stay cacheable; the window is loaded through a private customer-data section and only appears for signed-in customers: by default those who accepted an earlier version, or, if you choose, everyone until they accept the current version.

Yes. Hyvä templates for the privacy tab, guest pages, policy page and consent checkboxes are included. The checkout consent works on the Luma checkout, which Hyvä stores use through the Luma checkout fallback. The separate Hyvä Checkout product is not supported yet.