Client-side note encryption
Create a secure note
KeyBank keeps the key, not the message. Your note is encrypted in this browser and travels inside the link itself. The server holds only a one-time key, and removes it from active storage when the key is fetched.
Your one-time link is ready
- Sent to KeyBank. Only the key’s ID. The encrypted note stays in the fragment.
- Never leaves the browser. The encrypted note. Browsers do not send anything after
#to a server.
How it works
Store the key, not the message
Most secret-sharing services keep your encrypted message and promise to delete it. KeyBank inverts that: the encrypted message lives in the link you share, and the server keeps only a single-use key.
-
KeyBank creates a key
Your browser requests a fresh X25519 key pair or AES-256 key, with an expiry. ECC creation returns the public half; AES creation returns the symmetric key.
-
Your browser seals the note
Your browser encrypts with AES-256-GCM, deriving a key through X25519 for ECC mode. The ciphertext and public metadata go after the
#, which browsers never send to a server. -
The key can be fetched once
Decrypting fetches the one-time key, and KeyBank deletes it in the same atomic step. It arrives directly over TLS without a passphrase gate. Anyone who records decrypted API traffic can obtain the key. The note is decrypted locally, and the link never works again.
A typical secret-sharing service
- Keeps your encrypted message on its disk until it is read or expires.
- Asks you to trust that it really deletes the message.
- Handles notes of any length.
KeyBank
- Never receives your message, not even encrypted. A stolen key is useless without the link.
- Fetching removes the key from active storage; it cannot be fetched again.
- The note travels inside the link, so it is best for short secrets.