Deletion requests table updates #8111
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
forstisabella
added
the
content-update
✅ Deploy Preview for segment-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
ajay-seg
reviewed
Oct 30, 2025
| A deletion request can have one of the following statuses: | ||
| Segment's API returns the following statuses: | ||
|
|
||
| 1. `INITIALIZED` |
ajay-seg
reviewed
Oct 30, 2025
|
|
||
| Destination regulations can have the following statuses: | ||
|
|
||
| - **No action**: Segment didn't forward your regulation to a downstream destination |
There was a problem hiding this comment.
No Action status here indicates Not Applicable here. This status is for segment only regulations i.e internal and there is no downstream destination there to forward the request to.
This is the description... wording can be yours
forstisabella
commented
Oct 30, 2025
forstisabella
commented
Oct 30, 2025
pwseg
previously approved these changes
Oct 30, 2025
|
|
||
| To navigate to the deletion requests tab, open the Segment app and navigate to **Privacy > Deletion and Suppression > Deletion**. | ||
|
|
||
| If you need to verify if information about a specific user was deleted or suppressed, you can search for a `userId` to view its status in Segment internal systems and in any connected destinations. |
There was a problem hiding this comment.
nit:
Suggested change
| If you need to verify if information about a specific user was deleted or suppressed, you can search for a `userId` to view its status in Segment internal systems and in any connected destinations. | |
| If you need to verify if a specific user was deleted or suppressed, you can search for a `userId` to view its status in Segment internal systems and in any connected destinations. |
| - `FINISHED` | ||
|
|
||
| When checking the status of deletion requests using Segment's API, the deletion will report an overall status of all of the deletion processes. As a result, Segment returns a `FAILED` status because of a failure on an unsupported destination, even if the deletion from the Segment Internal Systems and supported destinations were completed successfully. | ||
| For more granular deletion request statuses, see the [Deletion requests tab](#deletion-requests-tab) in the Segment app. |
There was a problem hiding this comment.
Shouldn't this be the deletion-requests-status tab instead?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
UI parity, Regulations -> regulations
Merge timing
asap!
Related issues (optional)