Is it safe to email a photo of my ID or passport?

No — an emailed image sits in two inboxes indefinitely, plus their backups, and either account being breached years later exposes it. If a document is truly required, use a protected, expiring link instead, send any password over a different channel, and delete both ends when it's done.

Is texting sensitive information safer than emailing it?

Sometimes marginally — some messaging apps are end-to-end encrypted — but the real problem is the same: the message becomes a permanent copy in backups, previews, and the other person's device. The channel matters less than the fact that the copy lives forever.

What is the safest way to send a document someone insists on?

A protected link you can expire or revoke beats an attachment that lives forever. Password-protect the file, send the password over a second channel, redact anything the recipient does not need, and delete your copies — camera roll, downloads, sent items — afterward.

How do I share a password with a family member safely?

Not by text or email — those copies persist in plain sight. Use a password manager or encrypted vault with per-person sharing, so access is scoped and revocable. If you already shared one in plain text, change the password after.

What should I do if I already sent my SSN or ID over email?

Delete the message on both ends where you can, watch your statements, and consider a credit freeze — it is free and blocks new accounts in your name. Going forward, share the specific number a form needs rather than an image of the whole document.

How to share sensitive information safely

The everyday risk

The babysitter needs the insurance card. The lender wants a W-2. The new landlord asks for "a quick photo of your ID." So you do what everyone does: snap a picture, hit send, move on. Nobody meant any harm — and that's exactly what makes this the most ordinary risk in your digital life.

The problem isn't the person you sent it to. It's that every send creates a copy you no longer control — one that doesn't expire, lives in places you'll never see, and can't be taken back. Here's why the usual channels are riskier than they feel, and the small set of habits that covers almost all of it.

The problem

Where the copies end up

Send a document the usual way and it quietly multiplies — and not one of these copies can be expired, tracked, or taken back. The send is instant; the exposure is permanent.

Sits in two inboxes indefinitely — plus their backups. One breached account, years from now, and your ID is part of the haul.

Texts & chat apps

Synced to clouds, backed up to devices you've never seen, and sitting in a thread anyone borrowing the phone can scroll.

Camera rolls

The photo you took "just to send it" lives on — auto-backed-up, synced, and carried into every phone you'll ever migrate to.

Shared drives & links

"Anyone with the link" means anyone, indefinitely — links get forwarded, and shared folders outlive the reason they existed.

What safe sharing means

A handover, not a broadcast.

You don't have to refuse — life means handing things over. Safe sharing just keeps four things true. A texted photo keeps none of them.

→Only the intended person can open it. Encryption, not an open channel.
→They get only what they need. The field, not the file.
→It doesn't live forever. You can expire or revoke it.
→You know what's out there. A record, not a guess.

The playbook

Five habits that cover almost everything

In order of how often they'll save you.

Share the field, not the document. Most requests need a value — the policy number, the account digits, the date — not an image of the whole card. Read it over the phone or type the number itself, and the sensitive artifact never leaves your hands.

If it must be a file, make it expire. A protected link you can revoke beats an attachment that lives forever. Password-protect the file and send the password over a different channel than the link.

Strip what isn't needed. Crop and redact before sending: cover the SSN if they only need the income line, send the front of the card if the front is enough. The recipient loses nothing; you lose less if it leaks.

Delete your copies afterward. The photo in the camera roll, the scan in Downloads, the sent attachment — the transaction ended, and the copies shouldn't outlive it. This one habit quietly shrinks years of accumulated exposure.

Keep the originals somewhere built for sharing. One encrypted place that shares by field, per person, revocably — so next time you share from the vault, not the camera roll, and nobody else can read what's stored.

Before you hit send

Three questions and one red flag

A ten-second gut check before anything sensitive leaves your hands.

"Could I share a number instead of an image?" If yes, do that — it's faster than it sounds and removes most of the risk.

"Can I expire or take this back later?" If the channel has no answer to that, it's the wrong channel for anything sensitive.

"Would I be fine if this exact message surfaced in three years?" Because that's the realistic lifespan of a sent copy.

The red flag: anyone pressuring you to send an ID, SSN, or bank details right now over text or email. Urgency plus sensitive data is the signature move of a scam — real institutions have secure portals and can wait an hour.

Where Simply Once fits

Sharing is the reason Simply Once exists — done the way this whole guide wishes it worked. The babysitter gets exactly tonight's card; the lender gets exactly the field it asked for: scoped per person and per detail, revocable any time, with a record of who has what — and zero-knowledge encryption means what you store is readable by you and the people you choose, and no one else. Ever.

Part of our guide to organizing your family's important information →