Your file is encrypted inside your own browser, with a key only our processing machine can unwrap, before it ever leaves your device — so nothing readable crosses the internet in the first place.
Why "encrypted in transit" alone isn't the same claim
Most services encrypt data "in transit" (that's just HTTPS, the same padlock every website uses) and decrypt it the moment it reaches their server. That protects the file from someone intercepting it on the wire — it does nothing to stop the service itself, or anyone with access to its servers, from reading the content the instant it arrives.
What actually happens here
Each file gets its own encryption key generated in your browser before anything is sent. That key is wrapped so only the machine that will process the job can unwrap it. The file travels and sits encrypted the whole way; it's only decrypted inside an isolated workspace on hardware we own, right before processing starts.
Where this breaks down — said plainly
- This protects the file in transit and at rest before processing. Once a job runs, the content has to be readable by the software doing the work — that's true of any processing service, not a gap specific to this one.
- It doesn't make the choice of what to send us for you. Anything genuinely too sensitive to process anywhere outside your own walls shouldn't be uploaded to any third party, including this one.
Related guides
- How uploaded data is stopped from leaking out
- What is a destruction certificate?
- Can you redact documents without uploading them to a cloud?
Where this fits on the site: this is part of how every job runs here, across all services. See Services & Pricing for what's actually sold, or go straight to Choose your job.