Browser fingerprinting overview

[jonaharagon]

Changes proposed in this PR:

• Add fingerprinting overview page

Please do not add any suggestions or reviews correcting grammar or wording until this PR is undrafted, it will only waste time. This draft PR is only open to accept suggestions about what information needs to be incorporated on this page.

• I have disclosed any relevant conflicts of interest in my post.
• I agree to grant Privacy Guides a perpetual, worldwide, non-exclusive, transferable, royalty-free, irrevocable license with the right to sublicense such rights through multiple tiers of sublicensees, to reproduce, modify, display, perform, relicense, and distribute my contribution as part of this project.
• I am the sole author of this work.
• I agree to the Community Code of Conduct.

[netlify]

✅ Deploy Preview for privacyguides ready!

Name	Link
🔨 Latest commit	70077b7
🔍 Latest deploy log	https://app.netlify.com/sites/privacyguides/deploys/64343c9d272a7e0008faa40d
😎 Deploy Preview	https://deploy-preview-2119--privacyguides.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[ghost]

I like this from the Arkenfox wiki, maybe could incorporate it somewhere:

So if a fingerprinting script should run, it would need to be universal or widespread (i.e it uses the exact same canvas, audio and webgl tests among others - most aren't), shared by a data broker (most aren't), not be naive (most are) and not be just first party or used solely for bot detection and fraud prevention (most probably are) 1.

[jermanuts]

Somehow you managed not to mention javascript at all? lol. Most of of tracking is done by js but not all of it. Also, extensions deserve more representation than just being a quick notes referenced in footnotes as mentioned here. Someone demonstrated what a malicious extension could do https://mattfrisbie.substack.com/p/spy-chrome-extension on v3 which is supposed to be more secure than v2

[jonaharagon]

Somehow you managed not to mention javascript at all? lol.

This is not constructive.

In fact, since the bold warning in the OP was apparently not enough to avoid these comments, I'm locking this thread to contributors until the article is completed.

Also, extensions deserve more representation than just being a quick notes referenced in footnotes as mentioned here. Someone demonstrated what a malicious extension could do https://mattfrisbie.substack.com/p/spy-chrome-extension on v3 which is supposed to be more secure than v2

This has nothing to do with browser fingerprinting, at a quick glance.

---

Feedback and information about browser fingerprinting can be submitted to our forum: https://discuss.privacyguides.net/t/browser-fingerprinting-tracking-overview/12250