Privacy Filter
Personal data (names, addresses, IBAN), bank details, medical diagnoses — masked or blocked before reaching the AI model.
Every employee request runs through configurable inspection layers — before reaching an AI model. Sensitive data detected and masked, problematic content filtered. Effectiveness and responses are controlled via your admin configuration.

Each layer operates independently — multi-layer inspection reduces the risk that individual content slips through unnoticed.
Personal data (names, addresses, IBAN), bank details, medical diagnoses — masked or blocked before reaching the AI model.
Insults, discrimination, illegal content, drug references — requests are blocked or sent for confirmation depending on configuration.
Self-harm, prompt-injection attempts ("Ignore all instructions…"), harmful requests — blocked or sent for confirmation, depending on configuration.
Every interaction is logged — as a basis for your own compliance evidence, audits and reports.
On critical questions the answer is checked by 5 independent AI models, a leader filters the consensus. Single hallucinations don't pass — disagreements are shown transparently.
Yes. Admins can configure PII categories and strictness levels per user group.
Detected PII is masked or blocked depending on configuration. Detected values are replaced with placeholders before the AI call; the masked request is sent to the model.
Yes. Documents are analyzed before processing. Admins control allowed file types per group.
Layers 1-4 check the INPUT before it's sent to the AI (privacy, content, manipulation, audit). Veritas (layer 5) checks the OUTPUT — by querying 5 independent models in parallel and synthesising consensus. Pre-model and post-model protection interlock.
Pro and Enterprise: yes, at no extra cost (uses the normal fair-use budget). Demo: yes, with limited budget. Company admins can disable Veritas per tenant or per user. Details on the Veritas Chat feature page.