Skip to content
This repository has been archived by the owner on Mar 14, 2024. It is now read-only.

Commit

Permalink
Update Protected Audience article
Browse files Browse the repository at this point in the history
Changes taken from #5862  (which refers to the initial /fledge/ file).
  • Loading branch information
samdutton authored Oct 31, 2023
1 parent 8f4012c commit 74032d0
Showing 1 changed file with 14 additions and 13 deletions.
27 changes: 14 additions & 13 deletions site/en/docs/privacy-sandbox/protected-audience/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ description: >
websites a user has previously visited, designed so it cannot be
used by third parties to track user browsing behavior across sites.
date: 2022-01-27
updated: 2022-09-18
updated: 2023-10-31
authors:
- samdutton
- kevinkiklee
Expand Down Expand Up @@ -157,20 +157,21 @@ which features are already implemented and what's still in progress.

### What browser configuration is available? {: #user-controls}

Users can adjust their participation for Privacy Sandbox trials in Chrome by
enabling or disabling the top-level setting in
`chrome://settings/privacySandbox`. During initial testing, users can opt out of the Protected Audience API using the
Privacy Sandbox settings.
Users can adjust their participation in Privacy Sandbox trials by enabling or disabling the
top-level setting in `chrome://settings/privacySandbox`. During initial testing, people can use the
Privacy Sandbox setting to opt out of FLEDGE. API callers can't access group membership when users
browse in Incognito mode, and membership is removed when users clear their site data.

Chrome plans to allow users to see and manage the list of interest groups
they've been added to across the sites they've visited. As with the Privacy
Sandbox technologies, user settings may evolve with feedback from users,
regulators, and others.
`chrome://settings/adPrivacy/sites` lists sites where the user has been added to an interest group.
Chrome DevTools [shows interest groups](/blog/fledge-api/#observe-fledge-events)
that have been joined, left, or that participated in an auction.

{% Img src="image/80mq7dk16vVEg8BBhsVe42n6zn82/jkNZ1ZT44itRV653UiPX.png",
alt="Chrome settings for FLEDGE", width="800", height="648" %}

We'll update the available settings in Chrome as the Protected Audience API progresses,
[based on tests and feedback](/docs/privacy-sandbox/proposal-lifecycle/#testing).
In the future, we'll offer more granular settings to manage Protected Audience and
associated data.
As with other Privacy Sandbox technologies, user settings will evolve
[based on tests and feedback](/docs/privacy-sandbox/proposal-lifecycle/#testing) from users,
regulators, and others.

API callers can't access group membership when users browse in Incognito mode,
and membership is removed when users clear their site data.
Expand Down

0 comments on commit 74032d0

Please sign in to comment.