Fingerprinting prevention

Hi, I think Brave should deals better with fingerprinting. Especially:

  • ClientRects -> (it should be random like in Bromite),
  • Audio -> (cc_output[:30] hash and hybrid_output[:30] hash),
  • Content language -> (It should be possible to send only en-US and en),
  • Font fingerprinting,
  • Tab name,
  • Browser type.

Sources:

2 Likes

cc @yan @toml on this.

Thanks for the tag, I’ll take a look.

1 Like

@toml It’s been two years now and no changes? Client Rects and Font Fingerprinting still allow for easy user tracking with other additional parameters. It can be checked here http://f.vision/

So what’s the status update with this? Client Rects not being anonymized?