Skip to content

Commit 4038b54

Browse files
authored
Merge pull request #5202 from segmentio/update-privacy-portal-page
Update privacy portal page
2 parents fb1245a + 0c415c0 commit 4038b54

File tree

4 files changed

+2
-3
lines changed

4 files changed

+2
-3
lines changed

src/connections/sources/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ analytics.identify('user_123', {
5353

5454
Segment has three types of sources:
5555
* [Event streams](#event-streams-sources)
56-
* [Cloud app objects](#cloud-app-sources)
56+
* [Cloud app sources](#cloud-app-sources)
5757
* [Reverse ETL](#reverse-etl-sources)
5858

5959

-15 KB
Loading
31.6 KB
Loading

src/privacy/portal.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ The Inbox helps you keep track of new restricted data types as they are captured
2525

2626
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.
2727

28-
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.)
28+
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.)
2929

3030
You can click a row in the Inbox to learn more about a field and where it was collected. The expanded view shows:
3131

@@ -201,7 +201,6 @@ treat that property whenever it is appears in data Segment processes.
201201
3. Set the default classification:
202202
- **Red** for highly restricted
203203
- **Yellow** for moderately restricted
204-
- **Green** for least restricted
205204
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")
206205
5. Select how precise the match should be, by choosing **Exact** or **Similar** match.
207206
- **Exact** matches mean that a key matches the term exactly (for example "phone number" but never "phne number")

0 commit comments

Comments
 (0)