Anti-detect browser

Also called: antidetect browser, anti-detection browser.

An anti-detect browser is a browser whose unit of work is the identity rather than the window. Each identity gets its own storage on disk, its own set of device characteristics reported to pages, and its own route onto the network, so two sessions running side by side on one computer present as two unrelated visitors. That is the whole category: ordinary browsers are built to be one person efficiently, and these are built to be several people separately.

The distinction that matters when comparing them is where the substitution happens. Tooling that automates a browser it did not build can only intervene in JavaScript — an extension or an injected script replaces a native function with a wrapper — and a page that inspects the wrapper learns not only that something is hidden but that this visitor is the kind that hides things. Argus ships its own Chromium build, so the values are applied in the renderer, which is how fingerprints work here in detail.

What the category does not do is create permission. Separating accounts you are entitled to hold is not the same as making a prohibited account permitted, and any vendor blurring those two is describing something that does not exist.