Fingerprint Defender od Digital Fracture

Fingerprint Defender v2.1.2 - Blend in, don't stand out

A privacy extension that fights browser fingerprinting with noise randomization instead of static spoofing.

Why this approach

Most fingerprint "spoofers" fake your browser, GPU and screen. The problem: those fake values do not match any real browser, so you become the only person with that exact fake setup - easier to track, not harder. Fingerprint Defender does the opposite: randomize the things used to track you, and let your real, common values through so you look like everyone else.

Noise - breaks cross-site tracking

• Canvas - randomizes the canvas image pixels.
• Audio - randomizes the rendered AudioContext output (offline and real-time paths).
• Client Rects - adds tiny noise to element position and size measurements.

Block - leak prevention

• WebRTC - stops WebRTC leaking your local or public IP. Turn off for video calls.
• Battery - blocks the Battery Status API.

Spoof - one common value to blend in

• Screen - reports 1920x1080, the most common resolution.

Pass-through - real, common values left alone (on purpose)

Changing these would make you more unique, not less:

• WebGL / GPU - your real GPU; faking it creates impossible combinations.
• Browser / User-Agent - real, so you blend with other Firefox and Windows users.
• Timezone - real, so calendars and scheduling work.
• Fonts - real; the font list is the same on every site, so it cannot link you.
• Plugins - returned empty to reduce surface.

Honest limits - what this does NOT do

No extension makes you invisible:

• Cookies and logins are not touched. Turn on Firefox Enhanced Tracking Protection (Strict).
• Your IP address is not hidden, apart from the WebRTC leak. Use a VPN or Tor.
• Logged-in sites know who you are regardless of fingerprinting.
• Static device traits (sample rate, CPU cores, exact GPU) cannot be safely faked. Some testers build an "audio hash" from these - it will not change, and that is expected. It is the same for many users, so it does not single you out.
• AudioWorklet audio capture and canvas text-metrics are not covered.

How to test it properly

Reload a reputable tester a couple of times. The Canvas and Audio hashes should change each time - that is it working. WebGL, browser, timezone and fonts staying the same is intentional. The most reliable tester is CreepJS: it does not cache, it shows the Canvas and Audio codes changing on every reload, and it flags the canvas as "rgba noise". Note that browserleaks.com caches the canvas value it shows on screen, so it can look unchanged on a normal refresh even when the real canvas is changing every load - open it in a fresh tab, or just use CreepJS. Also good: Cover Your Tracks by EFF and amiunique.org.

Privacy

No data collection. No tracking. No external connections. Everything runs locally in your browser.

Developed by Digital Fracture