Burn after reading. The phrase comes from spy movies, but the concept is older than cinema. Some messages are meant to be seen once. Then destroyed.
A self destructing url brings that idea to the web. You share a link. The recipient opens it. The content appears. Then the link dies. Nobody else can open it. Not the person who forwards it. Not the server admin. Not anyone.
What a One-Time Link Solves
Consider a developer sharing an API key with a teammate. She could send it in Slack. Slack stores messages indefinitely. She could email it. Email sits in sent folders and backups. She could paste it in a code review. Code reviews are archived.
Every channel retains. A one time link does not.
She creates a self-destructing link containing the API key. She sends the link in Slack. Her teammate clicks it. The key appears on screen. The link is now dead. If someone scrolls through the Slack history next week and clicks the link, they see "This link has been viewed and is no longer available."
The key was seen exactly once by exactly one person.
How It Works Under the Hood
When you create a temporary link generator link, two things are stored. The slug, which is the short identifier. The encrypted content, which is what the recipient will see.
When someone opens the link for the first time, the server decrypts the content, serves it to the browser, and immediately deletes the record from the database. The slug and content are both gone.
The second request to the same URL returns a 410 Gone. There is nothing to serve. The data does not exist anymore.
This is different from a link that expires after a time period. A time-based expiry keeps the data alive until the clock runs out. A one-view link is dead the moment it is opened. Time is irrelevant.
Use Cases
**Credentials sharing.** API keys, database passwords, SSH keys. Send them once. They are consumed once. No retention.
**Confidential messages.** A lawyer sends case details to a client. The client reads them. The link expires. No copy lives in the client's email archive.
**Two-factor codes.** A support team sends a one-time access code via a self-destructing link. The code is used once and the link is already gone.
**Sensitive screenshots.** You need to share a screenshot of a bug containing user data. Upload it, wrap it in a one-time link, send it. One developer sees it. Then it is gone.
What One-Time Links Are Not
They are not a replacement for end-to-end encryption. If the network is compromised, the content can be intercepted in transit. Always use HTTPS. NovelCrypt's links are HTTPS by default.
They are not anonymous. The server sees the IP of the person who opens the link, briefly, during the request. If you need anonymity too, combine it with a no-logging policy.
They are not screenshot-proof. The recipient can take a screenshot of the content before the link self-destructs. Technology cannot prevent that. You are trusting the recipient, not the link, for ongoing secrecy.
Building a Self-Destructing Link
In NovelCrypt's URL shortener, select "Self-destruct after one view." Paste your content or destination URL. Click generate.
You get a link like novelcrypt.com/burn/aB3xK9. Send it. The first person to click sees the content. Everyone after sees the expired message.
You can combine this with password protection for extra security. The recipient needs the link and the password. They enter the password, see the content, and the link dies. Two factors, one view, zero retention.
The Psychology of One-Time Links
There is something about knowing a link will disappear that changes how people interact with it. They pay attention. They read carefully. They screenshot if they need a copy.
This is the same effect as Snapchat's original pitch. Ephemeral content demands presence. You either see it now or you miss it.
For important information, that is a feature. You want the recipient to focus. A self-destructing link signals "this matters, read it now."
When to Use What
Use a regular short link for public content. Blog posts, landing pages, marketing campaigns.
Use a password-protected link for semi-private content shared with a known group. Client deliverables, team documents.
Use an expiring short link for time-sensitive content. Event registrations, limited offers, embargoed press releases.
Use a one-time link for secrets. Credentials, confidential messages, anything that should be seen once and never again.
The self-destructing link tool handles all four. Pick the mode that fits your scenario.
A Note on Trust
You are trusting the shortener to actually delete the data. A dishonest service could keep a copy. This is why the architecture matters. NovelCrypt deletes the database row synchronously during the redirect. There is no async queue, no backup delay, no soft delete. The row is gone before the response is sent.
If you want to verify this, create a one-time link, open it, then try opening it again. The second request returns 410. The data is not there. It cannot be there. The delete happened before the redirect completed.
Self-destructing links are a small tool with a specific job. They make secrets ephemeral. Use them for anything that should not outlive its usefulness.,