Customer data protection — found from sitemap — LivePerson

Cited by

Facts read from this source

• Deletion API methods Report an error

  “This API allows a brand to submit a deletion request via one of the following methods:”

• Engagement deletion scope Report an error

  “Chat Engagement: Deletion of the personal data that is related to specific chat engagement(s) (including transcripts, personally identifiable information (PII), etc.).”

• Consumer deletion scope Report an error

  “consumerId: Deletion of personal data that is related to a specific consumer (does not include the consumer's conversations; those must be deleted in a separate request).”

• Ticket deletion scope Report an error

  “ticketId: Deletion of personal data that is related to a specific consumer's ticket and all related interactions to that ticket (this does not include the consumer's chats; those must be deleted in a separate request).”

• Request endpoint Report an error

  “POST https://{domain}/api/account/{site_id}/personal-data-deletion”

• Id limit Report an error

  “Only one of the deletion types which appear below can be sent in a single request with a list of up to 100 unique ids.”

• Ticketing restriction Report an error

  “Ticket ids for deletion array of strings Optional Valid to use only in Legacy accounts with a ticketing system”

• Monthly threshold Report an error

  “By default, the requests threshold is set to 100 requests per calendar month. If you wish to change this, please contact your LivePerson Account Team.”

• Response codes Report an error

  “201 Created 400 Bad request 401 Unauthorized request 403 Not sufficient priviliges 429 Requests threshold for current month was reached 500 Internal server error”

• Auth header Report an error

  “Authorization Contains oAuth string to allow request authentication and authorization.”

• Participantid link Report an error

  “In the Messaging Interactions API, the consumerId is referred to as "participantId" under the "consumerParticipants" array. You can use that participantId as part of this request to identify the specific consumer for which you'd like to request data deletion.”

• Response fields Report an error

  “request_id ID of the deletion request long siteId LP account id string request_time Time in which the deletion request was requested string requested_by The user who requested to delete string cancelled_by The user who canceled the deletion request string delete_json The body parameter of the request string cancel_timestamp Time in which the deletion request was requested string is_canceled Boolean indicates if the deletion request was cancelled or not boolean”

Scores citing this record

• The Agent Advocate Ticketing, queues & SLA
• The Agent Advocate Customer data protection
• The Agent Advocate Pricing transparency
• The Data Protection Officer Customer data protection
• The Shop Operator Customer data protection
• The Integrator Ticketing, queues & SLA
• The Integrator Customer data protection
• The Skeptic Ticketing, queues & SLA
• The Skeptic Customer data protection
• The Support Lead Customer data protection