Severity: Choose Minimal Impact

  1. Access Category: Choose Other
  2. Subject: Mention Data Erasure Request
  3. Description: Mention the following details in the free text area:
    1. User Email ID: Unique Identifier (email address) for the user requesting data erasure request
    2. First Name: First name of the user requesting data erasure
    3. Last Name: Last name of the user requesting data erasure
    4. Contact Email Address: Email address of the user requesting data erasure
    5. Reason for removal: Rational for requesting data erasure
    6. Erasure Requester Name: Name of the Administrator
    7. Erasure Requester Email: Email of the Administrator
  4. Send Notifications to (Comma Separated Ids): Notification will be sent to the administrator raising data erasure request; however, user’s (user requesting data erasure) email ID can be added for notification.
  5. Status: Choose New
  6. Assigned To: Mention BigFix AEXPS@hcl.com
  7. File: Attach user’s request for data erasure
  8. Click on Submit. A confirmation would be visible for new support ticket raised for data erasure.
    Figure 1. Data Erasure Request Submitted Successfully
    Graphical user interface, application Description automatically generated
  9. On successful request submission, the request submitter will receive an email confirmation from BigFix AEX:
    Figure 2. Data Erasure Request Ticket Confirmation Email
    Graphical user interface, text, application Description automatically generated
  10. The latest request will also be visible on the support page of the tenant.
  11. The data erasure request will be completed in 7 working days from the date of request and all the personal conversational data of the user (on behalf of whom the request has been raised) will be deleted including backup using a background job. Once data is deleted, the requester and user will be notified.
  12. Due to business requirements, aggregate data, which is required for business reporting, conversational metrics data such as conversational unique sessions, intents activated, integration triggered will be retained. Such details should be communicated to the user by the administrator or relevant DPO (data protection officer) of the organization.