Cookies and device identification

Effective November 13, 2026

On this website and the dashboard

Name	What it is	Why	How long
__Host-antibot_session	Your signed-in session (a random token; only its hash is stored)	Strictly necessary: signing in	Until you sign out, or seven days unused
__Host-antibot_2fa	A sign-in waiting for its second factor, after the right password (a random token; only its hash is stored)	Strictly necessary: signing in with two-step verification	Five minutes, or until the code is entered
antibot_sso	A single sign-on under way, tying the identity provider's answer to the browser that asked for it	Strictly necessary: signing in through your company's identity provider	Ten minutes, or until the provider answers
_abid	The receipt the live demonstration's agent writes when it identifies your browser	Only with the demonstration	Ten minutes
_abid on the sign-up and sign-in pages	The receipt our own agent writes there, read when the form is sent, to tell a person from a script	Strictly necessary: the security of the accounts you make and sign in to	Ten minutes
antibot:visitor on the sign-up and sign-in pages, in your browser's storage	Who your browser was, as our service signed it, so the device that signs in is recognised as the one that did before	Strictly necessary: the security of the accounts you make and sign in to	Until the next sign-up or sign-in replaces it; honoured for 400 days
Theme	Your light or dark choice, in your browser's storage	Your preference	Until you clear it

No advertising or analytics cookies are used.

The marketing pages' live demonstration identifies your browser as our customers' pages do — reading characteristics of your device — and shows you the result. It runs only when you press Identify this browser: until then nothing is read from your device and the agent is not loaded. What it records is kept in our demonstration organization for seven days.

On our customers' sites

Our customers decide to place our agent in their pages. It writes the _abid receipt cookie on their site and reads characteristics of the device to tell people from automated clients. The customer is responsible for telling its visitors and, where the law requires, for asking their consent; its own cookie notice describes it. What the agent writes, item by item, and what turns each off, is in our documentation (What the agent stores).