Fenced Frames: Securely embed content onto a page without sharing cross-site data.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.This data must be read in a secure environment to prevent leakage. Shared Storage: Create a general-purpose API which allows sites to store and access unpartitioned cross-site data.First-Party Sets: Allow related domain names owned by the same entity to declare themselves as belonging to the same first party.CHIPS: Allow developers to opt-in a cookie to partitioned storage, with a separate cookie jar per top-level site.# Strengthen cross-site privacy boundaries It's critical we receive feedback from developers and industry leaders to ensure we create durable web features with broad utility and robust privacy protections for users. Proposals have a lifecycle with up to three phases before becoming web standards: discussion, testing, and scaled adoption. These proposals cover a wide variety of use cases and requirements. # What are the Privacy Sandbox proposals?Ĭhrome and other ecosystem stakeholders have offered more than 30 proposals to date, which can be found in the public resources of W3C groups. The Privacy Sandbox's vision of the future has browsers providing specific tools to satisfy specific use cases, while preserving user privacy. This is a shift in direction for browsers. 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. The Privacy Sandbox APIs require web browsers to take on a new role.
0 kommentar(er)
