Compliance

Follow the document. Check the safeguards.

See where your files are processed, then explore the details your DPO needs.

On your device

Original document

Opened by Anoni on your machine.

Local detection

The engine detects data. You review the results.

Export and vault

You choose what to share. The encrypted mapping stays local.

The app’s connections

Engine and model downloads, activation, and license checks. A crash report can be sent with your agreement. These exchanges do not send your documents.

Documents and connections

Separate document processing from the app’s network connections.

On your machine, and nowhere else. Detection and anonymization run locally. Unplug the network: everything keeps working.

The safeguards

Encryption, models, and updates: how the mechanisms work.

The mapping between fake name and real data is encrypted with AES-256-GCM, using a key derived from your passphrase via Argon2id. Without the passphrase, no one decodes it. Not even us.

A record of processing

What you can keep after an export.

Each run produces a report generated locally: categories, counts, exclusions, SHA-256 fingerprint, version. No personal data inside. A trace to archive.