How it works
Write your note, choose when it burns, then seal it. You get a unique URL. Share that URL — the recipient opens it, reads it, and it's gone.
Security model
Your text is AES-256 encrypted in the browser before touching localStorage. The decryption key lives only in the URL fragment — never sent to any server.
🔑
Password handoff
Send credentials without them sitting in Slack or email history. Burns on first read.
one-time
🛠️
Dev / ops handoff
Pass secrets during a deployment. 5-min timer means the note is gone before you close the terminal.
5 min burn
📋
Sensitive drafts
Share a draft you don't want forwarded or stored anywhere. One read, then gone.
refresh burn
✍️
Private journal
Think in writing without it persisting on any device. Set to burn on exit — leave nothing behind.
no trace
🤝
Client onboarding
Share temp login details with a new client. 24h timer gives them time to log in, then it self-destructs.
24h burn
🔒
Contractor access
Give staging access that expires when the job ends. No hunting old messages to revoke things.
timed access
💬
Off-record message
Say something that shouldn't live in a chat log. Send the link — it burns after they read it.
ephemeral
🧪
Test credentials
Share QA logins that auto-expire when the review window closes. No cleanup needed.
timed
📦
Temp config snippets
Pass env files or config without committing them to version control or a shared doc.
single use
01
You write. Text is encrypted with AES-256 in your browser before anything is saved.
02
Encrypted blob is saved to localStorage. Plain text never touches storage.
03
Decryption key is embedded in the URL fragment only — never sent to a server.
04
On burn: the blob is deleted. Without the key, the ciphertext is meaningless.