How per-profile fingerprint protection works

Every desktop profile runs on the Sendwin engine, a patched build of Chromium. Alongside its own cookies and storage, each profile carries its own fingerprint settings — the values a website can read about the browser and the machine it runs on. The engine applies those values per profile, so two profiles on the same computer never share one browser identity.

This is a privacy feature, in the same spirit as the fingerprinting protection built into mainstream browsers. It keeps the profiles you manage separate from each other and from your personal browsing. It is not a promise about how any website or platform will treat an account — that is always the platform's decision, made under its own rules.

What stays consistent inside a profile

• Canvas rendering
• WebGL and GPU details
• Audio processing
• Installed fonts
• Hardware characteristics (cores, memory, screen)
• Timezone and locale, which follow the profile's proxy country
• User-Agent and client hints

Why consistency matters

The values are generated together, from one base device and the profile's proxy country, and they stay the same every time you open that profile. A profile that reported a different canvas hash on every reload, or a timezone that disagreed with its own locale, would be a less private profile, not a more private one — a value changed in isolation stands out. Keeping the whole set coherent per profile is what makes the protection useful.

Chrome or Edge identity

A profile's browser identity can be either Chrome or Edge. This is part of the profile's fingerprint settings, so its User-Agent and client hints stay consistent with the rest of the profile.