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

Update to FLEDGE settings content [DON'T MERGE BEFORE REVIEW] #5862

Closed
wants to merge 4 commits into from
Closed
Changes from 3 commits
Commits
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
28 changes: 13 additions & 15 deletions site/en/docs/privacy-sandbox/fledge/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-08-23
updated: 2023-03-29
alexandrascript marked this conversation as resolved.
Show resolved Hide resolved
authors:
- samdutton
- kevinkiklee
Expand Down Expand Up @@ -169,23 +169,21 @@ 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, people can use the
Privacy Sandbox setting to opt out of FLEDGE.
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 that
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.

We'll update the available settings in Chrome as the FLEDGE proposal
progresses, [based on tests and feedback](/docs/privacy-sandbox/proposal-lifecycle/#testing).
In the future, we'll offer more granular settings to manage FLEDGE and
associated data.
{% Img src="image/80mq7dk16vVEg8BBhsVe42n6zn82/jkNZ1ZT44itRV653UiPX.png",
alt="Chrome settings for FLEDGE", width="800", height="648" %}

API callers can't access group membership when users browse in Incognito mode,
and membership is removed when users clear their site 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.

{: #opt-out-site}

Expand Down