Vault Ask 
Vault Chat 
Vault Learn 
Vault Lingua 
Vault Tender 
Vault Cloak 
instead of real names in the request to the cloud AI
The Problem
Some tasks call for a very large cloud language model — analysing long contracts or expert reports, for instance. But documents containing names, addresses or bank details should not end up in the cloud unchecked.
The Vault Solution
Vault Cloak detects personal data locally on your hardware and replaces it with stable placeholders. Only this placeholder version goes to the cloud AI; Vault then puts the answer back together with the real details. Cloak is optional, does not access your knowledge base and is the only module that talks to an external AI. Without Cloak, Vault stays fully self-contained.
Your Benefits
- Detection of names, organisations, addresses, contact details, bank details and other identifiers on your hardware
- Stable placeholders: the same person has the same placeholder across all your documents
- A check before every request: known original values and patterns such as IBAN or e-mail — when in doubt, it blocks
- The answer shows the real details again; export generated locally in seven formats
- Documents and chats are visible only to whoever uploaded them — not even to administrators
- Optional: without Cloak, no request leaves your building
Example
You upload a contract as a PDF. Cloak replaces names, address and IBAN with placeholders, and you ask the cloud AI about the notice periods. The answer appears with the real names — as a Word file generated locally, if you like.
A note on data protection: Cloak pseudonymises, it does not anonymise — the placeholder mapping stays with you. Cloak does not automatically detect health data or other special categories under Art. 9 GDPR. Record in your data protection documentation whether and for what Cloak is used.