jaeshot.blogg.se

Privacy Sandbox achieves its (modest) privacy improvements in ways that restrict, break or weaken other more robust privacy tools. Google’s Privacy Sandbox proposal improves privacy only when your baseline for comparison is Google Chrome, the browser with the unambiguously worst privacy protections of any major browser.īut while Chrome is terrible for privacy, it’s at least designed to work with a Web where other browsers and privacy tools can deliver very high levels of privacy. The Web community should similarly doubt Google’s privacy promises (and intentions) after Google has spent decades profiting from (and entrenching) the Web’s worst privacy violations. It’s prudent to doubt someone selling antidotes after they’ve gotten rich by poisoning wells.

We present our concerns with Privacy Sandbox not only as a browser maker, but as individuals worried that Privacy Sandbox threatens what makes the Web special and unique: that users can modify their Web experience to best suit their needs and wants, and that features in the Web are designed first and foremost to benefit users. This post presents concerns with Privacy Sandbox that we have not seen discussed elsewhere, which we worry may go unconsidered in the CMA’s analysis.

In practice, we expect that Privacy Sandbox will harm Web privacy, and further cement Google’s control over the Web. Google presents Privacy Sandbox as a system for protecting privacy and openness on the Web. This misses the bigger picture: how Privacy Sandbox will interact with other Google proposals, and how radical and harmful it will be in practice.

Brave appreciates the CMA’s critical work, and applauds the CMA’s efforts to prevent Google’s long overdue privacy protections from harming the open Web.īut the CMA (along with other regulators) seem to be evaluating Google’s Privacy Sandbox as an isolated, independent set of features. This post was written by Director of Privacy Peter Snyder.īrave recently submitted concerns and comments to the UK Competition and Markets Authority (CMA) as part of the CMA’s effort to secure commitments from Google regarding Google’s Privacy Sandbox plans. This is the sixth in a series of blog posts discussing proposed Web standards.