Regex patterns
High-precision patterns catch emails, phone numbers, SSNs, credit cards and API keys the instant they appear.
Every prompt is scanned for sensitive data before it leaves your network. Names, API keys, financial records, proprietary code — masked automatically.
Each prompt passes through four independent detectors. Their findings combine into a single masking decision before anything leaves your perimeter.
High-precision patterns catch emails, phone numbers, SSNs, credit cards and API keys the instant they appear.
Named-entity recognition flags people, organizations, locations and custom entities that no static pattern would catch.
Industry and jurisdiction rules add INN, SNILS, OGRN, medical identifiers and financial references on top of the base set.
A trained classifier resolves ambiguous, context-dependent data that the earlier layers leave undecided.
The prompt sits at the sealed core. Every request crosses five inward layers of control — and your raw data never crosses back out.
Traffic is confined to your isolated network. No outbound path exists to the public internet except through the gateway.
Every call is authenticated and scoped by role. Access to prompts, keys and logs is least-privilege by default.
Prompts, embeddings and audit records are encrypted on the wire and on disk throughout their lifecycle.
The four-layer detector masks sensitive data and applies your policy before any token is allowed outward.
Raw prompts and local inference live at the sealed center — processed inside the boundary, never beyond it.
The boundary is the design, not a setting. Detection, masking and inference all run inside the perimeter you control — only sanitized prompts ever reach an external model.
These are platform capabilities, not customer benchmarks. Figures describe how the system is designed to operate, verified during your own pilot.
Tell us your stack and compliance needs. We'll return a proposal showing exactly how prompts are masked and where your data stays.