How the browser fingerprint works

A browser fingerprint is the set of traits a site uses to recognize a device even without cookies: how the graphics stack draws an image, quirks of the audio system, CPU core count, screen size, language and timezone.

If two accounts sign in with the same fingerprint, anti-fraud systems see one person. That’s why every Accovod profile has its own fingerprint — and the fingerprint isn’t the only thing that keeps profiles apart.

Why profiles don’t get linked

Sites link accounts by shared traces: the same cookies, IP or fingerprint. In Accovod each profile has its own of everything.

Separate storage

Cookies, LocalStorage, IndexedDB and cache are separate for every profile. A profile can’t see its neighbor’s data — like two different computers.

Its own IP

All of a profile’s traffic goes through its proxy. WebRTC doesn’t reveal your real IP around the proxy.

A unique fingerprint

The Accovod service generates the values when a profile is created. Two profiles are two different devices to a site.

Consistent data

User-Agent, browser properties, language and timezone don’t contradict each other — anti-fraud sees one coherent device, not a set of random values.

Passes popular checks

Accovod profiles pass BrowserScan, Pixelscan, BrowserLeaks, Whoer and other well-known checkers: no signs of spoofing, no IP leaks through WebRTC, no mismatches between parameters.

You can check it yourself in a couple of minutes:

1. Open a profile with a proxy set up.
2. Go to any of the services above.
3. Make sure the IP and country come from the proxy, and the timezone and language match that country.
4. Open the same service in a second profile: the fingerprint should differ.

If a checker finds a mismatch

It’s almost always the proxy, not the fingerprint: the profile’s timezone or language doesn’t match the IP’s country, or the proxy is on a blacklist. Check it with the check mark next to the proxy address in the profile form — see Checking a proxy.

What is spoofed

Profiles on macOS run on WebKit, the engine behind Safari. On Windows they run on Chrome or Edge — you pick the engine when you create a profile.

Parameter	macOS	Windows
User-Agent	Safari, Chrome or Firefox	Chrome or Edge
Browser properties	Match the chosen browser: a Firefox profile gets its own vendor, oscpu, productSub	navigator.userAgentData (Client Hints) and navigator.platform match the User-Agent
Language	navigator.language, Intl formats and the Accept-Language header the server sees before the page loads (macOS 15.4+)	Page language, date and number formats
Timezone	The profile’s timezone, not your computer’s	The profile’s timezone, not your computer’s
Audio	As in a real browser: Safari 26+ profiles get WebKit noise, as in Safari · More Privacy	Unique noise in the audio signal
CPU and memory	For profiles with a Windows User-Agent — core count, plus memory for Chrome. With a macOS User-Agent — as on a real Mac	Unique core count per profile
WebRTC	Direct network access is blocked	Network access only through the proxy
Canvas	Unique noise · More Privacy. Safari 26+ profiles: WebKit noise, as in Safari, different for every tab and site	Unique noise · More Privacy
WebGL	Real: WebKit itself hides the GPU model	Unique noise · More Privacy
Screen	As in a real browser: Safari 26+ profiles report the window size instead of the monitor, as in Safari · More Privacy	Real

Fonts. On macOS, sites see only the fonts that come with the system — as in Safari. Fonts you installed yourself don’t give away your Mac or link profiles together.

The built-in protection for Safari 26+ profiles works on a Mac with Safari 18.4 or later — macOS 15.4 and later already include it.

You can’t view or edit the values themselves: that protects you from accidental edits that make a profile stand out. The short Fingerprint ID in the profile form is the fingerprint in compressed form: different IDs mean different devices to a site.

Protection modes

Pick the mode in settings → Fingerprint Protect; it applies to every profile. The modes are the same on macOS and Windows.

	V3 More Native	V3 More Privacy
Approach	Minimal interference, behaves close to a regular browser	More parameters are spoofed
Canvas (macOS, plus screen and audio for Safari 26+ profiles), Canvas and WebGL (Windows)	Real	Spoofed
Site compatibility	Maximum	High
When to choose	Default, for most sites	If a site links profiles or sees real data

Why more spoofing isn’t always better. Every spoofed parameter is a chance of a mismatch. If a site notices that the Canvas image is “noisy” while everything else is real, that’s a signal too. Start with More Native and switch to More Privacy only if you have a reason.

After you change the mode, profiles are rebuilt and open pages reload. You stay signed in to your accounts.

Stealthy automation

When Automator or an AI agent drives a profile, Accovod’s helper scripts run in an isolated world. The site can’t find them in window and can’t use them to tell that a program is driving the page. Agent clicks arrive as real mouse events.

The fingerprint isn’t everything

Even a perfect fingerprint won’t help if all accounts share one IP, or a profile shows Moscow time on a US proxy. Read the short checklist How to avoid bans.