FAQ

Clearcote is a privacy and automation tool intended for lawful purposes — protecting your own privacy, web/QA testing, research, accessibility and automation you are authorized to run. You are responsible for how you use it; respect website terms of service and applicable laws.

Clearcote controls browser fingerprint signals so a session presents one coherent, plausible identity. It is not marketed against, and does not target, any specific detection product, and it is not a guarantee of evading any system. Treat it as a privacy/identity-consistency tool and validate behavior yourself.

Those overwrite navigator properties at runtime with injected JavaScript, which is brittle and self-revealing. Clearcote changes the C++ engine, so values come from Chromium's own code paths — there's no injected layer to detect. See Architecture.

No tool is. Engine-level, coherent controls remove many common tells, but detection is an evolving space. Always validate your configuration against tools like CreepJS, BrowserScan and Pixelscan for your use case.

No. It's built on ungoogled-chromium — Google services, telemetry and update beacons are removed.

Windows x64 today. Additional platforms are on the roadmap.

Yes — it's a drop-in browser. Point executablePath at the Clearcote binary. See Playwright & Puppeteer.

Use a different --fingerprint seed per identity (e.g. derived from a tenant/account id) and a separate user-data dir per profile for cookies/storage.

Yes — BSD-3-Clause. Every patch is human-readable, and the build is reproducible from source. Don't trust us, verify us.