Send API Keys and Tokens Securely
API keys pasted into Slack, tickets, or pull requests tend to live forever and leak through search, exports, and integrations. Send them through a link that is deleted from the server as soon as it is opened.
How it works in 3 steps
- 1.Write and create
Encrypted in your browser. The key is kept in the link, not on our server.
- 2.Send the link to one person
Use any app. Opening the link alone does not reveal or delete the note.
- 3.They click Open Note
The note is shown once and deleted from the server right away.
Before you paste a secret
- No account and no recovery: if the note is lost, it is gone.
- Unread notes expire automatically, from read-once (7 days) up to 30 days.
- A destroyed page means the note was opened or expired — Burn Note cannot tell which.
Paste the key, token, or .env snippet below to get a one-time link.
Where secrets usually leak
- Chat workspaces that are searchable by everyone and exported to third-party tools.
- Issue trackers and pull request comments.
- Email threads that are forwarded or archived.
How Burn Note keeps the key out of those places
- The key is encrypted with AES-256-GCM in your browser before anything is sent.
- Only the ciphertext reaches the server; the decryption key stays in the link fragment.
- The note is deleted the first time it is read, so the link in your chat history becomes useless.
Good habits for handing over credentials
- Create a key with the narrowest scope the recipient needs.
- Rotate the key if the recipient reports that the note was already destroyed.
- Prefer a secret manager for long-term storage; use a one-time link for the handoff.
FAQ
- Is there a size limit?
- Notes can be up to 64 KB of text, which is enough for API keys, tokens, certificates, and most .env files.
- Can I post the link in a public channel?
- You should not. Anyone who opens the link first can read the note. Send it directly to the person who needs it.
Back to Burn Note — free self-destructing encrypted notes.