DSR Request Statuses & Origins
The status of the request along the pipeline can be found under the "Status" tab of the request. The full set of DSR statuses that exist in the platform today include:
| Label | Enum | Description |
|---|---|---|
| Request Made | REQUEST_MADE | The DSR was just submitted. |
| Verification Failed | FAILED_VERIFICATION | Email or phone 2FA failed. The request was canceled because it was not confirmed. |
| Canceled | CANCELED | The request was canceled by an administrator or webhook rule. |
| Revoked | REVOKED | The request was canceled by the data subject. |
| Preflight | ENRICHING | Preflight jobs are actively being run. This includes business-logic checks and identity enrichment |
| On Hold | ON_HOLD | The request has been placed on hold and is pending manual review by a member of your team. |
| Waiting | WAITING | The request is in a waiting state to give an opportunity for the request to be canceled if a mistake. |
| Compiling | COMPILING | The request is looking up any data on the user and/or apply any user preferences across the stack. |
| Waiting for approval | APPROVING | The request has compiled and is pending a manual review before completion. |
| Completed | COMPLETED | The request has been fully processed and completed across the stack. |
| Downloadable | DOWNLOADABLE | Access only: the compiled data is available for download by the data subject over a 2-week period. |
| View categories | VIEW_CATEGORIES | Access only: the request is not available for download, but its associated data collection categories are made available to the data subject for review over a 2-week period. |
| Delaying execution | DELAYED | Erasure only: request is pending deletion. The data pending deletion can be downloaded by the data subject, and the deletion request can be canceled. |
| Approval after data removed | SECONDARY_APPROVING | Erasure only: the data deletion is completed but notification to data subject is pending approval. |
| Removing data | SECONDARY | Erasure only: the deletion jobs are being executed across the stack. At this point, the deletion cannot be canceled. |
| Data removed | SECONDARY_COMPLETED | Erasure only: deletion request has been successfully completed in full. |
You can filter requests in the "Incoming Requests" tab of the Admin Dashboard based on how the request was received, also known as its origin. The origin can be one of the following:
| Label | Enum | Description |
|---|---|---|
| API | API | The DSR was received through the Transcend API submitted. |
| Privacy Center | PRIVACY_CENTER | The user authenticated themselves and submitted the request through your Privacy Center |
| Admin Dashboard | ADMIN_DASHBOARD | The request was submitted manually by an admin or other employee. |