Whole Record Deletion

DataGrail's API integrations execute deletion using one of two methods, "standard" or "whole record". This article will outline the differences between the two methods and how it will impact your DataGrail workflow.

Standard Deletion

DataGrail's standard deletion method is used for the majority of API integrations and offers the most functionality within the DataGrail portal. The workflow for an integration using standard deletion is as follows:

1. Once a deletion request moves to the "Extracting Personal Data" state, the integration will automatically query the source system for data subject PII.
2. In the "Pending Action" state, privacy managers will have the ability to review and deselect any PII to be deleted.
3. Finally, in the "Pending Delete" state, the integration will only delete fields/records selected in the previous "Pending Action" state.

Whole Record Deletion

In the case an API does not support DataGrail's standard deletion method, DataGrail utilizes whole record deletion to provide the most automation possible with your integrations. The primary difference between these two deletion types is the ability to first query for PII in the "Extracting Personal Data" state. Whole record deletion integrations cannot first query systems for PII and do not support the selection of individual records for deletion. The workflow for a whole record deletion integration is as follows.

1. In "Extracting Personal Data" state, the integration will be marked as "Access Skipped".
2. In the "Pending Action" state, privacy managers will only have the ability to select/deselect the entire integration.
3. In the Pending Delete state, if selected, the integration will attempt to delete all data subject PII (if any) in the system.