├── .github ├── ISSUE_TEMPLATE.md └── ISSUE_TEMPLATE │ ├── 0--privacy-sandbox.md │ ├── 1--attribution-reporting-api--implementation-.md │ ├── 2--Noise-Lab.md │ ├── 3--chrome-facilitated-testing.md │ └── 4--third-party-cookie-deprecation.md ├── 3pc-migration-readiness.md ├── LICENSE ├── README.md ├── code-of-conduct.md ├── contributing.md └── docs ├── _config.yml └── index.md /.github/ISSUE_TEMPLATE.md: -------------------------------------------------------------------------------- 1 | ## Use Discussions for questions 2 | 3 | *Issues should only be used for documentation hosted in this repo. If that's the 4 | case, delete all this text and raise the issue.* 5 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/0--privacy-sandbox.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: '0: Privacy Sandbox' 3 | about: Question on any Privacy Sandbox API. 4 | title: '' 5 | labels: '' 6 | assignees: '' 7 | 8 | --- 9 | 10 | 11 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/1--attribution-reporting-api--implementation-.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: '1: Attribution Reporting API (implementation)' 3 | about: Technical questions on how to implement Attribution Reporting API code, or 4 | questions on its docs or demo. 5 | title: '' 6 | labels: attribution-reporting 7 | assignees: '' 8 | 9 | --- 10 | 11 | _Open an issue here for technical questions on how to implement Attribution Reporting API code, or questions on the docs or demo for this API. For questions on how to fulfil a certain use case with the API, file an issue in the [spec repository](https://github.com/WICG/conversion-measurement-api/issues) instead._ 12 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/2--Noise-Lab.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: 2. Noise Lab 3 | about: Feature request or bug report on Noise Lab 4 | title: '' 5 | labels: noise-lab 6 | assignees: '' 7 | 8 | --- 9 | 10 | ### To request a feature, fill the field below 11 | 12 | **Feature you'd like to see** 13 | _Describe the feature and the problem it would solve_ 14 | 15 | ### To report a bug, fill the fields below 16 | 17 | **Version** 18 | _Paste the version number of Noise Lab you're using (displayed on the top left of Noise Lab)_ 19 | 20 | **Bug** 21 | _Describe the bug_ 22 | 23 | **How to reproduce** 24 | _Add steps to reproduce the behavior_ 25 | 1. Go to '...' 26 | 2. Click on '....' 27 | 3. See error 28 | 4. ... 29 | 30 | **Expected behavior** 31 | _Describe what you expected to happen._ 32 | 33 | **Screenshots** 34 | _If possible, add screenshots to help explain your problem._ 35 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/3--chrome-facilitated-testing.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: '3: Chrome-facilitated testing' 3 | about: Questions or discussion on the structure and plans of the Chrome-facilitated testing modes. 4 | title: '' 5 | labels: chrome-testing 6 | assignees: '' 7 | 8 | --- 9 | 10 | Read https://developer.chrome.com/docs/privacy-sandbox/chrome-testing/ for context on Mode A, Mode B, and the use of User-Agent Client Hints. 11 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/4--third-party-cookie-deprecation.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: '4: Third-party cookies' 3 | about: Questions or discussion about migrating from third-party coookies to alternative solutions. 4 | title: '' 5 | labels: third-party-cookies 6 | assignees: '' 7 | 8 | --- 9 | 10 | Read https://developer.chrome.com/docs/privacy-sandbox/cookies/ for context before raising issues here. 11 | 12 | For site-specific issues with third-party cookies, please report this via https://goo.gle/report-3pc-broken 13 | -------------------------------------------------------------------------------- /3pc-migration-readiness.md: -------------------------------------------------------------------------------- 1 | # Third-party cookie migration readiness list 2 | 3 | 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. 4 | 5 | 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). 6 | 7 | ## Disclaimers 8 | 9 | * 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. 10 | * 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. 11 | * 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 "\[3PC Migration Readiness List\]" in the subject and the Editors will respond in short order. 12 | * 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](https://privacysandbox.com/news/privacy-sandbox-update/) and are not reflective of Chrome’s [plans for third-party cookies](https://developers.google.com/privacy-sandbox/cookies). 13 | 14 | ## Guidelines 15 | 16 | * Enter information on behalf of your own organization. 17 | * Do not share detailed information inline; instead, link to other public pages (e.g. your own website, customer notes or other resources). 18 | * 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. 19 | * Table fields: 20 | * **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)* 21 | * **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* 22 | * *(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. 23 | * *(Optional)* **How to contact you:** Instructions to contact. This may include items such as an email address or a link to a website form. 24 | * *(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. 25 | * *(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. 26 | 27 | ## How to submit 28 | 29 | 1. On the [Developer Support GitHub page](https://github.com/GoogleChromeLabs/privacy-sandbox-dev-support), 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\!) 30 | 2. Click the pencil icon on the right side to edit the appropriate table below and add your information: 31 | 1. Use the | to make sure that the information that you provide correctly shows up in each cell 32 | 2. You may be directed to fork this repo to apply your own changes. 33 | 3. After you select ‘Propose changes’ an editor will review and publish your updates in the coming days. 34 | 3. You can find additional instructions here for [editing tables in GitHub](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/organizing-information-with-tables). 35 | 36 | ## Table \- Migration readiness 37 | 38 | ### Payments and transactions 39 | 40 | *For example: checkout or processing a credit card transaction* 41 | 42 | | Company / Party / Service | Status | Link to more information or documentation | How to contact you | Action required | Cookie domains | 43 | | :---- | :---- | :---- | :---- | :---- | :---- | 44 | | [br.clear.sale/](https://br.clear.sale/) | Temporary mitigations applied. No site changes required during the [deprecation trial](https://developers.google.com/privacy-sandbox/3pcd/temporary-exceptions/third-party-deprecation-trial#deprecation_trials), updates may be necessary post-trial. | [Api Documentation](https://api.clearsale.com.br/docs/behavior-analytics) | [contact](mailto:integracao@clear.sale?subject=Behavior 3PCD doubts) | | | 45 | | | | | | | | 46 | 47 | ### Embedded widgets 48 | 49 | *For example: an embedded realtime chat or commenting widget* 50 | 51 | | Company / Party / Service | Status | Link to more information or documentation | How to contact you | Action required | Cookie domains | 52 | | :---- | :---- | :---- | :---- | :---- | :---- | 53 | | [tawk.to](https://tawk.to) | No reliance on 3PCs | | | | | 54 | | | | | | | | 55 | 56 | ### IDP/Sign-In 57 | 58 | *For example: single sign-on or social sign-on* 59 | 60 | | Company / Party / Service | State of 3PCD readiness | Link to more information or documentation | How to contact you | Action required | Cookie domains | 61 | | :---- | :---- | :---- | :---- | :---- | :---- | 62 | | [Sign in with Google for Web](https://developers.google.com/identity/gsi/web/guides/overview) | Ready for 3PCD, sites may require to make updates to adopt changes | [Guide \- Migrate to FedCM](https://developers.google.com/identity/gsi/web/guides/fedcm-migration) | [StackOverflow Space](https://stackoverflow.com/questions/tagged/google-signin) | | | 63 | | [Google Identity Services JavaScript library](https://developers.google.com/identity/oauth2/web/guides/overview) | No reliance on 3PCs | | [StackOverflow Space](https://stackoverflow.com/questions/tagged/google-signin) | | | 64 | | [Google Sign-In](https://developers.google.com/identity/sign-in/web/sign-in) | Temporary mitigations applied. No site changes required during the [grace period](https://developers.google.com/privacy-sandbox/cookies/temporary-exceptions/grace-period). However, updates may be necessary when the library transitions to new FedCM APIs. | [Google Sign-in with FedCM APIs](https://developers.google.com/identity/sign-in/web/gsi-with-fedcm) | File a [GitHub](https://github.com/google/google-api-javascript-client/issues) issue or use the [google-sign](https://stackoverflow.com/questions/tagged/google-signin) tag on Stack Overflow | True | | 65 | | [Sec4U \- Authfy](https://www.sec4u.com.br/authfy) | No reliance on 3PCs | | [Sec4U Website](https://www.sec4u.com.br/) | | | 66 | | | | | | | | 67 | 68 | ### Infrastructure 69 | 70 | *For example: a CDN or CMS* 71 | 72 | | Company / Party / Service | State of 3PCD readiness | Link to more information or documentation | How to contact you | Action required | Cookie domains | 73 | | :---- | :---- | :---- | :---- | :---- | :---- | 74 | | | | | | | | 75 | 76 | ### Anti-Fraud and Anti-Abuse 77 | 78 | *For example: a security or anti-fraud vendor* 79 | 80 | | Company / Party / Service | State of 3PCD readiness | Link to more information or documentation | How to contact you | Action required | Cookie domains | 81 | | :---- | :---- | :---- | :---- | :---- | :---- | 82 | | [reCAPTCHA V2](https://developers.google.com/recaptcha/docs/display) | No action needed by sites. Service is compatible with 3PCD. | | [reCAPTCHA Help Center](https://support.google.com/recaptcha/?hl=en) | | | 83 | | [reCAPTCHA V3](https://developers.google.com/recaptcha/docs/v3) | No action needed by sites. Service is compatible with 3PCD. | | [reCAPTCHA Help Center](https://support.google.com/recaptcha/?hl=en) | | | 84 | | [reCAPTCHA Enterprise](https://cloud.google.com/recaptcha-enterprise/docs) | No action needed by sites. Service is compatible with 3PCD. | | [reCAPTCHA Enterprise Help](https://cloud.google.com/recaptcha-enterprise/docs/getting-support) | | | 85 | | [br.clear.sale/](https://br.clear.sale/) | Temporary mitigations applied. No site changes required during the [deprecation trial](https://developers.google.com/privacy-sandbox/3pcd/temporary-exceptions/third-party-deprecation-trial#deprecation_trials), updates may be necessary post-trial. | [Api Documentation](https://api.clearsale.com.br/docs/behavior-analytics) | [contact](mailto:integracao@clear.sale?subject=Behavior 3PCD doubts) | | | 86 | | | | | | | | 87 | 88 | ### Analytics and Business Tools 89 | 90 | *For example: a page analytics or customer experience tool* 91 | 92 | | Company / Party / Service | State of 3PCD readiness | Link to more information or documentation | How to contact you | Action required | Cookie domains | 93 | | :---- | :---- | :---- | :---- | :---- | :---- | 94 | | [Chartbeat \- Heads Up Display](https://chartbeat.com/products/optimization/) | Temporary mitigations applied with a long-term solution in progress. No site changes are expected to be required. | [HUD Documentation](https://help.chartbeat.com/hc/en-us/sections/201761058-Heads-Up-Display) | [Support](mailto:support@chartbeat.com?subject=hud 3PCD) | | | 95 | |[Mather Economics](https://www.mathereconomics.com/),
[Listener First Party Data Platform](https://www.mathereconomics.com/listener-mathers-data-analytics-platform/), &
[Sophi AI](https://www.mathereconomics.com/sophi-start/) | 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](https://www.mathereconomics.com/privacy-policy/)
[Content Paywall (2.0) (sophi.io)](https://resources.sophi.io/integrations/docs) | info@mathereconomics.com | | | 96 | | | | | | | | 97 | 98 | ### Other 99 | 100 | *Anything that doesn't fit into the above categories* 101 | 102 | | Company / Party / Service | State of 3PCD readiness | Link to more information or documentation | How to contact you | Action required | Cookie domains | 103 | | :---- | :---- | :---- | :---- | :---- | :---- | 104 | | [br.clear.sale/](https://br.clear.sale/) | Temporary mitigations applied. No site changes required during the [deprecation trial](https://developers.google.com/privacy-sandbox/3pcd/temporary-exceptions/third-party-deprecation-trial#deprecation_trials), updates may be necessary post-trial. | [Api Documentation](https://api.clearsale.com.br/docs/behavior-analytics) | [contact](mailto:integracao@clear.sale?subject=Behavior%203PC%20doubts) | | | 105 | | [Lunio](https://lunio.ai/) | No reliance on 3PCs | [Cookieless Product Overview](https://lunio.ai/product/) | [Support](https://lunio.ai/about-us/contact/) | | | 106 | | [WordPress VIP](https://wpvip.com/) & [rtCamp](https://rtcamp.com/) | 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](https://wpvip.com/2024/02/21/vip-rtcamp-privacy-sandbox/) | [Get your free audit](https://wpvip.com/website-audit-and-cookie-analysis/) | | | 107 | | [Plumrocket](https://plumrocket.com/) | 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](https://plumrocket.com/blog/privacy-sandbox) | [Get Audit](https://plumrocket.com/contacts) | | | 108 | | | | | | | | 109 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | 2 | Apache License 3 | Version 2.0, January 2004 4 | http://www.apache.org/licenses/ 5 | 6 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 7 | 8 | 1. Definitions. 9 | 10 | "License" shall mean the terms and conditions for use, reproduction, 11 | and distribution as defined by Sections 1 through 9 of this document. 12 | 13 | "Licensor" shall mean the copyright owner or entity authorized by 14 | the copyright owner that is granting the License. 15 | 16 | "Legal Entity" shall mean the union of the acting entity and all 17 | other entities that control, are controlled by, or are under common 18 | control with that entity. For the purposes of this definition, 19 | "control" means (i) the power, direct or indirect, to cause the 20 | direction or management of such entity, whether by contract or 21 | otherwise, or (ii) ownership of fifty percent (50%) or more of the 22 | outstanding shares, or (iii) beneficial ownership of such entity. 23 | 24 | "You" (or "Your") shall mean an individual or Legal Entity 25 | exercising permissions granted by this License. 26 | 27 | "Source" form shall mean the preferred form for making modifications, 28 | including but not limited to software source code, documentation 29 | source, and configuration files. 30 | 31 | "Object" form shall mean any form resulting from mechanical 32 | transformation or translation of a Source form, including but 33 | not limited to compiled object code, generated documentation, 34 | and conversions to other media types. 35 | 36 | "Work" shall mean the work of authorship, whether in Source or 37 | Object form, made available under the License, as indicated by a 38 | copyright notice that is included in or attached to the work 39 | (an example is provided in the Appendix below). 40 | 41 | "Derivative Works" shall mean any work, whether in Source or Object 42 | form, that is based on (or derived from) the Work and for which the 43 | editorial revisions, annotations, elaborations, or other modifications 44 | represent, as a whole, an original work of authorship. For the purposes 45 | of this License, Derivative Works shall not include works that remain 46 | separable from, or merely link (or bind by name) to the interfaces of, 47 | the Work and Derivative Works thereof. 48 | 49 | "Contribution" shall mean any work of authorship, including 50 | the original version of the Work and any modifications or additions 51 | to that Work or Derivative Works thereof, that is intentionally 52 | submitted to Licensor for inclusion in the Work by the copyright owner 53 | or by an individual or Legal Entity authorized to submit on behalf of 54 | the copyright owner. For the purposes of this definition, "submitted" 55 | means any form of electronic, verbal, or written communication sent 56 | to the Licensor or its representatives, including but not limited to 57 | communication on electronic mailing lists, source code control systems, 58 | and issue tracking systems that are managed by, or on behalf of, the 59 | Licensor for the purpose of discussing and improving the Work, but 60 | excluding communication that is conspicuously marked or otherwise 61 | designated in writing by the copyright owner as "Not a Contribution." 62 | 63 | "Contributor" shall mean Licensor and any individual or Legal Entity 64 | on behalf of whom a Contribution has been received by Licensor and 65 | subsequently incorporated within the Work. 66 | 67 | 2. Grant of Copyright License. Subject to the terms and conditions of 68 | this License, each Contributor hereby grants to You a perpetual, 69 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 70 | copyright license to reproduce, prepare Derivative Works of, 71 | publicly display, publicly perform, sublicense, and distribute the 72 | Work and such Derivative Works in Source or Object form. 73 | 74 | 3. Grant of Patent License. Subject to the terms and conditions of 75 | this License, each Contributor hereby grants to You a perpetual, 76 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 77 | (except as stated in this section) patent license to make, have made, 78 | use, offer to sell, sell, import, and otherwise transfer the Work, 79 | where such license applies only to those patent claims licensable 80 | by such Contributor that are necessarily infringed by their 81 | Contribution(s) alone or by combination of their Contribution(s) 82 | with the Work to which such Contribution(s) was submitted. If You 83 | institute patent litigation against any entity (including a 84 | cross-claim or counterclaim in a lawsuit) alleging that the Work 85 | or a Contribution incorporated within the Work constitutes direct 86 | or contributory patent infringement, then any patent licenses 87 | granted to You under this License for that Work shall terminate 88 | as of the date such litigation is filed. 89 | 90 | 4. Redistribution. You may reproduce and distribute copies of the 91 | Work or Derivative Works thereof in any medium, with or without 92 | modifications, and in Source or Object form, provided that You 93 | meet the following conditions: 94 | 95 | (a) You must give any other recipients of the Work or 96 | Derivative Works a copy of this License; and 97 | 98 | (b) You must cause any modified files to carry prominent notices 99 | stating that You changed the files; and 100 | 101 | (c) You must retain, in the Source form of any Derivative Works 102 | that You distribute, all copyright, patent, trademark, and 103 | attribution notices from the Source form of the Work, 104 | excluding those notices that do not pertain to any part of 105 | the Derivative Works; and 106 | 107 | (d) If the Work includes a "NOTICE" text file as part of its 108 | distribution, then any Derivative Works that You distribute must 109 | include a readable copy of the attribution notices contained 110 | within such NOTICE file, excluding those notices that do not 111 | pertain to any part of the Derivative Works, in at least one 112 | of the following places: within a NOTICE text file distributed 113 | as part of the Derivative Works; within the Source form or 114 | documentation, if provided along with the Derivative Works; or, 115 | within a display generated by the Derivative Works, if and 116 | wherever such third-party notices normally appear. The contents 117 | of the NOTICE file are for informational purposes only and 118 | do not modify the License. You may add Your own attribution 119 | notices within Derivative Works that You distribute, alongside 120 | or as an addendum to the NOTICE text from the Work, provided 121 | that such additional attribution notices cannot be construed 122 | as modifying the License. 123 | 124 | You may add Your own copyright statement to Your modifications and 125 | may provide additional or different license terms and conditions 126 | for use, reproduction, or distribution of Your modifications, or 127 | for any such Derivative Works as a whole, provided Your use, 128 | reproduction, and distribution of the Work otherwise complies with 129 | the conditions stated in this License. 130 | 131 | 5. Submission of Contributions. Unless You explicitly state otherwise, 132 | any Contribution intentionally submitted for inclusion in the Work 133 | by You to the Licensor shall be under the terms and conditions of 134 | this License, without any additional terms or conditions. 135 | Notwithstanding the above, nothing herein shall supersede or modify 136 | the terms of any separate license agreement you may have executed 137 | with Licensor regarding such Contributions. 138 | 139 | 6. Trademarks. This License does not grant permission to use the trade 140 | names, trademarks, service marks, or product names of the Licensor, 141 | except as required for reasonable and customary use in describing the 142 | origin of the Work and reproducing the content of the NOTICE file. 143 | 144 | 7. Disclaimer of Warranty. Unless required by applicable law or 145 | agreed to in writing, Licensor provides the Work (and each 146 | Contributor provides its Contributions) on an "AS IS" BASIS, 147 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 148 | implied, including, without limitation, any warranties or conditions 149 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A 150 | PARTICULAR PURPOSE. You are solely responsible for determining the 151 | appropriateness of using or redistributing the Work and assume any 152 | risks associated with Your exercise of permissions under this License. 153 | 154 | 8. Limitation of Liability. In no event and under no legal theory, 155 | whether in tort (including negligence), contract, or otherwise, 156 | unless required by applicable law (such as deliberate and grossly 157 | negligent acts) or agreed to in writing, shall any Contributor be 158 | liable to You for damages, including any direct, indirect, special, 159 | incidental, or consequential damages of any character arising as a 160 | result of this License or out of the use or inability to use the 161 | Work (including but not limited to damages for loss of goodwill, 162 | work stoppage, computer failure or malfunction, or any and all 163 | other commercial damages or losses), even if such Contributor 164 | has been advised of the possibility of such damages. 165 | 166 | 9. Accepting Warranty or Additional Liability. While redistributing 167 | the Work or Derivative Works thereof, You may choose to offer, 168 | and charge a fee for, acceptance of support, warranty, indemnity, 169 | or other liability obligations and/or rights consistent with this 170 | License. However, in accepting such obligations, You may act only 171 | on Your own behalf and on Your sole responsibility, not on behalf 172 | of any other Contributor, and only if You agree to indemnify, 173 | defend, and hold each Contributor harmless for any liability 174 | incurred by, or claims asserted against, such Contributor by reason 175 | of your accepting any such warranty or additional liability. 176 | 177 | END OF TERMS AND CONDITIONS 178 | 179 | APPENDIX: How to apply the Apache License to your work. 180 | 181 | To apply the Apache License to your work, attach the following 182 | boilerplate notice, with the fields enclosed by brackets "[]" 183 | replaced with your own identifying information. (Don't include 184 | the brackets!) The text should be enclosed in the appropriate 185 | comment syntax for the file format. We also recommend that a 186 | file or class name and description of purpose be included on the 187 | same "printed page" as the copyright notice for easier 188 | identification within third-party archives. 189 | 190 | Copyright [yyyy] [name of copyright owner] 191 | 192 | Licensed under the Apache License, Version 2.0 (the "License"); 193 | you may not use this file except in compliance with the License. 194 | You may obtain a copy of the License at 195 | 196 | http://www.apache.org/licenses/LICENSE-2.0 197 | 198 | Unless required by applicable law or agreed to in writing, software 199 | distributed under the License is distributed on an "AS IS" BASIS, 200 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 201 | See the License for the specific language governing permissions and 202 | limitations under the License. 203 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Privacy Sandbox Developer Support 2 | 3 | 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 aims to help sites reduce cross-site and cross-app tracking while helping to keep online content and services free for all. 4 | 5 | Learn more about the project on: 6 | 7 | - Our overview site: [privacysandbox.com](https://privacysandbox.com) 8 | - Our developer documentation: [developer.google.com/privacy-sandbox](https://developer.google.com/privacy-sandbox) 9 | 10 | 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 cookies, you can raise an issue here to ask the team. 11 | 12 | ## Process 13 | 14 | 1. Take a look through the existing [issues](https://github.com/GoogleChromeLabs/privacy-sandbox-dev-support/issues) 15 | to see if your issue has already been raised. 16 | 2. If not, [create a new issue](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. 17 | 3. Make sure you read the [Code of Conduct](/code-of-conduct.md). 18 | 19 | We respond to issues in a number of different ways: 20 | 21 | * 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 help you pull together the specific details for the issue. 22 | * 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. 23 | * 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. 24 | * 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. 25 | 26 | 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. 27 | 28 | ## Open issues in languages other than English 29 | 30 | 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. 31 | 32 | 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. 33 | 34 | ## Third-party cookie deprecation (3PCD) readiness list 35 | 36 | We also use this repo as a location for different companies and organizations to share information about their work migrating from third-party cookies to alternative solutions. 37 | 38 | View and learn how to add your own organization to the [Third-party cookie deprecation (3PCD) readiness list](./3pcd-readiness.md). 39 | -------------------------------------------------------------------------------- /code-of-conduct.md: -------------------------------------------------------------------------------- 1 | # Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | In the interest of fostering an open and welcoming environment, we as 6 | contributors and maintainers pledge to making participation in our project and 7 | our community a harassment-free experience for everyone, regardless of age, body 8 | size, disability, ethnicity, gender identity and expression, level of 9 | experience, education, socio-economic status, nationality, personal appearance, 10 | race, religion, or sexual identity and orientation. 11 | 12 | ## Our Standards 13 | 14 | Examples of behavior that contributes to creating a positive environment 15 | include: 16 | 17 | * Using welcoming and inclusive language 18 | * Being respectful of differing viewpoints and experiences 19 | * Gracefully accepting constructive criticism 20 | * Focusing on what is best for the community 21 | * Showing empathy towards other community members 22 | 23 | Examples of unacceptable behavior by participants include: 24 | 25 | * The use of sexualized language or imagery and unwelcome sexual attention or 26 | advances 27 | * Trolling, insulting/derogatory comments, and personal or political attacks 28 | * Public or private harassment 29 | * Publishing others' private information, such as a physical or electronic 30 | address, without explicit permission 31 | * Other conduct which could reasonably be considered inappropriate in a 32 | professional setting 33 | 34 | ## Our Responsibilities 35 | 36 | Project maintainers are responsible for clarifying the standards of acceptable 37 | behavior and are expected to take appropriate and fair corrective action in 38 | response to any instances of unacceptable behavior. 39 | 40 | Project maintainers have the right and responsibility to remove, edit, or reject 41 | comments, commits, code, wiki edits, issues, and other contributions that are 42 | not aligned to this Code of Conduct, or to ban temporarily or permanently any 43 | contributor for other behaviors that they deem inappropriate, threatening, 44 | offensive, or harmful. 45 | 46 | ## Scope 47 | 48 | This Code of Conduct applies both within project spaces and in public spaces 49 | when an individual is representing the project or its community. Examples of 50 | representing a project or community include using an official project e-mail 51 | address, posting via an official social media account, or acting as an appointed 52 | representative at an online or offline event. Representation of a project may be 53 | further defined and clarified by project maintainers. 54 | 55 | This Code of Conduct also applies outside the project spaces when the Project 56 | Steward has a reasonable belief that an individual's behavior may have a 57 | negative impact on the project or its community. 58 | 59 | ## Conflict Resolution 60 | 61 | We do not believe that all conflict is bad; healthy debate and disagreement 62 | often yield positive results. However, it is never okay to be disrespectful or 63 | to engage in behavior that violates the project’s code of conduct. 64 | 65 | If you see someone violating the code of conduct, you are encouraged to address 66 | the behavior directly with those involved. Many issues can be resolved quickly 67 | and easily, and this gives people more control over the outcome of their 68 | dispute. If you are unable to resolve the matter for any reason, or if the 69 | behavior is threatening or harassing, report it. We are dedicated to providing 70 | an environment where participants feel welcome and safe. 71 | 72 | Reports should be directed to *[PROJECT STEWARD NAME(s) AND EMAIL(s)]*, the 73 | Project Steward(s) for *[PROJECT NAME]*. It is the Project Steward’s duty to 74 | receive and address reported violations of the code of conduct. They will then 75 | work with a committee consisting of representatives from the Open Source 76 | Programs Office and the Google Open Source Strategy team. If for any reason you 77 | are uncomfortable reaching out to the Project Steward, please email 78 | opensource@google.com. 79 | 80 | We will investigate every complaint, but you may not receive a direct response. 81 | We will use our discretion in determining when and how to follow up on reported 82 | incidents, which may range from not taking action to permanent expulsion from 83 | the project and project-sponsored spaces. We will notify the accused of the 84 | report and provide them an opportunity to discuss it before any action is taken. 85 | The identity of the reporter will be omitted from the details of the report 86 | supplied to the accused. In potentially harmful situations, such as ongoing 87 | harassment or threats to anyone's safety, we may take action without notice. 88 | 89 | ## Attribution 90 | 91 | This Code of Conduct is adapted from the Contributor Covenant, version 1.4, 92 | available at 93 | https://www.contributor-covenant.org/version/1/4/code-of-conduct.html 94 | -------------------------------------------------------------------------------- /contributing.md: -------------------------------------------------------------------------------- 1 | # How to Contribute 2 | 3 | We'd love to accept your patches and contributions to this project. There are 4 | just a few small guidelines you need to follow. 5 | 6 | ## Contributor License Agreement 7 | 8 | Contributions to this project must be accompanied by a Contributor License 9 | Agreement. You (or your employer) retain the copyright to your contribution; 10 | this simply gives us permission to use and redistribute your contributions as 11 | part of the project. Head over to to see 12 | your current agreements on file or to sign a new one. 13 | 14 | You generally only need to submit a CLA once, so if you've already submitted one 15 | (even if it was for a different project), you probably don't need to do it 16 | again. 17 | 18 | ## Code Reviews 19 | 20 | All submissions, including submissions by project members, require review. We 21 | use GitHub pull requests for this purpose. Consult 22 | [GitHub Help](https://help.github.com/articles/about-pull-requests/) for more 23 | information on using pull requests. 24 | 25 | ## Community Guidelines 26 | 27 | This project follows [Google's Open Source Community 28 | Guidelines](https://opensource.google/conduct/). 29 | -------------------------------------------------------------------------------- /docs/_config.yml: -------------------------------------------------------------------------------- 1 | theme: jekyll-theme-minimal -------------------------------------------------------------------------------- /docs/index.md: -------------------------------------------------------------------------------- 1 | # Privacy Sandbox Developer Support 2 | 3 | **Summary - ask your Privacy Sandbox developer question in the [Discussions](https://github.com/GoogleChromeLabs/privacy-sandbox-dev-support/discussions)!** 4 | 5 | You can learn more about the Privacy Sandbos and the associated projects at: 6 | 7 | * [web.dev/digging-into-the-privacy-sandbox](https://web.dev/digging-into-the-privacy-sandbox/) 8 | * [www.chromium.org/Home/chromium-privacy/privacy-sandbox](https://www.chromium.org/Home/chromium-privacy/privacy-sandbox) 9 | * [privacysandbox.com](https://privacysandbox.com/) 10 | 11 | These efforts are divided into three main areas: 12 | 13 | 1. 🧰 Replacing functionality served by cross-site tracking 14 | 2. 🍪 Phasing out third-party cookies 15 | 3. 🕶️ Mitigating workarounds 16 | 17 | As these changes come to the web platform, Chrome, and other browsers it means 18 | that you, as a web developer, will have changes to make to your sites. Either to 19 | take advantage of new APIs or to ensure that you're taking into account 20 | new restrictions. 21 | 22 | Our aim is to land these with clear documentation and minimal disruption, but 23 | it's likely you're going to have questions and we're here to try and answer 24 | them! You can raise issues directly in this repo, and we'll also use this as a 25 | location to collate questions and issues we hear from around the ecosystem. 26 | 27 | ## Process 28 | 29 | 1. Take a look through the existing [Discussions](https://github.com/GoogleChromeLabs/privacy-sandbox-dev-support/discussions) 30 | to see if your issue has already been raised. 31 | 2. If not, create a new one! There are existing topics, but don't worry too much 32 | about picking the right one - we'll still answer. 33 | 3. Make sure you read the [Code of Conduct](https://github.com/GoogleChromeLabs/privacy-sandbox-dev-support/blob/main/code-of-conduct.md). 34 | 35 | We will respond to your issues in a number of different ways: 36 | 37 | * If your question is best raised as an issue against one the Privacy Sandbox 38 | proposals, we will point you to the right repo and can help you pull together 39 | the specific details for the issue. 40 | * If your question is actually an implementation issue, we will point you to the 41 | relevant component on the browser's bug tracker (doesn't have to be Chrome!) 42 | and can help you get the specific details needed for the issue. 43 | * If your question is already covered by existing documentation, we will point 44 | you to that, but we will also try to understand what meant it wasn't easily 45 | discovered or evident in the first place. There's probably something we can do 46 | to make the documentation better! 47 | * And, of course, if your question relates to what you need to specifically do 48 | on your site - then we will help work through a plan with you. The aim is that 49 | we will use your question to create the first draft of documentation. 50 | 51 | Your question may well cover several of these things in one, so we will also 52 | separate all those threads with you to get to the answers you need. 53 | 54 | You can also contact the team via 55 | [@ChromiumDev](https://twitter.com/ChromiumDev). 56 | --------------------------------------------------------------------------------