Multivendor GDPR

Vendors or customers can request account data updates or deletions by contacting the admin with specific details of the changes needed.

• Vendors/customers can submit requests to update their personal data.
• They can also request the deletion of their complete account data.
• The admin can view all requests for data updates and deletions from vendors/customers in a grid format.
• The admin has the option to change the status of each request.
• Each time a request status is updated, the vendor/customer will receive an email notification.
• Additionally, the admin will receive an email for vendor data requests.

The cookie consent notice will appear on every page of the site.

• If vendors or customers accept the cookie notice, it will be hidden for one day, and the acceptance will be stored as a cookie in the system.
• Upon installation of the module, a default cookie static block will be automatically generated.
• The admin has the option to create additional static blocks or modify the existing default block.
• To display a static block on the front end, the admin must enter the corresponding static block identifier code.
• The admin can also choose the position of the cookie block, either at the bottom left or bottom right of the page.

The admin can enable the customer data agreement for vendors and customers, as well as configure its content.

• Consent for customer data can be activated on both the vendor/customer registration and account pages.
• The admin has the ability to set a custom label for the agreement checkbox.
• The content of the customer data agreement can be managed from the back end.
• If the vendor/customer consents to the use of their data, the admin may utilize their information in accordance with the customer data agreement.
• Should the vendor/customer wish to modify their account information, they will need to re-accept the customer data agreement.

• Enable Extension: A dropdown option for enabling GDPR compliance with “Yes” as a selectable option.

• Require Customer Agreement: A dropdown option where the admin can choose "Yes" to require customer agreement.
• Consent Checkbox Text: A text area for customizing the consent checkbox label, e.g., "I accept the terms and conditions.
• Agreement Details Content: A text area for the content of the agreement, which typically includes terms of use and legal disclaimers.

• Show Cookie Consent Message: A dropdown allowing the admin to choose whether to display the cookie consent message.
• Cookie Message Placement: Dropdown to specify where the cookie message will be displayed (e.g., "Bottom Left").
• Cookie Message Block Identifier: A field for entering the block identifier for the cookie message.

• Template for Data Update Request: Dropdown for selecting the email template used for data update requests, with a default option provided.
• Template for Data Deletion Request: Dropdown for selecting the email template for deletion requests.
• Template for Request Status Updates: Dropdown to select the email template used for status updates regarding requests.
• Template for Request Deletion Updates: Dropdown for choosing the template for updates on deletion requests.

The admin has the ability to modify the status of vendor/customer requests, with the following options available: pending, processing, complete, and declined.

• Pending: This status indicates that the vendor/customer has submitted a request, and it is currently awaiting review.
• Processing: This status informs the vendor/customer that their request has been received and is being actively worked on.
• Complete: This status signifies that the user’s request has been successfully fulfilled according to their specifications.
• Declined: This status allows the admin to formally reject the request.

The admin will receive an email notification for each status update. Additionally, the email templates for these notifications can be customized in the configuration settings.