Profiles

A profile is a browser of its own: its own data directory, its own cookies and local storage, its own generated device, and its own proxy. Nothing is shared between profiles, which is the entire point.

The editor

Five tabs. General, Proxy and Fingerprint are where the work happens; Platform holds the account login, its 2FA seed and a cookie import; Advanced holds the startup flags.

New profiles arrive with a fingerprint already composed, drawn from the same preset pools the app ships. The Environment Overview panel on the right is the summary of what a site sees, and the refresh control beside the user agent generates a different device.

Fingerprint settings

The Fingerprint tab has 4 groups of settings: core identity, hardware noise and graphics, hardware configuration, and advanced. Everything worth knowing about each one is on the fingerprint management page, including the two settings the app itself warns about:

• WebGL Metadata set to Custom. It changes the GPU string, but a service worker still reports the real one, and detectors look for that mismatch. The app recommends Real.
• Port Scan Protection. It replaces fetch, XHR and WebSocket inside the page, and some sites notice the patched functions. Off unless you need it.

Two more defaults worth understanding:

• OS. A profile can report Windows, macOS, Linux, Android, with Android emulating a Pixel 7. New profiles use the host OS. If you claim a different one, fonts, canvas raster and the real engine behaviour still come from the Windows machine, and the editor says so.
• Device memory. Chrome caps navigator.deviceMemory at 8 GB, so that is what a site reads however much RAM you set.

Engines

Chromium is the default. The app downloads Chrome for Testing builds per version, and if Google Chrome is installed it launches that instead for profiles that don’t load extensions, because a real binary is stealthier. The Chrome version a profile reports always matches the build that actually launches.

A Chromium profile can also present as Chrome, Edge, Brave, Opera, Vivaldi, Yandex: the user agent token, the Sec-CH-UA brand list and the navigator identity change together, while TLS stays that of the real Chrome underneath.

Firefox launches real Firefox, a copy already on your computer, or one the app downloads. Its overrides are narrower: proxy, user agent, locale, timezone and WebRTC off. The rest of the Fingerprint tab does not apply to Firefox profiles.

fingerprint-chromium is optional and off by default. It is a patched Ungoogled-Chromium build that applies canvas, WebGL, audio, user agent, platform and timezone natively instead of through injected scripts. The download is checked against a SHA-256 pinned in our source.

Groups and tags

Groups are for the thing a profile belongs to: a client, a market, a platform. Tags are for the work: a campaign, a quarter, a batch. Filter the table by group, tag, proxy or status, and the bulk toolbar acts on whatever is selected: launch, tag, assign a proxy, move to Trash.

Trash is recoverable. Deleting for good is a separate, confirmed action.

Leak Check

Leak Check runs from a profile’s row and has two halves.

Configuration analysis tests the profile’s proxy and looks for contradictions in its settings. Each check passes, warns or fails, and together they give a trust score out of 100 with a grade from A to F. The profile doesn’t need to be running.

Live test reads the real navigator, timezone and WebRTC values out of the profile’s open browser and scores those too, so what you see is what a site sees. The profile must be running.

Run it before a profile touches an account you care about. It is the cheapest check in the app.

Launching

Launch opens the profile with its proxy attached and its fingerprint applied. Several profiles can run at once. While a profile is running it is locked to the member who opened it, so two people cannot drive the same account by accident.

At launch, if geo auto-match is on (it is by default) the app looks up where the proxy exits and sets the profile’s timezone, language and WebRTC address to match. HTTP/3 is disabled for proxied profiles so UDP cannot bypass the proxy.