A few months ago, a teammate pinged me asking for a file from an old Slack thread. The link still worked — from a project we'd wrapped up seven months earlier. No one had revoked it. It just existed, quietly accessible to anyone in that channel.
The file wasn't sensitive. But it easily could have been.
The Problem with Permanent Links
Most file sharing tools default to forever. Upload, get a link, send. Done. But that link doesn't go anywhere — it lives in Slack histories, email inboxes, browser bookmarks. Every day it exists is another day something could go wrong.
Think about what you've shared: log files with internal endpoints, staging builds for one person, config files "just this once." None of those were meant to be permanent. But they probably still are.
Why Ephemeral Sharing Should Be Your Default
Persistent links are quiet backdoors. Once a link is out there, you don't control who has it — it gets forwarded, copied, saved. And with tightening data privacy regulations (GDPR, CCPA), ephemeral sharing is becoming a compliance expectation, not just a best practice.
The question shouldn't be "should I set an expiry?" — it should be "why wouldn't I?"
What I Built
I wanted no-account, end-to-end encrypted, auto-expiring file sharing. I couldn't find exactly what I needed, so I built SimpleDrop.
Upload a file, get an encrypted link, send it. The file exists as long as it needs to — then it's gone.
Permanent should be opt-in. Temporary files deserve temporary links.
Have you run into problems with old shared links? Drop a comment below.
Top comments (0)