Scans of your passport. A signed contract. Medical records, tax documents, payroll files. Sooner or later everyone has to send a document that genuinely must not leak — and most people do it the worst possible way: as an email attachment, unencrypted, copied onto multiple mail servers indefinitely. Here's a practical, non-paranoid guide to doing it right.

Why email is the wrong place for sensitive documents

An email attachment is duplicated onto your mail provider's servers, your recipient's provider's servers, and every phone and laptop syncing either inbox. Those copies persist for years, outside your control, protected only by each party's password habits. Email also fails gracefully in the wrong direction: forwarded chains, wrong-recipient autocomplete, and mailbox breaches expose attachments wholesale.

The two properties that matter

When evaluating any method for confidential documents, ask:

  1. Is it encrypted end to end? Meaning: unreadable to everyone except sender and recipient — including the service in the middle.
  2. Where do copies live afterwards? Every stored copy is a future liability. Fewer copies, held for less time, in fewer places — that's the whole game.

Cloud links with passwords improve on email but still leave a copy on the provider's servers, tied to accounts and retention policies. The strictest available answer to "where do copies live?" is nowhere — which is what direct P2P transfer provides.

Sending a confidential document with ZetaShare

ZetaShare streams files directly between two browsers over a DTLS 1.3-encrypted channel. No upload, no server copy, no account:

  1. Open ZetaShare and drop in your document.
  2. Set a password. This is essential for confidential material — the link alone won't start the transfer.
  3. Send the link through one channel (e.g., email) and the password through another (e.g., text message or a phone call). This "two-channel" habit means intercepting one channel gets an attacker nothing.
  4. Confirm your recipient received it, then close the tab. The link is now dead, and no copy exists anywhere between your device and theirs.

Extra precautions worth taking

  • Verify the recipient first. Most document leaks are mundane: the wrong "David" in autocomplete. Confirm before sending, not after.
  • Strip what the document doesn't need. PDFs and Office files carry metadata (author, tracked changes, comments). Export a clean copy for external sharing.
  • Redact properly. Drawing a black rectangle over text does not remove it. Use real redaction tools that delete the underlying content.
  • Mind the endpoints. Encryption protects transit; it can't protect a document that lands on a compromised or shared computer. For highly sensitive material, agree with the recipient on where it will be stored.

Who this workflow fits

Freelancers sending contracts, HR teams moving payroll files, patients sharing records with a specialist, landlords and tenants exchanging IDs, lawyers sending drafts — any situation where the honest requirement is "this must reach exactly one person and exist nowhere else."

FAQ

Is a password-protected P2P transfer enough for legal/medical documents? It provides end-to-end encryption in transit with zero third-party storage — stronger on both axes than standard email or cloud links. Your profession may add its own compliance requirements; when in doubt, check them.

What if my recipient isn't tech-savvy? They click your link, enter the password, and receive the file in their browser. No account, no install — it's less friction than most "secure portals."

For a deeper look at the security model, read Is P2P file sharing safe? — or send your document securely now.