The purpose of this page is to consolidate information about how companies across the web are reducing their reliance on third-party cookies. The usefulness of this page depends on participants sharing information and updates.
Note: This page is primarily focused on non-advertising use cases such as payments, sign-in and other types of non-advertising services and user features. Companies testing and adopting the Privacy Sandbox relevance and measurement APIs can note their status on the GitHub tester pages for Protected Audience, Topics and Attribution Reporting.
- Not a complete list. Participants are strongly encouraged to share their activities and insights publicly for the benefit of the broader community, but sharing is voluntary and therefore this page is not expected to reflect all activity.
- Not evaluative. Editors will review submissions for relevance and to ensure general conformance to the guidelines above, but are not evaluating or endorsing the information provided.
- Editors will regularly review and approve submissions that meet the guidelines below. If you believe that there's an error in a submission, please create an issue in the Privacy Sandbox Developer Support repository with the words "[3PC Migration Readiness List]" in the subject and the Editors will respond in short order.
- Some entries may reference third-party cookie “deprecation.” These entries were added prior to the announcement of a new way forward for Privacy Sandbox on the web and are not reflective of Chrome’s plans for third-party cookies.
- Enter information on behalf of your own organization.
- Do not share detailed information inline; instead, link to other public pages (e.g. your own website, customer notes or other resources).
- Add entries to the relevant category in the 'Table - Readiness' section below. If the entry fits into multiple categories, please list them in each relevant category.
- Table fields:
- Company/Party/Service: The organization, company, service, or site entering information about their use of third-party cookies. If the service/site is part of a larger company, provide the company name in parentheses. For example: news.example (ACME), stocks.example (ACME)
- Status: A short free-text status update for the entity listed. For example: Ready for 3PC unavailability, No reliance on 3PCs, Temporary mitigations applied, No known issues, Implementing CHIPS by end Q4 2024
- (Optional) Link to relevant documentation: Link to blog posts, customer-facing documentation, or other relevant guidance supporting your site/service's plans for reducing 3PC reliance.
- (Optional) How to contact you: Instructions to contact. This may include items such as an email address or a link to a website form.
- (Optional) Action required: True/false to indicate whether or not sites embedding your service need to take action. In the future, this detail may be consumed by Chrome DevTools to help inform top-level sites of any action required to prepare for 3PC changes.
- (Optional) Cookie domains: A comma separated list of domains (or subdomains) used by your service to serve third-party cookies. This detail may be consumed by Chrome DevTools to help inform top-level sites of the status of your 3PC migration. If you do not wish for your entry to be visible to Chrome DevTools users, leave this field blank.
-
On the Developer Support GitHub page, navigate to the document in the main table called 3pc-migration-readiness.md (If you can read this sentence then you have already completed this step!)
-
Click the pencil icon on the right side to edit the appropriate table below and add your information:
- Use the | to make sure that the information that you provide correctly shows up in each cell
- You may be directed to fork this repo to apply your own changes.
- After you select ‘Propose changes’ an editor will review and publish your updates in the coming days.
-
You can find additional instructions here for editing tables in GitHub.
For example: checkout or processing a credit card transaction
| Company / Party / Service | Status | Link to more information or documentation | How to contact you | Action required | Cookie domains |
|---|---|---|---|---|---|
| br.clear.sale/ | Temporary mitigations applied. No site changes required during the deprecation trial, updates may be necessary post-trial. | Api Documentation | contact | ||
For example: an embedded realtime chat or commenting widget
| Company / Party / Service | Status | Link to more information or documentation | How to contact you | Action required | Cookie domains |
|---|---|---|---|---|---|
| tawk.to | No reliance on 3PCs | ||||
For example: single sign-on or social sign-on
| Company / Party / Service | State of 3PCD readiness | Link to more information or documentation | How to contact you | Action required | Cookie domains |
|---|---|---|---|---|---|
| Sign in with Google for Web | Ready for 3PCD, sites may require to make updates to adopt changes | Guide - Migrate to FedCM | StackOverflow Space | ||
| Google Identity Services JavaScript library | No reliance on 3PCs | StackOverflow Space | |||
| Google Sign-In | Temporary mitigations applied. No site changes required during the deprecation trial, updates may be necessary post-trial. | Deprecation and Sunset | File a GitHub issue or use the google-sign tag on Stack Overflow | ||
| Sec4U - Authfy | No reliance on 3PCs | Sec4U Website | |||
For example: a CDN or CMS
| Company / Party / Service | State of 3PCD readiness | Link to more information or documentation | How to contact you | Action required | Cookie domains |
|---|---|---|---|---|---|
For example: a security or anti-fraud vendor
| Company / Party / Service | State of 3PCD readiness | Link to more information or documentation | How to contact you | Action required | Cookie domains |
|---|---|---|---|---|---|
| reCAPTCHA V2 | No action needed by sites. Service is compatible with 3PCD. | reCAPTCHA Help Center | |||
| reCAPTCHA V3 | No action needed by sites. Service is compatible with 3PCD. | reCAPTCHA Help Center | |||
| reCAPTCHA Enterprise | No action needed by sites. Service is compatible with 3PCD. | reCAPTCHA Enterprise Help | |||
| br.clear.sale/ | Temporary mitigations applied. No site changes required during the deprecation trial, updates may be necessary post-trial. | Api Documentation | contact | ||
For example: a page analytics or customer experience tool
| Company / Party / Service | State of 3PCD readiness | Link to more information or documentation | How to contact you | Action required | Cookie domains |
|---|---|---|---|---|---|
| Chartbeat - Heads Up Display | Temporary mitigations applied with a long-term solution in progress. No site changes are expected to be required. | HUD Documentation | Support | ||
| Mather Economics, Listener First Party Data Platform, & Sophi AI |
Prepared for 3PCD. All Mather Economics and Sophi clients will not be impacted. All of Mather Economics products and services use first party data and are integrated directly in collaboration with our clients. | Privacy Policy - Mather Economics Content Paywall (2.0) (sophi.io) |
[email protected] | ||
Anything that doesn't fit into the above categories
| Company / Party / Service | State of 3PCD readiness | Link to more information or documentation | How to contact you | Action required | Cookie domains |
|---|---|---|---|---|---|
| br.clear.sale/ | Temporary mitigations applied. No site changes required during the deprecation trial, updates may be necessary post-trial. | Api Documentation | contact | ||
| Lunio | No reliance on 3PCs | Cookieless Product Overview | Support | ||
| WordPress VIP & rtCamp | Prepared for 3PCD and offering audits to help businesses evaluate and understand the impact of third-party cookie deprecation | WordPress VIP and rtCamp Partner to Help Businesses Adapt to New Web Privacy Standards | Get your free audit | ||
| Plumrocket | Ready for 3PC deprecation. Conducting cookie audits to help businesses identify issues related to 3PC deprecation and adapt to the changes. | Third-Party Cookie Audit | Get Audit | ||