Policy and enforcement
Blank starts by watching, and does nothing louder until you decide to. Enforcement is opt-in, and it's designed so you never escalate faster than your data supports.
Enforcement modes
Your organization has one fleet-wide enforcement mode, and it's the ceiling on everything.
- Monitor (the default). Record every finding, coach nothing, block nothing. This is where every deployment begins.
- Coach. Show the employee an in-page note when a medium-or-higher finding is about to be sent. They can remove it or proceed. It's a nudge, not a wall.
- Block. Cancel a send that policy says must not go out.
The effective action is always the quieter of the fleet mode and any rule, so an org in Monitor coaches nothing no matter what a rule says.
The 14-day gate
You can't escalate past Monitor until the org has 14 days of real data. Coaching people about a picture you haven't actually measured is how you lose their trust, so the gate makes sure the baseline is real first. Pulling the brake back down to Monitor is never gated. An admin mid-incident shouldn't have to wait.
Policy rules
Within Coach or Block mode, rules decide what happens to a specific finding. A rule targets any combination of four axes:
- the detector that fired (for example,
credit-card), - the AI tool (for example, ChatGPT),
- the tool's category (for example, chatbot),
- the user group.
When several rules match, the most specific wins (detector beats tool beats category beats group), then an admin priority, then the more restrictive action. A narrow exception can sit on top of a broad rule without deleting either.
Every change is versioned with who changed it and a readable diff, and a 30-day preview shows how many findings a rule would have affected before you turn it on.
The Block precision gate
You can't enable Block on a detector until it has cleared a 95% precision floor: enough real detections to judge, with a low-enough false-positive rate. Blocking on a noisy detector is blocking someone's actual work, so the gate is enforced on the server, not just hidden in the UI. Tool-wide and category-wide Block rules span many detectors and are allowed. A single-detector Block waits until that detector has earned it.
Coaching has a severity floor
Blank records every finding but only interrupts at medium severity and up. Low-risk findings, like a colleague's email address or a phone number, are on your usage picture but never in an employee's face. The vocabulary is closed and ours, so it can't be gamed by an odd value.
Custom detectors
Beyond the built-in detectors, you can add your own patterns, like an internal project codename or a customer-ID format. Each one is safety-checked (including against catastrophic regular expressions) before it's allowed to run on employees' machines.