Setup Guide

How to install and use Profile Keeper with the custom Chromium build and desktop client.

Contents Overview Requirements 1. Create an Account 2. Install Chromium 3. Install the Desktop Client 4. Pair the Client 5. Create a Profile 6. Configure Connection 7. Launch a Browser Daily Usage Troubleshooting

Overview

Profile Keeper helps you maintain consistent digital identities across sessions. It consists of three components:

Web Dashboard (this site) — manage profiles, fingerprints, and connections
Desktop Client — system tray app that syncs profiles and launches isolated browser instances
Custom Chromium — a patched Chromium build with native fingerprint noise (canvas, audio, math) applied at the C++ level for zero detection overhead

Requirements

Windows 10 or later (64-bit)
An account on this Profile Keeper server
SSH access to a remote server (optional, for IP tunneling)

1. Create an Account

1Go to the Dashboard and register with your email and password.

2Log in with your credentials. You'll see the main dashboard with Profiles, Devices, and Downloads.

2. Install Chromium

1Click Download Chromium in the top navigation bar. This downloads a ZIP file (~180 MB).

2Extract the ZIP to a permanent location, for example:

C:\ProfileKeeper\Chromium\

3Verify the folder contains chrome.exe, chrome.dll, and a Locales folder.

Do not run chrome.exe directly. The desktop client launches it with the correct flags and profile isolation. Running it manually will use default settings without any fingerprint protection.

3. Install the Desktop Client

1Click Download Client in the top navigation bar to get profile-keeper-client.exe.

2Place it in the same parent folder as your Chromium install, for example:

C:\ProfileKeeper\profile-keeper-client.exe
C:\ProfileKeeper\Chromium\chrome.exe

3Run profile-keeper-client.exe. A system tray icon will appear.

The client looks for Chromium at %USERPROFILE%\chromium\src\out\Release\chrome.exe by default. If your Chromium is elsewhere, place it at that path or create a symbolic link:

mklink /D "%USERPROFILE%\chromium\src\out\Release" "C:\ProfileKeeper\Chromium"

4. Pair the Client

1In the web dashboard, go to the Devices tab and click + Pair Device.

2A 6-character pairing code will appear. It expires in 5 minutes.

3Right-click the system tray icon and select Pair. Enter the code when prompted.

4Once paired, the client syncs all your profiles automatically. The tray icon tooltip shows the sync status.

5. Create a Profile

1In the dashboard Profiles tab, click + New and give your profile a name.

2Open the profile and click Generate New under Fingerprint. Optionally select a country to match the timezone and language.

3The fingerprint includes canvas noise seeds, audio noise seeds, language, timezone, and geolocation coordinates — all applied natively by the custom Chromium build.

Each profile gets a completely isolated Chrome user data directory. Cookies, history, extensions, and local storage are all separate between profiles.

6. Configure Connection

Direct Connection

Check Direct connection in the profile settings to use your current IP address. No tunnel is needed.

SSH Tunnel (SOCKS5 Proxy)

1Uncheck Direct connection to reveal the tunnel settings.

2Enter your SSH server details: host, port, username, and authentication method (password or SSH key).

3Click Save Config.

When the client launches Chrome for this profile, it automatically establishes a SOCKS5 tunnel over SSH and routes all browser traffic through it. The tunnel runs on a random local port and is transparent to the browser.

If using SSH key authentication, the keys must already be on the client machine at ~/.ssh/. The client tries the SSH agent first, then falls back to id_ed25519, id_rsa, and id_ecdsa.

7. Launch a Browser

1Right-click the system tray icon. Your synced profiles appear in the menu.

2Click a profile name to launch an isolated Chromium instance.

3The browser opens with all identity overrides applied:

Language and Accept-Language header (via --lang flag)
Timezone (via CDP Emulation.setTimezoneOverride)
Geolocation (via CDP Emulation.setGeolocationOverride)
Canvas, audio, and math noise (native C++ patches, seed-based)
SOCKS5 proxy (if tunnel configured)

Daily Usage

Launch: Right-click tray icon, select a profile. If the browser is already running, it brings it to focus instead of opening a duplicate.
Switch profiles: You can run multiple profiles simultaneously — each is a fully isolated browser instance.
Cookies: Use the Save Current / Restore buttons in the dashboard to back up and restore cookies for a profile.
Regenerate fingerprint: Click Generate New in the profile's Fingerprint section. Close and relaunch the browser for it to take effect.
Syncing: The client syncs with the server periodically. Changes you make in the dashboard (fingerprint, connection settings) are picked up automatically.

Troubleshooting

Browser doesn't launch

Make sure Chromium is at the expected path (see step 3).
Check the client log for errors. On Windows, the log is in the same folder as the client executable.

Fingerprint not applied

The profile must have a generated fingerprint. Check the dashboard.
Close and relaunch the browser after generating or changing a fingerprint.

Tunnel won't connect

Verify the SSH server is reachable from the client machine.
If using key auth, ensure your SSH keys are at ~/.ssh/ and the public key is authorized on the server.
Try connecting manually with ssh -D 1080 user@host to verify credentials work.

Client not syncing

Check that the device is still paired in the Devices tab. If revoked, re-pair.
Ensure the client machine has internet access to reach this server.