![]() While blocking third-party storage provides strong privacy protections, those protections come with the significant risk of breaking sites that expect third-party storage to be available. To date Brave has had the most aggressive policy of a popular, general use browser namely, disabling third-party storage all together. And for nearly as long, privacy focused browsers have different techniques to protect users against tracking that relies on third-party storage. This tracking and re-identification occurs generally without your consent, or even knowledge. Most tracking on the Web, for most of the Web’s history, has relied on “third-party storage”, or the saving and retransmitting of unique identifiers to sites other than the one you intend to visit. Background: Brave’s Current Third-Party Storage Protections ![]() ![]() “Ephemeral site storage” can be enabled in Brave Nightly now, by visiting brave://flags and setting “Enable Ephemeral Storage” to “Enabled.” The feature will be enabled by default on our Desktop and Android browsers shortly, once the system has been sufficiently tested in Nightly. This post presents “ephemeral site storage”, a new strategy for managing third-party storage in Brave, designed to improve Web compatibility, while maintaining the same level of privacy protection. Blocking third-party storage protects Brave users from the most common forms of tracking, but can also break sites. Since our first release, Brave has by default blocked all third-party application storage (e.g., cookies, localStorage, indexedDB). This post describes work done by Principal Engineer Brian Johnson, Senior Software Engineer Ivan Efremov, and Senior Privacy Researcher Peter Snyder.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |