MaskWright

2026-06-02 · Avery Chen · 870 words

Fingerprint spoofing versus tracking prevention

Spoofing paints a story. Tracking prevention reduces signal. Those are different jobs. This note separates them so a privacy mode is not sold as a profile.

Fingerprint spoofing versus tracking prevention 1

One thing worth flagging: a privacy mode that blocks canvas, strips fonts, and partitions storage is not a profile. A profile that presents a coherent Windows desktop is not a tracker blocker. Spoofing paints a stable story. Tracking prevention reduces signal. Mixing the two produces a collage.

If you do not have a right to the account, neither job creates that right. This split lives under Browser fingerprinting because 2023 tracking-prevention pages keep getting sold as antidetect.

Two answers to "the page can see me"

What browser fingerprinting measures is a bundle of engine answers. Once you accept that the page can ask, you have two honest strategies.

StrategyGoalTypical toolsFailure mode
Tracking preventionSend less dataBrave, strict Firefox, blockersYou look like a privacy browser
Spoofing (operator sense)Stable, coherent desktop per folderLocal profile + seedCollage if APIs are also stripped
Mix of bothConfusedCanvas blocked plus workstation GPUTwo products in one tab

Reduce the answers. Disable the API. Return an empty font list. Block the third-party cookie. Decline Topics. That is tracking prevention. The goal is less data, even if the leftover shape looks like a privacy browser.

Replace the answers with a stable, coherent story. Same seed after quit. GPU family that matches the UA. Clock that follows the exit. Separate folder per authorized account. That is spoofing in the operator sense: paint, then stay painted. The goal is isolation, not silence.

What tracking prevention is good at

It is good at shrinking digital footprint that was stored as third-party state. After third-party cookies CHIPS and Topics are the industry's replacement language. A prevention browser can refuse those callers.

It is good at making you look like other prevention users. Shared empty states are a crowd. That crowd is still a crowd of privacy browsers. Sites that care about "real desktop Chrome" will notice the missing APIs.

It is bad at splitting two authorized ads accounts on one PC. Both profiles, if they use the same prevention browser profile, still share cookies. Prevention is not a folder.

It is bad at hiding the desk from cross-browser joining. The exit IP and the NIC remain. A MAC address is not a browser fingerprint, and prevention does not rewrite it either. Device fingerprinting still sits under the tab.

What spoofing is good at, in this product

On Windows, a headed MaskWright profile can override a lot of what JavaScript sees. UA and Client Hints. Timezone, locale, languages, and geolocation aligned to an exit lookup. Screen, cores, memory. WebGL parameters and renderer strings. WebGPU adapter info. Canvas with OS-biased stable noise. Font probes. Client rects. Seeded audio. WebRTC modes. Media device IDs. Plugins, battery, network information, voices, permission state, bluetooth presence, window.chrome, webdriver false.

The point of that list is one desktop person per folder, repeated across launches. It is not a stripped API surface.

When the custom Chromium 131 core is present, some deeper tells can move with the binary. When it is missing, we fall back to system Chrome or Edge with CDP and inject only. I will not market the fallback as a privacy browser, and I will not market it as a patched core.

We do not ship tracker-blocking as the product. Dashboard ads and an ads JSON feed exist. That is the opposite of a prevention pitch. Honesty about funding is part of the fork.

A 2023 page that says tracking prevention is fingerprint spoofing skipped the stability requirement. Noise that changes every reload is not a person. Empty APIs are not a Windows workstation.

A feature list that says "we block fingerprinting" on an antidetect tool skipped the isolation requirement. Blocking the measurement can make every profile look like the same privacy user. That joins the profiles.

How I want you to choose

If your job is to send less data to random callers, use tracking prevention, or use the site's official privacy controls.

If your job is to keep authorized accounts from sharing one engine identity on a Windows PC, use a local profile with a seed that stays put.

Do not buy a privacy mode and call it a profile. Do not buy a profile and call it a tracker blocker. The words are doing different work.

Authorized work wants the second shape: different folders, different cookies, each folder a boring, repeatable desktop.

FAQ

Can I turn on strict tracking prevention inside a MaskWright profile? You can install add-ons, but stripping canvas while claiming a workstation GPU is the collage. I keep work profiles looking like ordinary desktop Chrome or Firefox.

Does spoofing hide me from ads? No. That is not the job. Isolation keeps two logins from sharing one folder. It does not retire first-party ads accounts you already have.

Which one should I use for personal browsing? Prevention, or a hardened daily driver. Keep brand logins in named local profiles.

I check the profile the way I would check any other tool: does the story stay put, and does it agree with itself. I do not score a privacy browser on whether it "looks like a real person." That is the wrong rubric.

Related notes