Contact person: Business Client

Phone:Show

Email:Show

Location: Sao Goncalo, Brazil

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"I want a seasoned Chromium builder to take the vanilla source, strip out the Google-telemetry the way ungoogled-chromium does, then layer in strong privacy defences that play nicely with professional multi-login workflows. The project targets Windows and macOS only; each platform must ship with its own branded executable name and icon so users see a clean, company-specific browser identity from the installer all the way to the task-bar.

Privacy priorities
The big requirement is to disable the major fingerprinting APIs (Canvas, WebGL, Audio, Client Hints, etc.) while keeping everyday site compatibility intact. I do not need blanket third-party cookie blocking or obfuscation gimmicks—just the systematic API disablement so popular fingerprinting scripts fail silently. Think of the approach Brave or Tor take, but without touching cookies or user-agent string unless absolutely necessary for multi-login stability.

Multi-login friendliness
My users juggle many isolated browser instances side by side. The build therefore must respect Chromium profile separation, ensure storage, cookies, and service-worker caches never bleed across profiles, and avoid any shared persistent identifiers that would undermine session isolation. Native command-line flags such as `--profile-directory` must work as normal so existing automation tools can spawn concurrent sessions without hacks.

Search engine & branding
Google Search should remain the default provider after first run. Apart from that, no Google services should phone home. The product icon, app bundle ID, executable filename, About dialog strings, and user-visible update URLs must all reflect my new brand.

Deliverables
• Signed installers: one `.exe` for modern Windows, one notarised `.dmg`/`.app` for recent macOS ARM and Intel
• Source-patch set or forked repo with build instructions (GN args, patches, icon assets) so I can reproduce the binaries
• A short technical read-me describing which fingerprinting APIs were stubbed or removed and the exact flags/toggles you used to keep profile isolation intact

If you have prior experience trimming Chromium, tweaking GN build flags, and signing macOS apps, this should be straightforward. I’m ready to review your approach and move quickly once we confirm the technical path." (client-provided description)