From 74032d0e02b991382b51f267286fee107399c245 Mon Sep 17 00:00:00 2001 From: Sam Dutton Date: Tue, 31 Oct 2023 12:45:32 +0000 Subject: [PATCH 1/2] Update Protected Audience article Changes taken from #5862 (which refers to the initial /fledge/ file). --- .../protected-audience/index.md | 27 ++++++++++--------- 1 file changed, 14 insertions(+), 13 deletions(-) diff --git a/site/en/docs/privacy-sandbox/protected-audience/index.md b/site/en/docs/privacy-sandbox/protected-audience/index.md index 9c4fcc3f6830..0be6d79226c7 100644 --- a/site/en/docs/privacy-sandbox/protected-audience/index.md +++ b/site/en/docs/privacy-sandbox/protected-audience/index.md @@ -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 @@ -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. From bc3b54e9d3cbeac02e78ed1c41d2bdb68d2cc1f2 Mon Sep 17 00:00:00 2001 From: Sam Dutton Date: Tue, 31 Oct 2023 15:41:33 +0000 Subject: [PATCH 2/2] Update index.md --- site/en/docs/privacy-sandbox/protected-audience/index.md | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/site/en/docs/privacy-sandbox/protected-audience/index.md b/site/en/docs/privacy-sandbox/protected-audience/index.md index 0be6d79226c7..86ac5a76744d 100644 --- a/site/en/docs/privacy-sandbox/protected-audience/index.md +++ b/site/en/docs/privacy-sandbox/protected-audience/index.md @@ -157,17 +157,14 @@ which features are already implemented and what's still in progress. ### What browser configuration is available? {: #user-controls} -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. +Users can control access to Privacy Sandbox APIs from `chrome://settings/privacySandbox`. `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" %} +{% Img src="image/80mq7dk16vVEg8BBhsVe42n6zn82/1cZU24BcqUZ4LbbUtYcY.png", + alt="Chrome settings for Protected Audience", width="800", height="499" %} As with other Privacy Sandbox technologies, user settings will evolve [based on tests and feedback](/docs/privacy-sandbox/proposal-lifecycle/#testing) from users,