Page 10 - May_1_Newsletter_2024

the BlockThirdPartyCookies policy to false to opt out their managed browsers ahead of the experiment and
allow time to make necessary changes to not rely on this policy or third-party cookies. You can read more in
the Chrome Enterprise release notes.

We also intend to provide further reporting and tooling to help identify third-party cookie usage on enterprise
sites. We have less visibility of enterprise browsers in Chrome's usage metrics which means it is especially
important for enterprises to test for breakage and report issues to us.

Enterprise SaaS integrations will be able to use the third-party deprecation trial described below.

Request additional time with the third-party deprecation trial for non-

advertising use cases

As with many previous deprecations on the web, we understand there are cases where sites need extra time to
make the necessary changes. When it comes to privacy-related changes like this, we also have to balance that
against the best interests of people using the web.

We plan to offer a deprecation trial to provide a way for sites or services used in a cross-site context to register
for continued access to third-party cookies for a limited period of time.

Key term: deprecation trials are a type of origin trial that allow a feature to be temporarily re-enabled.

We will share more details as plans progress, but we are starting with a few key principles:

· It will be a third-party deprecation trial allowing third-party embeds to opt in to temporarily continue
using third-party cookies.

· Registering will require a review process to ensure the deprecation trial is only used for functions that
greatly affect critical user journeys and registrations will be considered on a case by case basis.

· It will not interfere with the advertising testing planned for the start of 2024, as described by the
CMA. As such, this means advertising use cases will not be considered for the deprecation trial.Next
step: We will publish an Intent to the blink-dev mailing list with further details this month and contin-
ue to update documentation here.

Preserving critical user experiences

Cross-site cookies have been a critical part of the web for over a quarter of a century. This makes any change,
especially a breaking change, a complex process that requires a coordinated and incremental approach. While
the additional cookie attributes and new privacy-focused APIs account for the majority of use cases, there are
specific scenarios where we want to ensure we do not break the experience for people using those sites.

Primarily these are authentication or payment flows where a top-level site either opens a pop-up window or
redirects to a third-party site for an operation and then returns to the top-level site, making use of a cookie ei-
ther on that return journey or in the embedded context. We intend to provide a temporary set of heuristics to