Interception is structurally impossible.
DocVanish never receives your decryption key. Encryption runs entirely in your browser. What reaches our infrastructure is ciphertext we cannot read.
Keys that never leave your device
AES-256 encryption runs in your browser before any data is transmitted. The key is derived locally and destroyed on session end — our servers process only an opaque, unreadable payload.
Watermark tied to the share link
Each watermark is cryptographically bound to its unique share token. A leaked copy carries a forensic signature traceable to the exact link — the recipient, the timestamp, the session.
The audit trail is yours alone
What we never store
Document content. Decryption keys. Recipient identifiers. Share analytics. File metadata. Server-side copies of any kind.
DocVanish retains zero document content, zero share analytics, zero recipient metadata. No access logs are written. When the link expires, the record of its existence expires with it.
We do not instrument document opens, page views, or download attempts on your shared files. What you send is outside our visibility by architectural design, not policy preference.
See exactly how a document moves through DocVanish
The full upload-to-expiry flow, with every encryption step made visible. No assumptions required.