Where does your PDF go?

When you open a document in Omitly, it stays on your machine. Opening, redacting, saving and verifying all happen locally, on your own disk and in your own memory. The document you are working on is never uploaded to Omitly and never sent to a server to be processed.

Your document stays on your machine

There is no account to sign in to and no cloud step in the workflow. A redaction you make, the redacted file you save, and the audit report embedded inside it are all produced on your computer. You can work on confidential files — including offline — and the content never leaves the device.

What that means in practice

• No upload of your documents. The file you redact is never transmitted, in whole or in part.
• No content telemetry. Omitly does not send the text, the filenames or the contents of your documents anywhere.
• You can verify it. Because verification is local too, a recipient can check a redacted PDF on their own machine without uploading it either.

The network traffic Omitly does make

Being honest about this matters. The desktop app is not hermetically sealed off from the network — like most installed software it can check for its own updates and reach a support endpoint when you use in-app support, and an optional timestamp can be requested when you seal a document. None of that traffic carries your document’s contents. The distinction Omitly holds to is simple: your document and its contents never leave your machine, even though the app itself is an ordinary networked application.

If you connect your own AI, the text and previews it asks Omitly for go to that AI, and to its provider if it is hosted. That is your choice, and it is off until you set it up. See Connect your AI.

If you need a fully offline guarantee for a specific environment — a fleet deployment, an air-gapped network — see Deploying Omitly with Group Policy and Omitly on air-gapped and offline networks, or email support and we’ll work through the specifics with you.