In 2018, the California state had passed a law that provided California residents with the right to be informed on how their data is collected and distributed by organizations and businesses. The California Consumer Privacy Act (CCPA) came into force on January 1, 2020, making all merchants whose online business covers the California region responsible for complying with the new requirements. The regulations are related to collecting, managing, and disclosing the personal information of website visitors who come from California.
The Amasty California Consumer Privacy Act Magento 2 extension provides online merchants with a complete set of tools to make their stores compliant with the new regulations. By installing the Magento 2 module, you will ensure customers in the safe processing of their personal data and avoid penalties for violating the legislation.
- Configuration of privacy settings targeted at California residents;
- Ability to create multiple consent checkboxes;
- Display of custom checkboxes on various pages;
- Customer access to the collected info;
- Cookie usage control;
- Ability to reject the usage of personal data by a customer;
- Option to download personal customer information;
- Anonymization of customer data;
- Ability to send requests for removing personal details from the customer account;
- Automatic creation of deletion requests for abandoned accounts.
To ensure your store visitors in transparent handling of their personal data, you can allow customers to view which information is being collected. The Magento 2 CCPA module also allows informing customers how their details are processed and whether they are sold to third parties.
Moreover, you can enable the option that will let customers download their data collected by your store for the 12-month period. The download of private account information will be possible only with a unique password kept by a customer so that you can ensure your clients of safe access to their data. As a store admin, you can view and manage all download requests in the Magento backend.
Furthermore, the California Consumer Privacy Act Magento 2 extension allows anonymizing customer data by converting it into a sequence of random symbols. Besides, the module grants users a right to delete their personal info. Customers can ask store managers to remove their accounts. After processing the request, user data can be deleted permanently.
- Date Created;
- Version Number;
- Last Edited;
- Last Edited By;
- Status (Disabled, Enabled, or Draft);
- Action (Edit).
You can apply filters to look for particular documents and change the sorting of the grid columns. It is also possible to delete selected policy documents in bulk.
- status (enabled or disabled),
- whether it is required or not,
- whether it is hidden after a user gives the consent,
- whether it is included in the log,
- location (Registration, Checkout, Contact Us, or Newsletter Subscription).
You can edit each checkbox individually and apply mass action to delete selected checkboxes. To create a new checkbox, press the “New Checkbox” button.
You can track all consents submitted by customers and check their details on a separate grid under Customers → CCPA → Consent Log. The available mass actions here allow sending consent requests to selected customers via email.
To manage the delete requests, go to Customers → CCPA → Delete Requests. The appropriate grid shows the name and email of a customer who sent the deletion request, the date and time when it was performed, the initiator of the request (the customer or automatically), and the number of completed and pending orders of the customer. Store managers can approve or deny selected requests in bulk.
It is also necessary to mention that the Amasty CCPA module extends the Customers grid by adding the “Don’t Sell My Personal Information” column.
As for the general settings of the Amasty CCPA Magento 2 extension, it is divided into 4 tabs: General, Customer’s Account Privacy Settings, Personal Data Deletion, and Email Notifications.
The General settings tab lets you enable/disable the extension’s functionality on the frontend and make the “Don’t Sell My Personal Information” option in the Privacy Settings tab of the customer account visible only to users from California. Here, you can also activate the log’s automatic cleaning and specify the number of days after which the logged records should be removed.
Next, you can allow customers to download their personal details, opt-out from selling their data, and send requests for deleting the account.
The Personal Data Deletion tab is divided into 2 sections: Automatic Personal Data Deletion and Prevent Data Deletion of Recent Orders. In the first section, you can enable the feature that will automatically delete accounts of customers who didn’t make any orders for a specified period.
Another section in the same tab lets you specify the number of days, which will be considered the period of recent orders, and disable customers’ data deletion in the corresponding order-related documents. Here, you can also define statuses of orders for which personal data anonymization and deletion will not be allowed.
In Email Notifications, you can enable email alerts sent to admins on the creation of a new delete request. Here, you should also select an email sender and template and specify the notification recipients’ email addresses.
In this tab, you also enable/disable notifications sent to customers on their requests’ approval and denial. For each type of notification, you should choose email senders and templates and specify email addresses for sending replies.
Now, let’s see how the CCPA Magento 2 extension functions from a frontend user perspective.
Furthermore, the Magento 2 CCPA module adds a new section to the customer account area – Privacy Settings. The section allows your clients to download a copy of the collected user info in a CSV format, opt-out from selling their data to third parties, and submit requests for deleting their accounts.
The CCPA extension for Magento 2 can be purchased for $149. Follow the link below to get more details about the module: