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

Commit 74032d0

Browse files
authored
Update Protected Audience article
Changes taken from #5862 (which refers to the initial /fledge/ file).
1 parent 8f4012c commit 74032d0

1 file changed

Lines changed: 14 additions & 13 deletions

File tree

  • site/en/docs/privacy-sandbox/protected-audience

site/en/docs/privacy-sandbox/protected-audience/index.md

Lines changed: 14 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ description: >
99
websites a user has previously visited, designed so it cannot be
1010
used by third parties to track user browsing behavior across sites.
1111
date: 2022-01-27
12-
updated: 2022-09-18
12+
updated: 2023-10-31
1313
authors:
1414
- samdutton
1515
- kevinkiklee
@@ -157,20 +157,21 @@ which features are already implemented and what's still in progress.
157157

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

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

165-
Chrome plans to allow users to see and manage the list of interest groups
166-
they've been added to across the sites they've visited. As with the Privacy
167-
Sandbox technologies, user settings may evolve with feedback from users,
168-
regulators, and others.
165+
`chrome://settings/adPrivacy/sites` lists sites where the user has been added to an interest group.
166+
Chrome DevTools [shows interest groups](/blog/fledge-api/#observe-fledge-events)
167+
that have been joined, left, or that participated in an auction.
168+
169+
{% Img src="image/80mq7dk16vVEg8BBhsVe42n6zn82/jkNZ1ZT44itRV653UiPX.png",
170+
alt="Chrome settings for FLEDGE", width="800", height="648" %}
169171

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

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

0 commit comments

Comments
 (0)