Find what's sensitive without sending it anywhere to check.

Three layers run inside the gateway: validated rules, a local NER model for names and addresses, and your own dictionaries. No LLM is involved.

Three layers

Each layer catches what it is good at.

Hover a layer to see what it catches.

Daniel Reed wants to move €2,400 from GB82 WEST 1234 5698 7654 32 to project Atlas. Call him on +44 7700 900123 or daniel.reed@example.com.

Consistency

One person, one token.

Spelling variants of the same name share a token; a partial name does not. Try your own.

MentionCompared asToken

Accuracy

Measured per type, not promised.

TypeMethodDefaultPrecisionRecall
PERSONLocal NER (int8 BERTurk)On94.4%99.5%
TCKNChecksumOn100%100%
VKNChecksumOn100%100%
IBANCountry format, mod-97On100%100%
CARDLuhnOn100%100%
PHONEParsed to E.164On100%100%
EMAILPatternOn100%100%
SECRETKey and token patternsOn100%100%
ADDRESSRulesOn100%63.3%
Your rules and dictionaryRegex, exact termsOn——
DOBPlanned———
City, country, amounts, datesRecognised, passed throughOff——

Synthetic Turkish and English corpus v1: 6,470 labelled values, strict span match, October 2026. Your data will differ; the local harness scores a labelled sample on your premises.

  • Up to 32,000 characters per message by default; above that the send fails closed.
  • Every type can be switched on or off per deployment.

Give your teams AI your security team can sign off.