Skip to content

Commit d6745d7

Browse files
committed
update language per eng [netlify-build]
1 parent e69c2be commit d6745d7

File tree

1 file changed

+13
-13
lines changed

1 file changed

+13
-13
lines changed

src/privacy/user-deletion-and-suppression.md

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -79,22 +79,22 @@ The deletion requests status table allows you to see the status of each of the r
7979
- The date that Segment received your regulation
8080
- The date that Segment completed a regulation
8181

82-
To view more information about a regulation, select it from the deletion requests tab. On the side sheet for that regulation, you can view the status of your regulation within Segment and in downstream destinations, the ID of the source the regulation was coming from, and, if applicable, the reason a regulation failed.
82+
To view more information about a deletion request, select the userID on the deletion requests tab. On the side sheet for that deletion request, you can view the status of the request within Segment and in downstream destinations, and, if applicable, the reason a request failed.
8383

84-
Segment actions can have the following statuses:
84+
Segment deletion requests can have the following statuses:
8585

86-
- **Initialized**: Segment started processing your regulation
87-
- **In progress**: Segment has started processing your regulation
88-
- **Success**: Segment processed your regulation
89-
- **Failed**: Segment was unable to process your regulation
86+
- **Initialized**: Segment accepted your deletion request and placed it in the deletions queue
87+
- **In progress**: Segment started processing your deletion request
88+
- **Success**: Segment processed your deletion request
89+
- **Failed**: Segment was unable to process your deletion request
9090

91-
Destination regulations can have the following statuses:
91+
Destination deletion requests can have the following statuses:
9292

93-
- **No action**: Used for Segment-only regulations to indicate that they weren't forwarded to a downstream destination
94-
- **Initialized**: Segment forwarded your regulation to a downstream destination
95-
- **In progress**: The destination started processing your regulation
96-
- **Success**: The destination processed your regulation
97-
- **Failed**: The destination was unable to process your regulation
93+
- **No action**: Used for Segment-only deletion requests to indicate that they weren't forwarded to a downstream destination
94+
- **Initialized**: Segment added your deletion request to a queue to send to a destination
95+
- **In progress**: Segment started forwarding your deletion request to a destination
96+
- **Forwarded**: Segment forwarded your request to a destination
97+
- **Failed**: Segment was unable to forward your request to a destination
9898

9999

100100
#### Deletion requests made using Segment's API
@@ -111,7 +111,7 @@ Segment's API returns the following statuses:
111111
- `FAILED`
112112
- `FINISHED`
113113

114-
For more granular deletion request statuses, see the [Deletion requests tab](#deletion-requests-tab) in the Segment app.
114+
For more granular deletion request statuses, see the [Deletion requests tab](#deletion-requests-status) in the Segment app.
115115

116116
### Deletion request SLA
117117

0 commit comments

Comments
 (0)