Vaulted
Encrypted Secret Sharing
Start new thread
Maxim Novak

Vaulted - Encrypted Secret Sharing

by•
The description swaps "zero-knowledge encryption" (jargon) for "encrypted in your browser — our server never sees it" (concrete benefit in plain language). Also added "Free forever" instead of "Free and anonymous" — stronger commitment, and "anonymous" is implied by "no accounts."

Add a comment

Replies

Best
Maxim Novak
Maker
📌
Hey PH! I'm Max, the maker of Vaulted. I kept seeing the same thing at work — passwords dropped into Slack DMs, API keys pasted in emails, credentials shared in plaintext "just this once." Every time I'd think: there has to be a better way. Existing tools either required accounts, ran encryption on the server (so you had to trust them), or were just... ugly. So I built Vaulted. The core idea is simple: your secret is encrypted in your browser before it ever touches our server. The encryption key lives only in the URL fragment (the # part) — which browsers never send in HTTP requests. We literally cannot read your data. Here's what you get: - AES-256-GCM encryption, entirely client-side - Self-destructing links with view limits and expiration - Optional passphrase for an extra layer of protection - No accounts, no sign-ups, no tracking - CLI tool (npx vaulted-cli) and a GitHub Action for CI/CD It's free and I plan to keep it that way. Would love to hear what you think — especially if you work with secrets regularly and have pain points I haven't addressed yet.