Local, with Anoni
On your device
Document
Anoni
Result
Detection and anonymization run on your machine. The document is not sent to a server for processing.
Local vs cloud
Where is your document processed?
Your processing choice determines where you send your data. Here is the document’s journey in each case.
Starting point
A document containing sensitive details.
Cloud
Upload to the remote service
Document
Remote server
Result
The service receives the document for processing. Hosting, retention, and access conditions depend on the provider.
Local processing does not mean no connection: engine installation, activation, and license checks use the network. These exchanges are separate from your document content.
How it works in detail
The data, the vault, and the network.
To anonymize your document in the cloud, a service first has to read it. That means you upload it whole, in the clear, before any data is removed. The transfer happens, the copy lands on someone else's server, the logs may keep it. The risk you wanted to avoid, you already took it the moment you pressed send.
The honest trade-off
Local means the work runs on your machine, and so does the read-through. You keep the document, and you keep responsibility for it. Anoni finds the sensitive data and replaces it, fast, but it does not relieve you of a final check. The tool helps. It does not decide for you.
You choose what to share.
After preparing and reviewing the document, you choose its recipient. If you send it to an AI, that service’s terms apply to the text you send.