How to share sensitive documents safely
Medical records, ID scans, financial paperwork and legal documents need more care than an email attachment. A practical checklist for sending them without leaving copies everywhere.
At some point everyone has to send a document they would rather not have floating around: a passport scan for a rental application, a medical report to a specialist, a bank statement to an accountant, a signed contract.
The usual approach is to attach it to an email, wince slightly, and press send. Here is what that actually costs, and what to do instead.
What happens to an emailed document
An email attachment does not go to one place. It goes to, at minimum:
- Your sent folder, indefinitely
- Your mail provider's servers, indefinitely, in a form they can read
- Your recipient's mail provider's servers, same
- Your recipient's inbox, indefinitely
- Frequently, the recipient's local mail client cache and phone
- Often a backup system at both providers
Six-plus copies, none of which you control, most of which outlive the reason you sent it. Email providers scan attachments — for malware at minimum, and historically for advertising. Neither Gmail nor Outlook is end-to-end encrypted; both providers can read your attachments and have complied with legal demands for them.
There is a longer treatment of this in is email secure for sensitive documents, but the short answer is no.
The checklist
1. Ask whether you need to send it at all.
The most secure document transfer is the one that does not happen. Do they need the full bank statement, or the balance on one date? The whole passport page, or the number? A redacted version of a document is dramatically less damaging if it leaks, and a surprising proportion of requests are habit rather than requirement.
2. Redact what is not needed.
Black out account numbers, addresses, dates of birth and reference numbers that are not relevant. Do it properly: drawing a black rectangle over text in a PDF viewer does not remove the text, it covers it, and the text is still selectable underneath. Use a tool with a real redaction function, or flatten to an image first, or print-and-rescan if you have no better option.
3. Strip metadata.
Scanned documents carry scanner model and timestamps. Photos of documents — a very common way to send an ID — carry GPS coordinates from your phone. A PDF made from a Word file inherits the author name and organisation from the original.
For a photo of a document, the simplest reliable fix is to screenshot the photo and send the screenshot. Screenshots carry almost nothing.
4. Send it through something end-to-end encrypted.
This is the part where the tool matters. What you want is a service that encrypts on your device, so it is not making a promise about behaviour — it is unable to read the file regardless of intent. The practical test: if it can show a preview thumbnail of your document, it can read your document.
5. Prefer short-lived delivery.
A file that is deleted once collected has a exposure window of minutes. A file sitting in a cloud folder has an exposure window of "until someone remembers". Choose the first.
6. Confirm the recipient out of band.
More sensitive documents are lost to sending them to the wrong person than to interception. Before you send anything serious, confirm the address or alias through a different channel — a phone call, a message on another app. This is the single highest-value habit on this list and it takes ten seconds.
7. Tell them how to handle it.
Ask them to download it, store it where it needs to go, and delete the copy. Most people will, if asked. Nobody will if not.
Documents that deserve extra care
Identity documents — passports, driving licences, national ID. These are the raw material for identity fraud and they do not expire when the transaction does. Where possible, send a version with a visible watermark stating the purpose and date ("For [company] tenancy application, 4 March 2026"), which makes a stolen copy far harder to reuse.
Medical records. In many jurisdictions these carry specific legal protections, and the practice you are sending to may have obligations about how they receive them. Ask — many have a secure portal, and using it is both safer and less work for them.
Financial statements. Contain account numbers, transaction histories and address history. Redact aggressively; an accountant needs totals far more often than they need line items.
Anything involving someone else's data. If a document contains information about a third party — a co-signer, a patient, an employee — you are making a decision on their behalf. That raises the bar.
Doing it with AliasCloak
The flow, concretely:
- Clean and redact the document first. This part is on you and no tool does it for you.
- Ask the recipient to open aliascloak.com and click "Create mailbox". It takes a second, needs no email address, and gives them an alias like
quiet_forest_owl. - Confirm that alias with them by phone or another channel.
- Enter the alias, attach the document, and send. Your browser encrypts it before anything is transmitted.
- They collect it. Our copy is deleted as soon as their device confirms it decrypted successfully.
Files up to 4 GB, no account for either party, and nothing readable on our servers at any point. What we can see is that a mailbox with a given public key received some number of encrypted bytes — not what they are, not what they are called, not who sent them.
What this does not solve
Being honest about the boundaries:
- Once your recipient has the document, it is theirs. They can forward it, keep it, or lose it.
- If your device is compromised, so is everything on it before encryption ever happens.
- We do not strip metadata for you. Step three is genuinely your job.
The security page sets out the full model, including the parts that are limitations.
For most people, most of the time, the meaningful upgrade is simply: stop emailing them. Everything else on this list is refinement.
Keep reading
Private by design
