Security
One file. One machine. Then nothing left.
A production Outlook store or a hypervisor disk is not a PDF. Isolation is the product — not a badge on the homepage. This page says what happens to the file, and what we refuse to pretend.
From the upload to an empty room
Encrypted in
Alone for the job
You take the result
Then the room is gone
What we actually do with the file
Nobody else’s mailbox in the same room
Each conversion runs in a disposable environment. An OST, a PST or a VMDK is not mixed into a shared desktop session with another customer’s archive.
The pipe is sealed
Uploads and downloads use TLS. We do not offer an unencrypted public conversion endpoint, and we do not take a business file over a clear channel.
We convert. We do not keep.
Guest inputs and outputs expire after delivery. This is not an archive host. Business workspaces keep operator job history; they are still not a records-management system. Keep your own copy of the result.
Your archive is not a dataset
Uploaded files are not used to train machine-learning models. Iacopo helps describe an intent. It does not retain your document as learning data.
No certificate hanging in a hallway
We follow GDPR and describe ISO 27001-aligned practices and Swiss nFADP respect. This page is not a certificate. For a processor agreement or a named security questionnaire, use Contact.
ContactWork stays off the public web
Dashboards, API keys, task URLs and /app are not for search engines. Task pages send noindex. Do not treat a conversion job URL as a public document.