The Case for Ephemeral File Sharing: Nothing Left Behind
Most software defaults to persistence — save everything, keep a history, make it searchable later. That default is so pervasive it rarely gets questioned. It's worth making the case, deliberately, for the opposite default when the task genuinely doesn't call for it.
Persistence became the default almost by accident
Storage got cheap enough, fast enough, that keeping everything became easier than deciding what to delete — and so most tools quietly settled on keeping a copy of everything, indefinitely, by default. Not because every use case actually needs that, but because building a system that forgets on purpose takes more deliberate design than one that simply never throws anything away.
What persistence quietly costs
Every stored copy is something that now has to be protected for as long as it continues to exist: a bigger attack surface for a future breach, a data-protection liability that sits there whether or not anyone ever looks at it again, a thing someone is eventually supposed to remember to delete and, in practice, very often doesn't.
Not every transfer needs a history
Sending a document to one specific person, right now, is a complete and self-contained task the moment it arrives. There's no obvious benefit to a permanent record of that handoff existing anywhere once both people already have what they needed — the value of the transfer was in the moment it happened, not in a durable log of it.
What 'ephemeral' actually means here
Once a direct transfer completes, there's no copy sitting on a server waiting to be breached, subpoenaed, or simply forgotten about on some old backup. The file exists on the sender's device, briefly in transit across an encrypted connection, and on the receiver's device — and nowhere else that either of them didn't already fully control before the transfer even started.
A useful mental model: a phone call, not a mailbox
A phone call happens, and then it's over — nobody expects the phone company to keep a permanent, searchable recording of every call by default. A mailbox, by contrast, is built to hold things indefinitely until someone comes to collect them. Most file-sharing tools quietly model themselves on the mailbox. A one-off handoff between two specific people is much closer, in shape, to the phone call.
When you actually do want a record
This isn't an argument that persistence is always wrong — a shared team drive, a photo backup, a document you'll want to find again next year, all genuinely benefit from being kept. The point is narrower: those are different tasks from a one-off handoff, and they deserve a tool built around persistence on purpose, not a transfer tool that happens to keep a copy because that was simply the easier default to build.
This is a deliberate trade-off, not a missing feature
The honest cost of an ephemeral transfer is real: no built-in history to browse later, no re-downloading a file you already sent from some other device down the line. For a one-off handoff, that's rarely an actual loss. For anything you'll genuinely want to find again in six months, this deliberately isn't the right tool for that job — and that's a feature of the design, not an oversight in it.
Related reading
Secure Transfer Does Sending a File Ever Touch a Server? A Plain-English Breakdown What GDPR and Data-Minimization Actually Require From File-Sharing Tools