Launch prices end 31 Dec. Subscribe before then and keep yours · Lock my price

The words, in plain English.

Fingerprints, leaks, proxies and sessions: what each one is, why it matters, and what to do about it.

33 terms

Fingerprints, networks and sessions.

browser fingerprint

A browser fingerprint is the set of values a website can read from your browser without a cookie: version, screen, graphics, audio, fonts, language and more. Together they often identify one browser.

canvas fingerprint

A canvas fingerprint comes from drawing hidden text and shapes with the browser’s canvas API and hashing the pixels. Small differences between graphics stacks make the hash a signal.

WebGL fingerprint

A WebGL fingerprint combines the graphics vendor and renderer the browser names, its WebGL parameters and how it renders a 3D test scene. It identifies the GPU stack and must agree with the operating system.

audio fingerprint

An audio fingerprint comes from processing a test tone with the browser’s Web Audio API and hashing the result. Tiny differences in the audio stack make the output a signal.

user agent

The user agent is the string a browser sends to say what it is: its name, version and operating system. It has to agree with every other signal the browser presents.

client hints

Client hints are the structured successor to the user-agent string in Chromium browsers: the browser name and version, platform and architecture, available as headers and through navigator.userAgentData.

WebRTC leak

A WebRTC leak is when a page learns your real IP address through the browser’s peer-to-peer APIs even though your web traffic goes through a proxy or VPN.

DNS leak

A DNS leak is when the names you look up are resolved by your own network’s resolver instead of through your proxy or VPN, so your provider and the site can see two different locations.

residential proxy

A residential proxy routes your traffic through an IP address assigned to a home internet connection. Sites trust these addresses more than data-center ones, and providers usually bill by the gigabyte.

datacenter proxy

A datacenter proxy uses an IP address from a hosting or cloud provider. It is fast and cheap, and easy for a site to recognise as a server address.

mobile proxy

A mobile proxy exits through a mobile carrier’s network. Many real users share carrier addresses, so these IPs are seldom blocked, and they are the most expensive kind.

ISP proxy

An ISP proxy, or static residential proxy, is an address registered to a consumer internet provider but hosted in a data center. It keeps the same IP for as long as you rent it.

sticky session

A sticky session is a proxy login parameter that asks the provider to hold one exit address for a while. The provider decides the address and how long it lasts; it is not a guarantee of a unique IP.

rotating proxy

A rotating proxy assigns a new exit IP, either on every request or at a fixed interval, from a large pool. It suits scraping, and is the wrong tool for a logged-in account.

HTTP and SOCKS5 proxies

An HTTP proxy understands web requests and resolves names itself; a SOCKS5 proxy relays any TCP connection (and optionally UDP) without reading it. Both work in a browser profile; which you need depends on the provider and on WebRTC.

exit IP

The exit IP is the public address a website sees after your traffic leaves the proxy. It decides the country, city and network the site thinks you are in.

IP reputation

IP reputation is how risky a site judges an address to be, from its network type (home, mobile, hosting), its history of abuse and how many people share it.

browser profile

A browser profile is one stored identity: its settings, its saved data and, in an antidetect browser, its own fingerprint and proxy. Opening a profile opens that identity.

cookies and site data

Site data is what websites store in your browser: cookies, local storage, session storage and IndexedDB. It keeps an account signed in, and it can hold identifiers a site compares with the browser it sees.

headless browser

A headless browser runs without a visible window, so scripts can drive it on a server. It is efficient, and it presents a different detection surface from a visible browser.

CDP (Chrome DevTools Protocol)

The Chrome DevTools Protocol is the interface that lets code control a Chromium browser: open tabs, navigate, click, read the page. Playwright and Puppeteer speak it.

multi-accounting

Multi-accounting is operating many accounts on the same platform: a client’s several pages, a team’s shared logins, regional accounts, testing. It is legitimate work, and platforms have rules about it.

account warm-up

Account warm-up is a staged start for a new account: browsing first, then likes, follows, replies and posts on set days.

time zone mismatch

A time zone mismatch is when the browser reports one time zone while the connection’s IP address is in another. Pages can compare the two in a single call.

fingerprint consistency

Fingerprint consistency means every value a browser presents agrees with the others: operating system, user agent, client hints, graphics, screen, language and time zone. Contradictions are the signal.

antidetect browser

An antidetect browser runs many separate browser profiles on one computer, each with its own fingerprint, cookies and proxy, so many accounts can be kept apart and shared with a team.

font fingerprint

A font fingerprint is the list of fonts a site can detect on your computer, measured by drawing text and checking which typefaces render. Installed fonts differ from machine to machine.

WebGPU fingerprint

A WebGPU fingerprint is what the WebGPU API reveals about your graphics card: its vendor, architecture and capabilities. It must agree with what WebGL says.

client rects fingerprint

A client rects fingerprint comes from the exact sizes and positions of rendered elements, which vary slightly with fonts, rendering and system settings.

media devices fingerprint

A media devices fingerprint is the list of cameras, microphones and speakers a page can count, and their device IDs.

hardware fingerprint

Browsers report the number of CPU cores (hardwareConcurrency) and approximate memory (deviceMemory). Together with the graphics card they describe the machine.

TLS fingerprint

A TLS fingerprint identifies the software making a connection from how it opens a secure connection: its TLS version, cipher suites, extensions and their order.

port scan protection

Some sites probe ports on your own computer from the page to see which local services run. Port scan protection blocks those probes.

In the app

The words Clout Browser uses.

Profiles, fingerprints, proxies and the ways to script them.

Antidetect browser
A browser that keeps many profiles apart: each has its own fingerprint, site data and proxy, so one person or team can run many accounts on one computer.
Browser profile
One stored browser identity, its configuration and its browsing-data directory. In Clout Browser a profile is a row in the register that you can name, file in folders and reopen.
Fingerprint
The operating system, user agent, graphics, hardware and noise settings a profile presents to a website. It holds up when its signals agree with each other.
User agent
The browser identity string. It has to agree with the rest of the fingerprint, including the client hints a page can read.
Canvas fingerprint
A signal made by drawing a hidden image and reading back how this device’s graphics stack rendered it. Small differences between devices make the result a signal.
Site data
What websites have stored in a profile: cookies, local storage and IndexedDB. It is what keeps an account signed in.
Session
The signed-in state a browser or site uses. Stored cookies can expire, so a copied session can be dead.
Engine
The browser binary that opens a profile: SunBrowser or Chroma, according to the profile’s stored format. There is no toggle between them.
Kernel
A version of the browser engine, often identified by its Chromium major.
Pin
The engine major a profile requires. An installed newer major does not replace it automatically.
Proxy
A server that sets where a profile’s connection exits. Without one, the profile uses the computer’s own connection.
Exit IP
The public address a website sees after the proxy connection.
Sticky session
A provider credential parameter that asks for a held exit. The provider decides the exit and how long it lasts; it is not a guarantee of a unique IP.
LiteTunnel™
Clout’s own traffic technology. On supported sites it tunnels the heaviest traffic without spending proxy data; on every other site it tunes what pages pull, at the level chosen in the app (Lite by default). Profiles, fingerprints and sign-ins don’t change. Each plan includes an allowance; when it is spent, LiteTunnel™ pauses and browsing keeps working, with nothing owed.
Folder
An organisational collection of profiles. A folder can have subfolders and a profile can belong to several.
Rank
Owner, Admin, Manager or Employee: what a team member may do. Profile access separately decides where.
CDP
Chrome DevTools Protocol. Automation connects to the endpoint a profile start returns, so a script drives the real fingerprinted browser.
Local API
The HTTP server Clout Browser runs on your computer to start, stop and manage profiles. Its v1 routes match AdsPower’s; v2 is the clearer contract for new work.
MCP
Model Context Protocol, the tool interface an AI client uses to discover and operate other software. Clout Browser’s MCP server lets an agent list, start and stop profiles and take a browser’s CDP endpoint.
cloutctl
The Clout command line, for working with Clout Browser from a terminal or a script.

Your accounts deserve a better browser.

One profile free for as long as you like. Every plan free for 3 days. Cancel any time.