Tune your security policy

Updated May 22, 2026

Yaplet gives every visitor a trust score from 0 to 100 and uses it to decide who chats freely, who is flagged as low trust, and who is blocked. You don't write the scoring logic yourself — instead, the Policy page lets you choose how strict it is and which signals it watches.

Open the Policy page

Go to Audience → Security → Policy. (Security is available on the Growth plan and any plan that includes it. If you don't see the Security section, your plan doesn't include it.)

Turn monitoring on or off

The first section, Security monitoring, holds the master switch, Score every visitor in real time. It controls the whole engine for every brand. When it's off, a warning says "Monitoring is off", no visitor is scored or blocked, and the rest of the page dims. Turning it off doesn't clear existing statuses — scoring just pauses until you switch it back on.

Pick a protection level

Under Protection level, three one-click presets set both decision lines at once. Choose the one that fits your risk tolerance:

Level Block line Low-trust line Best for
Relaxed 20 30 Only flags as low trust when several signals stack; still blocks outright attacks
Balanced (recommended) 26 40 One weak signal never flags; blocks bots and attacks
Strict 30 46 Any single signal is flagged as low trust; also blocks stacks of signals

Balanced is the default and works well for most sites. If you drag the lines to your own values, the level simply shows as Custom.

Set the low-trust and block lines

In the Trust thresholds section, a single bar from 0 to 100 has two draggable handles:

  • Block line (red) — visitors scoring below it are automatically blocked from chat.
  • Low-trust line (yellow) — visitors between the two lines are flagged as low trust; at or above it they're trusted.

The block line always stays below the low-trust line — the handles can't cross. As you drag, three boxes (Blocked, Low trust and Trusted) follow the handles and show the score range of each zone. Under them, a strip counts how many of your current visitors sit in each zone. Those counts use your saved lines, so while you have unsaved edits the strip says "Your visitors at your saved lines".

Switch signals on or off

Below the lines is the catalog of built-in signals, split into Risk · Bot detection, Risk · Behavioral, Risk · Network and Trust. Each one has a single on/off toggle — that's the only control. You can't hand-edit a signal's strength, and you can't write your own detection rules; the catalog is the same well-tuned set for everyone. Each signal shows a read-only number (how much it moves the trust score) and a Permanent or Expires 30d label.

Risk signals (lower the score)

  • Bot detection: Attack-tool user-agent (browsers announcing themselves as attack tools such as sqlmap or nikto) and High event velocity (abnormally high activity rates)
  • Behavioral: Disposable email address (disposable and throwaway email domains) and No-reply / automated email (no-reply, bounce and mailer-daemon addresses)
  • Network: Suspicious URL accessed — a page load whose URL path matches a secret- or source-exposure pattern such as /.env or /.git/. Admin paths are never matched, so browsing your own admin area costs a visitor nothing.

Trust signals (raise the score)

These reward genuine visitors. Five are on by default: Email address set, Established visitor (30 days), Long-standing visitor (90 days), Wrote a message and Returning visitor (multiple days). The last two are measured on our side from what the visitor actually did, so no integration can stamp them onto everyone. Four more — External account ID set, Customer value set, Plan set, and Display name set — are off by default because they rely on profile fields your integration sets; turn one on only if your integration fills that field meaningfully.

Save your changes

Save and Discard live in the title bar at the top. After any edit it shows Unsaved changes with Discard and Save changes; if you leave the page with unsaved edits, Yaplet asks first. The block line can't be placed above the low-trust line. Changes apply going forward — existing scores aren't recalculated.

Once your policy is set, check flagged visitors on the Visitors list.

Did this article answer your question?