As developers, we often need to share sensitive information:
- A database password
- An API token
- A temporary secret for a teammate
Unfortunately, the common ways we share them—email, chat, cloud notes—leave permanent traces. Once it’s out there, it’s no longer under our control.
The Problem
- Email: gets archived and backed up
- Chat apps: messages live forever in history
- Docs: links may stay active longer than intended
For sensitive information, this creates unnecessary risk.
The Solution: One-Time, Encrypted Links
I built a small tool called ViewOnce.link to address this.
How it works:
- Paste your sensitive text (password, token, or secret note)
- It’s encrypted with AES-256 in the browser
- You set a password (only you and the recipient know it)
- A one-time link is generated
- Once opened with the correct password, the message is shown and then destroyed
Why It’s Different
- Zero storage: the original text and password are never stored on the server
- Zero knowledge: only someone with the password can decrypt
- One-time access: the link expires after use
Use Cases
- Safely share database credentials with teammates
- Send temporary access codes without leaving traces
- Pass confidential notes in a way that self-destructs
Try It Out
Check out the demo here: https://viewonce.link
I’d love feedback from the dev community:
- Does this fit into your workflow?
- Any suggestions to improve security or usability?
- Are there integrations (e.g., CI/CD, Slack bots) you’d find useful?
Closing Thought
Sharing secrets should be as easy as pasting text, but as safe as possible.
One-time encrypted links are one step toward that.
Top comments (0)