Skip to content
Alberto Medina edited this page Jul 26, 2024 · 37 revisions

Welcome to the Privacy Sandbox Analysis Tool (PSAT) Wiki!

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 main goal of Privacy Sandbox is to provide in Chrome the functionality and user choice to enable the capabilities that keep online content and services freely accessible by everyone, while reducing cross-site tracking on behalf of users.

Transitioning to a more privacy-preserving web

If you are website developer, or a developer of components used by web sites, and you use third-party cookies to achieve your goals, there good news is that you can now achieve the goals of you technologies and protect your users from violations of their privacy, by moving away from using unpartitioned third-party cookies and take advantage of new provacy-preserving APIs.

Transitioning to a more private web encompasses the following steps:

The Privacy Sandbox Analysis Tool

The purpose of this tool is to help developers like you in making your sites/applications more robust in protecting the privacy of users. This wiki outlines a testing/evaluation methodology that will guide you in analyzing your scenarios and the necessary insights needed to implement changes, including:

  1. How to set up an Evaluation Environment that will help predict what is likely to happen when third-party cookies have been blocked.
  2. How to identify specific aspects of the site that are likely to be affected, amongst other General debugging actions for Analysis.
  3. How to evaluate an existing component and/or user journey, to identify, triage and address issues, using various tools and resources, including ready-made step-by-step instructions for common Example Analysis Scenarios.
  4. How to Find Help and Report Issues that are encountered during this process.

In addition, within relevant contexts, it includes prompts and pathways for you to contribute your own use cases, provide feedback and seek even more guidance.

Clone this wiki locally