Skip to content

Commit

Permalink
Merge pull request #274 from GoogleChromeLabs/2024-clean-up
Browse files Browse the repository at this point in the history 
Clean up and add 3PCD readiness list
  • Loading branch information
@samdutton
samdutton authored Mar 7, 2024
2 parents 01b9fe8 + 3c8eb91 commit 8fdb77e
Show file tree
Hide file tree
Showing 2 changed files with 89 additions and 70 deletions.
73 changes: 73 additions & 0 deletions 3pcd-readiness.md
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,73 @@
# Third-party cookie deprecation (3PCD) readiness list

The purpose of this page is to consolidate information about how companies across the web are preparing for third-party cookie deprecation. 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](https://github.com/WICG/turtledove/blob/main/fledge-tester-list.md), [Topics](https://github.com/patcg-individual-drafts/topics/blob/main/topics-tester-list.md) and [Attribution Reporting](https://github.com/WICG/attribution-reporting-api/blob/main/ara-tester-list.md).

## Disclaimers

* 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](https://github.com/GoogleChromeLabs/privacy-sandbox-dev-support) with the words "[3PCD Readiness List]" in the subject and the Editors will respond in short order.

## Guidelines

* 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 3PCD readiness. 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 3PCD, No reliance on 3PCs, Temporary mitigations applied, No known issues, Implementing CHIPS by June 1, 2024_
* _(Optional)_ **Link to relevant documentation**: Link to blog posts, customer-facing documentation, or other relevant guidance supporting your site/service's 3PCD readiness.
* _(Optional)_ **How to contact you**: Instructions to contact. This may include items such as an email address or a link to a website form.

## How to submit

1. On the [Developer Support GitHub page](https://github.com/GoogleChromeLabs/privacy-sandbox-dev-support), navigate to the document in the main table called (If you can read this sentence then you have already completed this step!)
2. Click the pencil icon on the right side to edit the appropriate table below and add your information:
1. Use the `|` to make sure that the information that you provide correctly shows up in each cell
2. 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](https://docs.github.com/get-started/writing-on-github/working-with-advanced-formatting/organizing-information-with-tables).

## Table - Readiness

### Payments and transactions

_For example: checkout or processing a credit card transaction_

| Company / Party / Service | State of 3PCD readiness | Link to more information or documentation | How to contact you |
|---|---|---|---|
| <!-- copy this row --> | <!-- insert it above this line --> | <!-- fill in your info --> | <!-- submit the request --> |

### Embedded widgets

_For example: an embedded realtime chat or commenting widget_

| Company / Party / Service | State of 3PCD readiness | Link to more information or documentation | How to contact you |
|---|---|---|---|
| <!-- copy this row --> | <!-- insert it above this line --> | <!-- fill in your info --> | <!-- submit the request --> |

### IDP/Sign-In

_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 |
|---|---|---|---|
| <!-- copy this row --> | <!-- insert it above this line --> | <!-- fill in your info --> | <!-- submit the request --> |

### Infrastructure

_For example: a CDN or CMS_

| Company / Party / Service | State of 3PCD readiness | Link to more information or documentation | How to contact you |
|---|---|---|---|
| <!-- copy this row --> | <!-- insert it above this line --> | <!-- fill in your info --> | <!-- submit the request --> |

### Other

_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 |
|---|---|---|---|
| <!-- copy this row --> | <!-- insert it above this line --> | <!-- fill in your info --> | <!-- submit the request --> |
86 changes: 16 additions & 70 deletions README.md
View file
Original file line number Diff line number Diff line change
@@ -1,92 +1,38 @@
# Privacy Sandbox Developer Support

**Summary: ask your Privacy Sandbox developer questions in the [Issues](https://github.com/GoogleChromeLabs/privacy-sandbox-dev-support/issues)!**
The Privacy Sandbox initiative aims to create technologies that both protect people's privacy online and give companies and developers tools to build thriving digital businesses. The Privacy Sandbox reduces cross-site and cross-app tracking while helping to keep online content and services free for all.

You can learn more about the Privacy Sandbox and associated projects at:
Learn more about the project on:

* [developer.chrome.com/docs/privacy-sandbox](https://developer.chrome.com/docs/privacy-sandbox)
* [web.dev/digging-into-the-privacy-sandbox](https://web.dev/digging-into-the-privacy-sandbox)
* [chromium.org/Home/chromium-privacy/privacy-sandbox](https://www.chromium.org/Home/chromium-privacy/privacy-sandbox)
* [privacysandbox.com](https://privacysandbox.com)
- Our overview site: [privacysandbox.com](https://privacysandbox.com)
- Our developer documentation: [developer.google.com/privacy-sandbox](https://developer.google.com/privacy-sandbox)

These efforts are divided into three main areas:

1. 🧰 Replacing functionality served by cross-site tracking.
2. 🍪 Phasing out third-party cookies.
3. 🕶️ Mitigating workarounds.

As these changes come to the web platform, to Chrome and other browsers,
web developers will have to make changes to your sites. These changes may
take advantage of new APIs or ensure that you take into account new
restrictions.

We aim to land these changes with clear documentation and minimal disruption, but
it's likely you're going to have questions. We're here to try and answer
them! You can raise issues directly in this repo, and we'll also use this as a
location to collate questions and issues we hear from around the ecosystem.
That said, documentation doesn't always answer every question and that's what this repo is for. If you have questions around developer issues relating to Privacy Sandbox or third-party cookie deprecation, you can raise an issue here to ask the team.

## Process

1. Take a look through the existing [Issues](https://github.com/GoogleChromeLabs/privacy-sandbox-dev-support/issues)
to see if your issue has already been raised.
2. If not, create a new one! Don't worry about getting it exactly right first time, it's just the start of the discussion.
2. If not, [create a new one](https://github.com/GoogleChromeLabs/privacy-sandbox-dev-support/issues/new/choose)! Don't worry about getting it exactly right first time, it's just the start of the discussion.
3. Make sure you read the [Code of Conduct](/code-of-conduct.md).

We respond to Issues in a number of different ways:

* If your question is best raised as an issue against one of the Privacy Sandbox
proposals, we'll point you to the right repository and can help you pull together
the specific details for the issue.
* If your question is actually an implementation issue, we'll point you to the
relevant component on the browser's bug tracker (it doesn't have to be Chrome!)
and we can help you get the specific details needed for the issue.
* If your question is already covered by existing documentation, we'll share the docs,
and will try to understand the reasons why an answer to your question wasn't easily
discovered or evident in the first place. We'll follow up with documentation updates
if relevant.
* And, of course, if your question relates to what you need to specifically do
on your site, then we can help work through a plan with you. We may use
your question to create the first draft of documentation.
* If your question is best raised as an issue against one of the Privacy Sandbox proposals, we'll point you to the right repository and can help you pull together the specific details for the issue.
* If your question is actually an implementation issue, we'll point you to the relevant component on the browser's bug tracker (it doesn't have to be Chrome!) and we can help you get the specific details needed for the issue.
* If your question is already covered by existing documentation, we'll share the docs, and will try to understand the reasons why an answer to your question wasn't easily discovered or evident in the first place. We'll follow up with documentation updates if relevant.
* And, of course, if your question relates to what you need to specifically do on your site, then we can help work through a plan with you. We may use your question to create the first draft of documentation.

Your question may fall under several of these categories, and we may
separate all those threads with you to get to the answers you need.
Your question may fall under several of these categories, and we may separate all those threads with you to get to the answers you need.

## Open Issues in languages other than English

While the primary language for our Developer Relations team is English,
we know that's not the case for all of our developers. We’ll use our best
effort to understand Issues opened in languages other than English, with
the help of Google Translate. We will copy the translation into our
comment, and respond in English.

If you have further feedback or questions, you can continue to reply to us
in your preferred language, and we’ll follow this same protocol.

## Other channels

The Privacy Sandbox
[Feedback documentation](https://developer.chrome.com/docs/privacy-sandbox/feedback/)
explains where and how to provide feedback for Privacy Sandbox APIs
and proposals throughout the development process.

### Mailing lists for specific origin trials

You may be experimenting with Privacy Sandbox APIs via origin trials.
In this case, join the related mailing list to post your questions
and receive updates about your origin trial.

Available mailing lists:
While the primary language for our Developer Relations team is English, we know that's not the case for all of our developers. We’ll use our best effort to understand Issues opened in languages other than English, with the help of Google Translate. We will copy the translation into our comment, and respond in English.

* [Attribution Reporting (Conversion Measurement)](https://groups.google.com/u/1/a/chromium.org/g/attribution-reporting-api-dev)
* [Topics](https://groups.google.com/u/4/a/chromium.org/g/topics-api-announce)
* [FLEDGE](https://groups.google.com/u/4/a/chromium.org/g/fledge-api-announce)
* [Shared Storage](https://groups.google.com/a/chromium.org/g/shared-storage-api-announcements)
* [First-Party Sets](https://groups.google.com/a/chromium.org/g/first-party-sets-discuss)
If you have further feedback or questions, you can continue to reply to us in your preferred language, and we’ll follow this same protocol.

If no dedicated mailing list is available for your origin trial, ask your
questions on this repository.
## Third-party cookie deprecation (3PCD) readiness list

### Twitter
We also use this repo as a location for different companies and organizations to share information about their preparation for third-party cookie deprecation.

You can contact the team via
[@ChromiumDev](https://twitter.com/ChromiumDev).
View and learn how to add your own organization to the [Third-party cookie deprecation (3PCD) readiness list](./3pcd-readiness.md).

0 comments on commit 8fdb77e

Please sign in to comment.