Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://web.dev/articles/digging-into-the-privacy-sandbox below:

What is the Privacy Sandbox?

Stay organized with collections Save and categorize content based on your preferences.

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 has two core aims:

• Provide alternative solutions for browsing without third-party cookies.
• Reduce cross-site and cross-app tracking while helping to keep online content and services free for all.

The Privacy Sandbox APIs require web browsers to take on a new role. Rather than working with limited tools and protections, the APIs allow a user's browser to act on the user's behalf—locally, on their device—to protect the user's identifying information as they navigate the web. This is a shift in direction for browsers.

The Privacy Sandbox's vision of the future has browsers providing specific tools to satisfy specific use cases, while preserving user privacy.

Chrome and other ecosystem stakeholders have offered more than 30 proposals to date, which can be found in the public resources of W3C groups. These proposals cover a wide variety of use cases and requirements.

Proposals have a lifecycle with up to three phases before becoming web standards: discussion, testing, and scaled adoption. It's critical that we receive feedback from developers and industry leaders to ensure we create durable web features with broad utility and robust privacy protections for users. Read more about the proposal lifecycle.

The following section lists key proposals.

• CHIPS: Allow developers to opt-in a cookie to partitioned storage, with a separate cookie jar per top-level site.
• Related Website Sets: Allow related domain names owned by the same entity to declare themselves as belonging to the same first party.
• Shared Storage: Create a general-purpose API which allows sites to store and access unpartitioned cross-site data. This data must be read in a secure environment to prevent leakage.
• Storage Partitioning: Enable all forms of user agent state, such as localStorage or cookies, to be double-keyed: by the top-level site as well as the origin of the resource being loaded, rather than a single origin or site.
• Fenced Frames: Securely embed content onto a page without sharing cross-site data.
• Network State Partitioning: Prevent browser network resources being shared across first-party contexts, by ensuring that every request has a network partition key that must match in order for resources to be reused.
• Federated Credential Management (FedCM): Support federated identity without sharing the user's email address or other identifying information with a third-party service or website, unless the user explicitly agrees to do so.

• Topics API: Enable interest-based advertising without use of third-party cookies or tracking user behavior across sites.
• Protected Audience API: Ad selection to serve remarketing and custom audience use cases, designed so that it cannot be used by third parties to track user browsing behavior across sites. The Protected Audience API is the first experiment to be implemented in Chromium from the TURTLEDOVE family of proposals.

• Attribution Reporting: Correlate ad clicks or ad views with conversions. Ad techs can generate event-level or summary reports.
• Private Aggregation API: Generate noisy summary reports with cross-site data.

• User-Agent reduction and User-Agent Client Hints: Limit passively shared browser data to reduce the volume of sensitive information which leads to fingerprinting. Client Hints allow developers to actively request only the information they need about the user's device or conditions.
• IP Protection: Improve user privacy by protecting their IP address from being used for tracking.
• Bounce tracking mitigations: A proposal to reduce or eliminate the ability of bounce tracking to recognize people across contexts.
• Privacy Budget: Limit the amount of individual user data exposed to sites to prevent covert tracking.

• Private State Tokens: Allow websites to convey a limited amount of information from one browsing context to another (for example, across sites) to help combat fraud, without passive tracking.

• GitHub: read the explainers on GitHub and raise questions or comments in the Issues tab for each.
• W3C: Use cases can be discussed and industry feedback shared in the W3C Improving Web Advertising Business Group, the Privacy Community Group, and the Web Incubator Community Group.
• Developer support: Ask questions and join discussions on the Privacy Sandbox Developer Support repo.

• Digging into the Privacy Sandbox
• A Potential Privacy Model for the Web sets out the core principles underlying the APIs.
• Chromium's overview of the Privacy Sandbox
• Google AI Blog: Federated Learning: Collaborative Machine Learning without Centralized Training Data
• The future of third-party cookies

You can follow the monthly updates to the Privacy Sandbox in our blog.

The Privacy Sandbox timeline shows the current status and schedule for proposals.

These high-level resources will provide signposts to changes across the project, but for individual proposals where you want to follow in detail you should:

• Watch or Star proposal repos on GitHub to get notification of new issues and updates: the Privacy Sandbox status page provides a link to the repository for each proposal
• Join the associated W3C group for regular meetings discussing the proposal detail
• Star the associated entry on Chrome Platform Status for email updates on Chrome implementation changes.

• Participate in incubation, testing and refinement of the APIs: How to participate in the Privacy Sandbox initiative
• As a developer, join discussions or ask questions: Privacy Sandbox Developer Support

For questions about specific APIs, you can file an issue on the GitHub repository for an API Explainer.

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-04-24 UTC.

[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-04-24 UTC."],[],[]]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.3