<p>Brave Browser is a Chromium fork with many interesting features not found elsewhere, such as built-in Adblock and other extensions, fingerprinting protection, a cleaner Preferences menu compared to other Chrome forks, and the (opt-in) ability to automatically support (pay) the websites you visit. The developers describe it as <i>"A browser with your interests at heart."</i><sup><ahref="#one">[1]</a></sup> with the built-in privacy protections.</p>
<p>Brave is self updating software, uses <ahref="../articles/google.html">Google</a> as the default search engine, has built-in analytics, and even has an opt out rss-like news feed similar to Firefox's pocket feature. These features aren't the first things that come to mind when I imagine a privacy oriented browser.</p>
<h3>Whitelisting spyware from Facebook and Twitter</h3>
<p>On its website, Brave claims that <i>"Brave fights malware and prevents tracking, keeping your information safe and secure. It’s our top priority."</i><sup><ahref="#six">[6]</a></sup>. Yet despite this claim, Brave actually disables its tracking protections for Facebook and Twitter's scripts that allow them to track people across the web.<sup><ahref="#five">[5]</a></sup> Brave has been actively downplaying the role that JavaScript plays when tracking someone.</p>
<br></br>
<p><i>"Loading a script from an edge-cache does not track a user without third-party cookies or equivalent browser-local storage, which Brave always blocks and always will block. In other words, sending requests and receiving responses without cookies or other means of identifying users does not necessarily create a tracking threat."</i><sup><ahref="#seven">[7]</a></sup></p>
<br></br>
<p>This couldn't be more far from the truth. Just because a website isn't able to store cookies, doesn't mean it can't uniquely identify you. Using JavaScript from Facebook and Twitter would be more than enough to track you and blocking cookies alone isn't going to stop that. Just as a quick point of reference to what information JavaScript can scrape, you might want to visit <ahref="https://coveryourtracks.eff.org">this</a>.</p>
<p>They later on added an option to the extension to disable all of the JavaScript, but this new feature seems to be nothing more than the JavaScript switch found in <ahref="chrome://settings/content/javascript">vanilla Chromium</a>.</p>
<p>A quick note on the whitelisting trackers: This specific point on whitelisting trackers isn't making the case of Brave being spyware as much as showing Brave's privacy features being snake oil.</p>
<h3>Auto-updates</h3>
<p>Brave will check for updates every time you run it, and you can't turn it off from the browser. Athough, it's on Brave's low priority list to add an option to do so<sup><ahref="#two">[2]</a></sup>. I say low priority because it's been over a year and it hasn't been implemented yet.</p>
<p>A special note is that on most (all?) GNU/Linux distributions, the automatic updates are only for the extensions.</p>
<h3>Anti-privacy search engine by default</h3>
<p><ahref="../articles/google.html">Google</a> is the default search engine of Brave. For a browser that claims to be privacy oriented, this is a red flag. They at least make it easy for you to change the default search engine on the first run.</p>
<h3>Brave has built-in telemetry</h3>
<p>While running, Brave will make lots of requests to the domain <code>p3a.brave.com</code> as telemetry. They claim they store the collected data for several days<sup><ahref="#eight">[8]</a></sup>. Telemetry is the last thing that comes to mind when I imagine a privacy oriented browser.</p>
<h3>Brave Today</h3>
<p>Brave now has new feature similar to Firefox's pocket called Brave Today. If you don't know what Firefox Pocket is, it's basically an rss-like news feed is shown in every blank tab. This feature Brave has is sadly an opt-out rather than an opt-in and sends lots of requests to Brave's servers.</p>
<h3>SafeBrowsing</h3>
<p>Brave uses SafeBrowsing. It's a feature that tries to "protect" the user from potentially unsafe websites. However, it sends requests to fetch the information required to do so. Judging by some of the information in <code>Miscellaneous requests</code>, I wouldn't put it past Brave to use Google's SafeBrowsing implementation rather than their own.</p>
<h3>Brave Rewards</h3>
<p>Brave has a rewards program. You can find more information about it here<sup><ahref="#three">[3]</a></sup>. At first glance it looks like the rewards program is an opt in, but the browser makes connections to these domains regardless if you sign up or not:</p>
<divclass="center">
<p><code>rewards.brave.com</code></p>
<p><code>api.rewards.brave.com</code></p>
<p><code>grant.rewards.brave.com</code></p>
</div>
<h3>Miscellaneous requests</h3>
<p>Brave on first run sends a request to fetch the library used for checking spelling errors:</p>
<p>Brave on first run sends a request to <code>variations.brave.com</code>, which if I had to give a guess, has to do with some way to verify affiliates:</p>
<p>Right after the request to <code>variations.brave.com</code> is made, Brave fetches the list of affiliates through <code>laptop-updates.brave.com</code><sup><ahref="#four">[4]</a></sup>:</p>
<p>Brave made a request to <code>static1.brave.com</code>, which looks like it's used to fetch plugin information? When I entered the url into the browser to explore, it redirected to Google's error 404 page<sup><ahref="#nine">[9]</a></sup>. This seems kind of unsettling to me that one of Brave's domains would do this:</p>
