Customer data protection — found from sitemap — LivePerson

Cited by

Facts read from this source

• GDPR right to be forgotten Report an error

  “The Personal Data Deletion API allows brands to comply with the European Union's Right to be Forgotten requirement (a part of the GDPR).”

• Deletion permanent Report an error

  “This API will permanently delete any personal data that the consumer requests to be deleted. Once the data has been deleted there is no way to restore it.”

• Deletion scope Report an error

  “Personal data may include full conversation transcripts, hosted files or links sent by the consumer, survey free text answers and consumer's PII (personally identifiable information).”

• Deletion mechanism Report an error

  “What this document refers to as "deletion" is actually the replacement of specific, personal data with the text: “** LP deleted data **””

• Deletion timeline Report an error

  “Data will be deleted within 30 days from the time the deletion request was made final (explanation regarding when requests are made final can be found below).”

• Grace period Report an error

  “Once a deletion request is sent via the API, it will become final and irrevocable after a pre-defined time period (5 days by default). During that time period, it is possible for the brand to cancel the deletion request.”

• Monthly request limit Report an error

  “There is a limitation of the number of deletion requests that a brand can issue within a calendar month. By default, the requests threshold is set to 100 requests.”

• Closed only Report an error

  “Only closed chats / conversations can be deleted.”

• Chat flow Report an error

  “Use the Engagement History API to search for engagements with the identifying value. Find all relevant engagements and make note of the engagement id(s) to delete”

• Messaging flow Report an error

  “Use the Messaging Interactions API to search for conversations with the identifying value. Find all relevant conversation id(s) for deletion.”

• Messaging consumer deletion Report an error

  “Use the Create Delete Request method and make two requests: one with the list of conversations to delete and another with the consumerId. This makes sure that both the conversation and the rest of the consumer's data is completely deleted.”

• Ticketing masking Report an error

  “The tickets themselves will not be deleted but rather the metadata which links the tickets to the requesting consumer, such as ticket message (email) headers, UDEs (legacy SDEs) and ticket contact info, will be masked. Attachments in the relevant tickets will be deleted.”

• Ticketing auth Report an error

  “As the Ticketing system is a legacy feature used by legacy (non LE 2.0) accounts, this API requires authorization using an external OAuth 1.0 API key. This token should be generated by the LivePerson Support team.”

• Not for mass deletion Report an error

  “This API is not meant for massive deletion of data. There is an internal mechanism which will protect the system from misuse of the API.”

• Domain API Report an error

  “Retrieve your domain. Use the LivePerson Domain API to retrieve this information by providing the following service name: rtbf”

• API auth Report an error

  “This API requires authorization using API key or via login.”

• Related APIs Report an error

  “Use the Messaging Interactions API to search for conversations with the identifying value.”

Scores citing this record

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