| Where does real client or customer data end up? |
On your device: detected details are replaced with mirror data before sending |
On the provider's server, possibly EU-hosted |
At the model, if a spot gets missed |
| Professional secrecy |
A technical step before sending: replacement, preview, guard |
The plain text usually reaches the platform provider |
Depends on how carefully the person redacting works |
| Contract and third countries (DPA, e.g. USA) |
Your contract with the AI provider stays in place, but the provider only receives text in which detected details have been replaced. Real detected identities stay on your computer. With a locally downloaded model via Ollama, no external AI provider is involved |
Contracts (DPA, where applicable standard contractual clauses or the Data Privacy Framework) govern what happens to the plain text at the provider and its sub-processors |
Depends on what gets missed during redaction |
| Billing |
License per seat, annual or monthly; AI usage through your own API key, billed directly by the provider; no usage limit inside the tool |
Depends on the provider, often a subscription per user |
No tool, but plenty of staff time |
| Model quality |
Full strength of the connected cloud models (Claude, ChatGPT, Gemini, Mistral AI); usable because masking happens locally first |
Also top-tier models, but real data travels to their servers |
Any model can be used; it sees redacted spots instead of readable details |
| Setup effort |
Download, ready in a few minutes, no server, no hosting cost |
Depending on the provider, contract, onboarding and user management for the whole team |
Hosting, servers, IT config if self-run; otherwise ongoing manual effort |
| Works offline |
Yes: with Ollama and a locally downloaded model, the AI runs on the device |
Usually not: SaaS, no internet means no access |
Yes, but without AI assistance |
| Understands a whole case file? |
Deadlines, parties, completeness, mandatory source citations |
Knowledge base / RAG over uploaded documents |
No |
| If a provider suffers a data breach |
The AI provider holds texts in which detected details have been replaced. Details that were not detected may still be included. |
Plain text held by the platform provider may be affected |
Whatever was missed during redaction is affected |
| Proving deletion |
Deletion record from the app (“deletion certificate”) for the data deleted in the app, with verification scan |
Deletion request to the provider, proof often manual |
— |