The Handler

The Handler is a second opinion from a model on sessions the detector can't call. It is off today, on every plan. This page says what it would do when it is switched on, so you know what to expect and what it would see.

You don't need to do anything. Verdicts, tokens and the portal work fully without it, and the judge field on a verdict stays empty.

When it runs

Only on unclear sessions: the chance of a bot or agent is between 25 % and 75 %. Sessions in quarantine are never sent. Clear human, bot and agent sessions never reach it.

Usually it runs after the visit, in the background. A site can also let check() wait for it, for at most 1.5 seconds.

What it sees

• Page and referral details, such as the path, the site profile and the action.
• Browser environment measurements and interaction statistics.
• Numeric features and the signal codes found.
• A summarised timeline of the visit.

It does not get the raw IP address, the full user agent or linked identifiers such as a user id hash. Page and environment fields can still hold personal data, so don't treat them as anonymous.

What it can change

Its answer becomes one signal, judge.*, capped like every other group of evidence. It can tip an unclear session one way or the other. It can't override hard evidence, such as a known automation tool in the page or a verified signature.

If the final class changes, the session's final verdict is updated, the Debrief webhook fires, and connected tools can be relabelled.

Before it is switched on

Two providers are built: TypeSafe and Cloudflare Workers AI. Before an external provider processes any session, it will be listed on the subprocessors page and customers will be told as the DPA requires.

Next: Site profiles for how the recommendation is set, or Verdict.