ShareSafeNote

Self-destructing notes and one-time links: when they help, and when they don't

5 min read · updated October 4, 2026

Self-destructing notes sound like a spy-movie gadget, and the name can oversell them. A one-time link doesn't make a secret vanish from the universe; it makes sure the copy stored on the server disappears after one reading, and that a second reading is impossible. Used well, that is very valuable. Used for the wrong job, it creates a false sense of safety, or loses something you needed to keep.

What "one-time" actually guarantees

With one-time access, the default on ShareSafeNote, the note is deleted from the database at the moment it is read. In practice:

  • the note can be read once, by whoever opens it first;
  • after that, the link leads nowhere: an old email, chat message or history entry containing it no longer gives access to the secret;
  • nobody, including us, can retrieve it later: the encrypted copy is gone, and the key was never on the server.

What it does not guarantee is that the first reader is the right person. Its real strength is detection: since only one reading is possible, the intended recipient will notice that someone got there first. If an intruder reads your regular email, you never find out; with a one-time link, they can read the note, but the real recipient will then find it already opened.

If the recipient says "already opened"

Treat it as a compromise, even though there may be an innocent explanation: they opened it earlier on another device, a colleague shares the mailbox, an automated tool clicked through, or someone really intercepted it. From the outside you can't tell which, so assume the worst.

  1. Don't resend the same secret. Change it first: new password, revoked and reissued API key, new door code.
  2. Send the new secret in a fresh note, preferably through a different channel than the first link.
  3. Look for any use of the old one: sign-in history, API logs, active sessions.
  4. Work out which channel leaked. If a mailbox might be compromised, stop using it for anything sensitive.

Same logic if the link never arrives: it may have been lost in a channel you don't control. For an important secret, change it before sending a new one.

Choosing an expiry

One-time access limits the number of readings; expiry limits how long the link stays a live key sitting in an inbox. The options are none, 10 minutes, 1 hour, 24 hours and 7 days. An expired note can no longer be opened and is deleted at the first access attempt after expiry.

  • 10 minutes: you're on the phone or in a meeting with the recipient, who opens it right away.
  • 1 hour: same working session, but they need to finish something first.
  • 24 hours: different time zones, or a "tonight or tomorrow morning" handover.
  • 7 days: the recipient may only see it after a weekend or a vacation. Acceptable for less critical items, but the link sits around for a week.
  • None: rarely the right choice for a secret. With one-time access on, the note still disappears when read, but an unopened link stays valid indefinitely.

Rule of thumb: the shortest delay the recipient will realistically meet. A note that expires too soon takes a minute to recreate.

Link previews and screenshots

Chat apps and some email services visit links automatically to display a preview. With a naive design, that robot could "read" the note before the human does. On ShareSafeNote, the reader page does not load the note when it opens: the note is only fetched when the recipient clicks the decrypt button. A preview that simply loads the page leaves the note intact.

Screenshots are another matter. Once the note is on screen, nothing prevents a screenshot, a photo taken with another phone or a paste into a less safe place. Deletion controls the server's copy, not what the reader does with the text. Tell the recipient where the secret belongs, usually straight into their password manager, and warn them: once they leave the page, the note no longer exists.

Remember: a one-time link doesn't prove the right person read the note. It ensures that if someone else read it, the real recipient will find out.

Good uses, bad uses

Good fits:

  • handing over a password, Wi-Fi key, door code or temporary first-login password (see how to share a password securely);
  • sending an API key or token to a developer (see sharing API keys);
  • moving a recovery code or a config snippet from one computer to another without leaving it in an email.

Poor fits:

  • Long-term storage: notes are meant to disappear, and a lost link cannot be recovered. Long-lived secrets belong in a password manager.
  • Legal or official documents: they need a record (proof of sending, a retained copy, signatures). A one-time note is deliberately designed to leave none.
  • Collaboration: several people editing, commenting, coming back next week is a job for a shared document or a code repository. For showing code live, an encrypted live session exists, but it is temporary too.

A safe routine

  1. Keep one-time access on.
  2. Pick the shortest realistic expiry.
  3. Send the link through a different channel than the secret would have used, and the context separately.
  4. Ask the recipient to store the secret right away.
  5. Confirm they opened it.
  6. "Already opened" or never received? Change the secret, then resend.

The limits, honestly

  • One-time access doesn't identify the reader; it only ensures there is a single one.
  • It can't erase copies made after reading: screenshots, text pasted elsewhere.
  • It doesn't protect a compromised device or a malicious extension, on either end.
  • It doesn't stop you from sending the link to the wrong person: be wary of unexpected requests (see how to recognize phishing links).

Used for what they do well, short-lived secrets passed between two people, one-time links remove a whole category of forgotten copies. Next time, create a note and pick an expiry that matches the handover.

Share your next secret the safe way

Encrypted in your browser, read once, then gone. No account needed.

Create a secure note