All the code is maintained by the same team (thats us) and everything gets updated at the same time.
Meanwhile, Brave comes with all the necessary privacy/security features out of the box in one package. So each extension installed has the potential to be an attack vector. Not that I’m saying that these (or any) extensions are inherently not worthy of your trust, but even companies/devs with the best of intentions make mistakes, get hacked, etc. Each of these extensions are updated and maintained by separate developers, which means it’s up to each of those developers to ensure that their extension doesn’t have any security vulnerabilities and/or that those extensions aren’t doing anything shady with your data. The issue with installing a bunch of extensions in the name of privacy (or just in general really) – esp in Brave – is that you are inheriting whatever risks may be associated with those extensions since they’re managed by third parties.įor example, let’s say you install Ghostery, HTTPSE and maybe Privacy Badger extensions in your browser. It certainly isn’t a “myth” – typically privacy extensions do what they say they do (at least those that are relatively reputable) and some of them may have additional functionality not included by default in Brave (although to be fair, this is relatively rare, as Brave + Shields combine and implement the best privacy features out of the box). on Chrome? Or, do you think securing privacy using Chrome extensions is a myth?
How much privacy can be secured using extensions such as Ghostery, HTTPS everywhere, etc. With all that said, if you want to ensure privacy when using Google search, I would recommend doing so from a private browsing window. This behavior may change/come to be in the future, but at this time cookie data does get passed through when searching Google. Were we to intercept/make a call without passing through cookies, it would require an additional Chromium deviation and, further, would come with the cost of doing the work to maintain that change. You can see on our Github how we deviate from Chrome/chromium code (features-we-disable-or-remove) With respect to search, cookie data is still sent along with the search request when using Google search. Note that when not using Google services, the Allow Google login buttons on third-party sites option should be disabled, or some cookies/requests may be allowed.Brave prevents Google from tracking you when you’re not using Google systems/services, and removes some of the ways Google tracks you when using their systems/services to the best of our abilities.When you use Chrome, Google uses a litany of methods to track you, both when using Google systems/services as well as while you’re not.
0 kommentar(er)
