Confidential workflow
Process confidential images and PDFs locally with realistic safeguards
Local processing removes the conversion server from the file path, but it does not make an untrusted device safe or prevent later disclosure. Treat the browser session, downloaded copy, backups, and delivery channel as one workflow.
Workflow
Prepare a trusted environment
Use an updated managed device and browser, review extensions, close unrelated tabs, confirm the correct site origin, and follow organizational rules before opening the file.
Minimize the working copy
Use only the pages and data needed, remove incidental metadata when appropriate, avoid revealing filenames, and complete the supported operation without cloud storage.
Control the result
Verify the download, move it to approved storage, share through an authorized channel, remove unnecessary working copies, and close the session.
Limits to understand
Browser-local processing cannot defend against malware, compromised extensions, screen capture, operating-system swap files, synchronized download folders, shoulder surfing, or a recipient redistributing the output.
Privacy mode
Selected file bytes, pixels, metadata, passwords, options, previews, and outputs are not sent to the application server for supported tools. Ordinary page requests may still expose URL, browser, timing, and network data under site policies.
Verify the result
Observe the network panel during a representative job, confirm no request contains the file or filename, inspect the final copy for hidden data, and document where the result and backups are stored.
Frequently asked questions
Does local processing mean no network connection?
No. The site downloads code and may make ordinary page or consented analytics requests; the privacy boundary concerns selected file content and job data.
Is private browsing enough for confidential work?
No. It mainly changes local history and storage behavior. Device security, extensions, downloads, networks, and organizational policy still matter.