Detection statistics
Compliance profiles
Toggle a profile to see which entity types it enforces and how each is handled.
Exactly one profile is active per request — the engine narrows detection to the
profile's entity set and applies its thresholds.
Redaction volume
Intercept volume by window, read from the engine's metadata journal: entity
types, offsets, scores, byte counts and truncated value hashes. The engine
stores no entity values, so a hash can only be resolved by the local reveal
vault, which holds the key.
Intercepts
Click a pass to drill into its spans: type, offsets, masked preview and a
48-bit hash. Reveal (local) asks the vault on
this network to open that hash. The value is
shown in your browser only and never travels to the engine or through any
model.
Custom PII patterns
Loading…
This deployment is read-only: patterns are managed in engine/config.yaml
on the server. Saving from this page is disabled.
Customer-defined patterns are always treated as PII regardless of recognizer
score. Patterns live in engine/config.yaml under deny_list:
value (exact, case-sensitive) or set is_regex: true
for a pattern, plus an entity_type.
Statistics are aggregated from the audit trail, which stores entity types,
actions, scores and timestamps only — never raw values. No redacted content
appears on this page by design.