Magento 2 Data Privacy v3.x Configuration

Step-by-Step actions:

1. “Enable Extension”: this option allows you to enable or disable the module.
2. “Serial Key”: enter the unique serial key provided to you after purchasing the extension. Please, note: in most cases, this field will be pre-filled with a serial key automatically, and the green checkmark will be displayed. To find and paste your serial key manually, read the Serial Key Activation article.

Step-by-Step actions:

1. “Privacy Policy Page“: select the Privacy Policy CMS page from the list of all CMS pages.
2. “Cookie Policy Page“: select the Cookie Policy CMS page from the list of all CMS pages.
3. “Enable Privacy Center for Guests“: when enabled, the “Privacy Center” link will be available to guests in the footer of your store. Guests will be asked to provide their email addresses there in order to request access to their personal data. If provided, they will receive an email with a link to access the Privacy Center Dashboard.
4. “Guest Link Expiration (Days)“: specify the number of days the Privacy Center Dashboard access link will be active. This temporary shared URL is only displayed in the email to guests after they request access to their personal data on the Privacy Center page.

Step-by-Step actions:

1. “Anonymization Key“: enter the key for anonymized data. When a customer requests to delete an account and therefore all personal information, certain data (such as order billing info, emails, etc.) is anonymized, as it cannot be deleted to comply with local laws.
2. “Delete Inactive Customer Data“: set the option to Yes to automatically delete customer accounts that are inactive.
3. “Account Inactivity Timeout“: set the number of days since the last login for an account to be considered inactive.
4. “Send Email Notification“: send customers an email notification about scheduled account deletion with the option to cancel it.
5. “Account Deletion Cancellation Period“: set the number of days after email notification that users can cancel account deletion.

Step-by-Step actions:

1. “Sender Name“: enter the sender name of the emails.
2. “Sender Email“: enter the email address from which all emails should be sent.
3. “Download Confirmation Email Template“: choose the email template to use when a customer’s account data was successfully downloaded.
4. “Removal Requested Email Template“: the selected email template will be used when a customer’s account is scheduled for removal.
5. “Guest Privacy Center Email Template“: choose the email template to use when guest users request access to their personal data on the Privacy Center page.
6. “Save Config“: press the Save Config button to save and apply changes.

Step-by-Step actions:

1. Consent Checkboxes grid contains all necessary information about customer’s consents that is required by the GDPR law:
   • “ID“: a customer’s ID.
   • “Consent Location“: locations on your store where the checkbox is displayed.
   • “Checkbox Label“: the text displayed next to the checkbox informing users what they need to give their consent to.
   • “Link to CMS Page“: click on the CMS page link provided on the checkbox label to view or edit its settings.
   • “Required“: the “Yes” mark in this field indicates that the consent checkbox is required and must be checked in order to submit a form; the “No” mark indicates that it is optional.
   • “Display Checkboxes“: when “Yes” is displayed, the checkbox is active and shown next to the form.
   • “Action“: click on the “Edit” link to edit the checkbox. Click here to learn how to do it correctly.

Step-by-Step actions:

1. “Display Checkbox“: switch to “Yes” in order to display the checkbox when submitting a form. Otherwise, switch to “No” to disable the box.
2. “Consent Location“: choose one or more locations where the consent checkbox must be displayed. Showing checkbox in a custom location will require code modifications.
3. “Checkbox Label“: enter the label of the checkbox. You can also add the “pr-inpopup” CMS class to display the CMS page content in a popup so that users can learn more about consent before giving it.
4. “Link to CMS Page“: choose the CMS page associated with this checkbox. Linked CMS page content will be displayed in a popup so that customers can read detailed information about the consent before giving it. Leave empty if you do not want to display any CMS content. 
5. “Required“: indicate whether this checkbox must be checked in order to submit a form, or it can be optional.
6. “Geo Targeting“: if your data privacy law allows so, select countries to show the consent checkbox only to visitors from that countries.
7. “Internal Note“: use this optional field for Admins only to describe custom checkbox location (such as “New Year’s promo landing page”) or add some internal notes.
8. “Save Checkbox“: press the button to apply changes.

Step-by-Step actions:

1. In a Consent Locations grid, you can view all the information about consent locations:
   • “Location Name“: the name of the location where the consent checkbox is displayed.
   • “Location Key“: a unique identifier of your custom consent location, useful when displaying consent checkboxes manually.
   • “Type“: the type of consent location. The “Default” consent location is built-in and comes with the Data Privacy extension; the “Plumrocket” location is integrated from other Plumrocket extensions; the “Custom” location is the one created manually.
   • “Internal Note“: internal notes for custom checkbox location information. This field is optional and visible to admins only.
   • “Action“: if it is a custom consent location, click the “Edit” button and edit the location. Please, follow the New Consent Location instructions to learn how to edit a location correctly.
2. “Add New Location“: press the button to add a new location. Please, follow the New Consent Location section to learn how to get it right.

Step-by-Step actions:

1. “Location Name“: the name of your custom consent location.
2. “Location Key“: a unique identifier of your custom consent location. You will need this key when displaying consent checkboxes manually. Examples: “promo_page”, “myPopupForm”, “login_form”.
3. “Internal Note“: this field is optional and visible to admins only. It is useful when you need to add some internal notes or describe a custom checkbox location (such as “New Year’s promo landing page”).

Step-by-Step actions:

1. The Account Removal Requests log contains the records of each user’s request to delete one’s account along with all details. An anonymization key is used when an account is already deleted.
   • “Request Date“: the date when a customer requested the account deletion.
   • “IP“: an IP address from which the account removal was requested.
   • “Cancellation Date“: the date when the customer’s account was permanently deleted.
   • “Cancelled By“: the name of the user who has canceled the account removal request.
   • “Removal Date“: the date when the customer’s account was permanently deleted.
   • “Status: the status of the request. The available statuses are: pending, completed, canceled.
   • “Action“: if the account removal request’s status is”Pending”, press the “Cancel” button to disapprove the request.

Step-by-Step actions:

1. The Log of Account Data Downloads grid contains detailed information about customer account data downloads, namely the customer ID, email, and name, as well as the date and the IP address from which data was downloaded.

Step-by-Step actions:

1. The Log of Customer Consents grid represents all customer consents, as well as the following data in columns:
   • “Consent Location“: the location on your store where a customer gave consent.
   • “Action“: the action that a customer took to consent.
   • “Version“: the version of the policy or terms agreed by a customer.

Step-by-Step actions:

1. The Pages grid displays all CMS pages on your store along with their title, URL key, Layout, Store View, Status, creation, and modification date.
2. The “Action” grid column allows you to edit, delete and view CMS pages. Click on “Edit” opposite the corresponding page and follow the Edit CMS Page instructions to find out how to create the new version of a CMS page and request customer consent to it.

Step-by-Step actions:

1. “Enable Revisions“: set to “Yes” to enable CMS page revision.
2. “Document Version“: enter the version of the document.
3. “Notify All Customers vis Popup“: set to “Yes” to enable popup notifications to all customers upon successful login. Customers will be notified that the agreement is updated and asked to agree with the document’s new version.
4. The Editor allows you to enter the request to agree with the new document displayed to customers on the popup.

Step-by-Step actions:

1. The Revision History grid displays all document’s previous versions, along with their modification date and the name of a user who updated the document.
2. Click on the “View Revision” button to see the document content.