Deletion Methods

Teleskope offers a range of deletion options depending on the capabilities of the target platform or tool. Efficiently manage Data Subject Request (DSR) deletions by enrolling each Database table and 3rd party SaaS tool with an appropriate deletion method.

Relational Databases

To service DSR deletions in an instance, Teleskope must first have read access to crawl its databases, tables, and columns. After identifying its schema, you can determine the Deletion Method during the enrollment process. To automate DSR deletions, Teleskope performs queries that can:

• Anonymize the cell

• Delete the entire row

Upon request, Teleskope can enable alternative redaction methodologies like those used in our Scrub API.

Third Party Integrations and Unstructured Databases

To service DSR deletions for third party integrations, Teleskope depends on recommendations and APIs made available by the developer. Often, integrations contain multiple resources (like User, Invoices, Address) that must be deleted to fully scrub a customer's information; in these circumstances, Teleskope allows you to choose the resources and endpoints it relies on.

After enrolling the 3rd party integration, navigate to DSR -> Third Party Integrations -> Edit -> Enrollments to specify which endpoints are used for a DSR Deletion requests.

For third party integrations that store documents or long form text, Teleskope relies primarily on native redactions or deletion API, but may also redact from files directly as a user or admin.

For third party integrations that store relational user data, Teleskope relies primarily on available API.

For third party integrations that do not provide publicly available API, Teleskope can submit a DSR Deletion Request email on your behalf.

For unstructured databases, Teleskope replaces the object with a redacted version, scrubbed of any user data.