KeyBank

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 the active database when fetched. Cloudflare backups can retain earlier database state.

Stays in this browser

Short notes make short links.

Both encrypt your note locally. ECC uses a public key; AES uses a fresh symmetric key.

Link expires after

Or the first time it is opened, whichever comes first.

Only key type and expiry are sent to the API. Your message stays here.

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.

  1. 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.

  2. 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.

  3. 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. Anyone who records decrypted API traffic can obtain the key. The note is decrypted locally, and the API will not return the key 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.
  • Reading the note is what deletes the key: fetch and delete are one step.
  • The note travels inside the link, so it is best for short secrets.

This is a long note

This note is larger than 100 KB once encoded as UTF-8. That can make the final share link unwieldy.

The encrypted note lives inside the link, so a long note means a long link. You can continue, but it may be hard to copy, scan, or open on every device.