Merge pull request #5202 from segmentio/update-privacy-portal-page

Update privacy portal page
segmentio · Aug 17, 2023 · 4038b54 · 4038b54
2 parents fb1245a + 0c415c0
commit 4038b54
Show file tree

Hide file tree

Showing 4 changed files with 2 additions and 3 deletions.
diff --git a/src/connections/sources/index.md b/src/connections/sources/index.md
@@ -53,7 +53,7 @@ analytics.identify('user_123', {
 
 Segment has three types of sources: 
 * [Event streams](#event-streams-sources)
-* [Cloud app objects](#cloud-app-sources)
+* [Cloud app sources](#cloud-app-sources)
 * [Reverse ETL](#reverse-etl-sources) 
 
 

diff --git a/src/privacy/images/privacy-add-new-matcher.gif b/src/privacy/images/privacy-add-new-matcher.gif
diff --git a/src/privacy/images/privacy-edit-matcher.png b/src/privacy/images/privacy-edit-matcher.png
diff --git a/src/privacy/portal.md b/src/privacy/portal.md
@@ -25,7 +25,7 @@ The Inbox helps you keep track of new restricted data types as they are captured
 
 Segment detects these fields by scanning data from your Web, Mobile, Server, and Cloud Event Sources to detect PII based on the [default PII matchers](#default-pii-matchers). New properties sent into Segment appear in the Inbox in realtime.
 
-When you view the Inbox for the first time, it displays every property that was sent into Segment from Web, Mobile, Server, and Cloud Event Sources dating back to August 9, 2019. ([Cloud Object Sources](/docs/connections/sources/#cloud-apps) do not appear in the Inbox at this time.)
+When you view the Inbox for the first time, it displays every property that was sent into Segment from Web, Mobile, Server, and Cloud Event Sources dating back to August 9, 2019. ([Object Cloud Sources](/docs/connections/sources/#object-cloud-sources) and [Reverse ETL Sources](/docs/connections/sources/#reverse-etl-sources) do not appear in the Inbox at this time.)
 
 You can click a row in the Inbox to learn more about a field and where it was collected. The expanded view shows:
 
@@ -201,7 +201,6 @@ treat that property whenever it is appears in data Segment processes.
 3. Set the default classification:
    - **Red** for highly restricted
    - **Yellow** for moderately restricted
-   - **Green** for least restricted
 4. Choose whether to match on a **Key** (for example, "SIN", "Social Insurance Number", "Social Insurance No.", "SocInsNo") or on a **Value** (for example. "123-456-789", "1234567")
 5. Select how precise the match should be, by choosing **Exact** or **Similar** match.
    - **Exact** matches mean that a key matches the term exactly (for example "phone number" but never "phne number")