Fidelity.com is able to identify that i’m visiting from a linux machine.
This is happening despite fingerprinting being enabled in the brave shield.
Check the attached screenshot.
Brave describes its fingerprinting protection as a combination of blocking/removing/modifying browser APIs and randomizing values returned by APIs. The objective is to make it difficult for a site to construct a stable, unique “browser fingerprint.”
A fingerprint can be assembled from things such as:
graphics/GPU characteristics;
WebGL/WebGPU information;
Canvas rendering;
audio processing;
installed fonts;
browser language;
screen/device characteristics;
certain media-device information;
WebRTC-related information;
various other browser APIs.
Brave doesn’t simply turn all of those off. Instead, it may block some, remove information from others, and “farble” (randomize) still others so that the combination isn’t a reliable identifier.
And Brave has continued adding protections. For example, in August 2026, Brave announced additional GPU fingerprinting defenses: WebGL vendor/renderer information is replaced with a generic value, WebGPU adapter information is emptied, and the WebGL extension list is randomized.
The OS is currently conveyed in ways that are deeply embedded in normal Web operation.
The most obvious example is the User-Agent. A web server can receive an HTTP request containing information about the browser/platform, and historically the User Agent has included the operating system. Brave itself acknowledges that a User Agent can declare the OS and device type.
Brave does modify this information. For example, Brave deliberately presents itself as Chrome rather than identifying itself as Brave, and it has generalized/nonessential User Agent information.
But Brave doesn’t simply say:
“Never tell any website what operating system this computer uses.”
That would break or complicate a surprising amount of the Web.
Because I was instructed more than 60 years ago, to make an effort to credit sources … I included “ChatGPT” that confirmed the info … that I would have otherwise provided as a response to your concern.
Also, I try to provide more info in a variety of responses - because other members of this forum will search for answers.
Your particular issue was interesting because of some past reports some years ago, re Fidelity.com and Fingerprinting. Some users were unable to sign in at that website - when Fingerprinting was blocked. But later on, Brave made some adjustments so that Fingerprinting being blocked, would no longer block/inhibit(?) WebGL ← that websites required to function. (Something like that.)
