Privacy Updates
ARCHIVED 2021-12-04, DATE APPROXIMATE · VERSION 20211204_rev01 · COMPARED WITH 20211114_rev01
Full text changes — 20211114_rev01 to 20211204_rev01
COLOUR MARKS THE SEVERITY OF A FLAGGED CLAUSE · + AND − MARK ADDED AND REMOVED
| 1 | ## [Brave and UC San Diego Announce SugarCoat, A New Solution to Strengthen the Protection of Web Users' Privacy While Not Breaking Websites](https://brave.com/privacy-updates/12-sugarcoat/) | |
| 2 | ||
| 3 | Post #12 | Nov 18, 2021 | |
| 4 | ||
| 5 | Brave is pleased to announce SugarCoat, the result of a year-long research collaboration with University of California San Diego to create a new system to improve Web privacy without sacrificing compatibility at Web scale. | |
| 6 | ||
| 1 | 7 | ## [Debouncing](https://brave.com/privacy-updates/11-debouncing/) |
| 2 | 8 | |
| 9 | Post #11 | Oct 14, 2021 | |
| 10 | ||
| 3 | 11 | Brave is releasing additional protections against certain forms of bounce tracking. We call these new protections "debouncing". As of desktop version 1.32, Brave will protect users against bounce tracking by recognizing when the user is about to visit a known tracking domain, skipping visiting the tracking site all together, and instead directly navigating the user to the intended destination. |
| 4 | 12 | |
| 5 | 13 | ## [Custom Filter List Subscriptions](https://brave.com/privacy-updates/10-custom-filter-lists/) |
| 6 | 14 | |
| 15 | Post #10 | Sep 21, 2021 | |
| 16 | ||
| 7 | 17 | Starting in version 1.31, Brave will support custom filter list subscriptions, allowing users to further control how unwanted network requests and in-page elements are blocked in Brave. This work is part of Brave's goal of providing best-of-breed content filtering tools, and keeping people in control of their Web browsing. |
| 8 | 18 | |
| 9 | 19 | ## [Improving Privacy By Improving Web Compatibility](https://brave.com/privacy-updates/9-web-compat-blocking/) |
| 10 | 20 | |
| 21 | Post #9 | Sep 1, 2021 | |
| 22 | ||
| 11 | 23 | Brave is disabling filter list blocking for first-party subresources to improve privacy for typical Brave users. Advanced users still have the ability to deploy more aggressive privacy protections, even those that might break sites. |
| 12 | 24 | |
| 13 | 25 | ## [Grab Bag 2: Permission Lifetimes, Bounce Tracking, and Fingerprinting Protections](https://brave.com/privacy-updates/8-grab-bag-2/) |
| 14 | 26 | |
| 27 | Post #8 | Jul 21, 2021 | |
| 28 | ||
| 15 | 29 | Brave users can now choose to give sites temporary access to permission-protected capabilities to better protect their privacy. Common examples of permission-protected browser capabilities include web cameras, microphones, location information, and motion sensors, among others. |
| 16 | 30 | |
| 17 | 31 | ## [Ephemeral Third-party Site Storage](https://brave.com/privacy-updates/7-ephemeral-storage/) |
| 18 | 32 | |
| 33 | Post #7 | Feb 1, 2021 | |
| 34 | ||
| 19 | 35 | 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. |
| 20 | 36 | |
| 21 | 37 | ## [Fighting CNAME Trickery](https://brave.com/privacy-updates/6-cname-trickery/) |
| 22 | 38 | |
| 39 | Post #6 | Jul 20, 2020 | |
| 40 | ||
| 23 | 41 | Trackers are constantly working on new techniques for evading privacy tools, and keep deploying new ways to evade privacy-protecting tools like the Brave browser. This post discusses a recent technique trackers use, CNAME cloaking, and a new feature in Brave that keeps Brave users protected. |
| 24 | 42 | |
| 25 | 43 | ## [Grab Bag: Query Stripping, Referrer Policy, and Reporting API](https://brave.com/privacy-updates/5-grab-bag/) |
| 26 | 44 | |
| 45 | Post #5 | Jul 20, 2020 | |
| 46 | ||
| 27 | 47 | In order to stay one step ahead of online trackers, Brave regularly releases new privacy features and improvements. This post discusses three recent changes in Brave that each help make the web a more privacy, and person, respecting platform. |
| 28 | 48 | |
| 29 | 49 | ## [Fingerprinting Defenses 2.0](https://brave.com/privacy-updates/4-fingerprinting-defenses-2.0/) |
| 30 | 50 | |
| 51 | Post #4 | May 18, 2020 | |
| 52 | ||
| 31 | 53 | Brave's goal is to both be the best browser for protecting your privacy, and the best browser for day-to-day, full-featured Web use. This post describes new privacy features being developed in Brave to better protect user privacy, without breaking privacy-respecting, user-serving websites. |
| 32 | 54 | |
| 33 | 55 | ## [Fingerprint Randomization](https://brave.com/privacy-updates/3-fingerprint-randomization/) |
| 34 | 56 | |
| 57 | Post #3 | Mar 5, 2020 | |
| 58 | ||
| 35 | 59 | Brave now protects users from being fingerprinted by making them appear subtly different to each website. Browser fingerprinting protection is available today in our Nightly version. These new protections both provide the strongest fingerprinting protections of any popular browser, and work without introducing bothersome permission prompts or breaking websites. |
| 36 | 60 | |
| 37 | 61 | ## [Third-Party Cosmetic Filtering](https://brave.com/privacy-updates/2-third-party-cosmetic-filtering/) |
| 38 | 62 | |
| 63 | Post #2 | Feb 20, 2020 | |
| 64 | ||
| 39 | 65 | Brave is releasing a new system for hiding unwanted, privacy harming page elements. These include empty page space caused by blocking trackers, and third-party ads that cannot be blocked at the network layer. |
| 40 | 66 | |
| 41 | 67 | ## [Web Resource Replacements](https://brave.com/privacy-updates/1-web-resource-replacements/) |
| 42 | 68 | |
| 69 | Post #1 | Jan 23, 2020 | |
| 70 | ||
| 43 | 71 | Problem: Blocking Trackers Sometimes Breaks Sites. One of many ways Brave protects your privacy on the Web is by blocking requests to trackers. By blocking these requests, Brave prevents you from being followed around the Web, and from ad companies, data brokers, and other privacy-harming parties from recording your online activity. |