Brave Browser is built to protect users’ privacy by blocking online trackers. The browser protects users from all kinds of tracking including IP tracking, state-based tracking as well as fingerprinting tracking. Browsers such as Chrome have enhanced their fingerprinting protection. However Brave has its doubts regarding these dynamic approaches compared to Web privacy.
Browser fingerprinting involves tracking people without consent and this is a trend that is increasingly becoming common. Brave has different approaches to protecting users from fingerprinting.
Removal of functionality
This is the easiest way of dealing with fingerprinting. To deal with harmful functionality it is ideal to do away with the functionality. It can be in the form of altering the functionality so that it always returns the same value. Although the approach seems to efficient it nonetheless risks breaking sites.
Determining access through trust
Sometimes browsers can limit access to functionality by focusing on sites one trusts can be a good way of preventing against tracking. A user can allow and block other sites from accessing the functionality. Browsers can easily identify sites to trusts by having first-party sites as the most trusted and third party sites as the least trusted.
Adding randomness to the semi-identifying functionality
Alternatively one can incorporate randomness to the outputs of the fingerprinting functionality. Sometimes the browser can make regular User-Agent string changes which means that the value will vary every time the site reads it thus minimizing identification. The approach is popular because it uses a range of fingerprinting libraries. Usually, the libraries create identifiers by blending several values and therefore randomizing one could alter the whole identifier.
Restricting access via threshold
This is another way of preventing fingerprinting. It entails limiting access to the identifying functionality depending on the previous behavior of the browser. It is user-specific and it employs general heuristic to make access decisions and not on a user-by-user basis.
Chrome uses this approach in the “Privacy Budget” where websites get access to identifying information but they are blocked once they reach an “identifiably” threshold. Beyond the threshold, the site cannot access any additional related functionality.