Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update portal.md #7386

Draft
wants to merge 1 commit into
base: develop
Choose a base branch
from
Draft

Update portal.md #7386

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/privacy/portal.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -227,7 +227,7 @@ Fields that are classified as 'Red' are masked for users that do not have PII Ac
Keep in mind that if you have set Standard Controls to block fields from any of your sources, any new classifications you create in the Inbox will start to take affect immediately. For example, if you have a Privacy Control set up to block **Red** data from your Android source, any new fields you classify in the Inbox as **Red** will be blocked from entering Segment from your Android source.

**Yellow Classification**:
Fields that are classified as 'Yellow' are masked for users that do not have PII Access enabled.
Fields that are classified as 'Yellow' are masked for users that do not have PII Access enabled. A Custom Matcher is needed to mask fields other than those in the Default PII Matchers list.

**Green Classification**:
Classifying a field as 'Green' does not have any impact on the behavior of masking of fields within the Segment App, it is only available for the housekeeping purposes.
Expand Down