Encrypted before upload
The secret is encrypted in the browser. What reaches the server is ciphertext stored in Postgres, not the message itself.
bQuick Secret
bQuick Secret is a privacy-first way to send a one-time secret. It is encrypted in the browser before upload, stored as ciphertext, and decrypted only in the recipient’s browser with a key the server never receives.
Browser-side encryption
Free to use
MIT licensed
Plaintext never leaves the device. The link you share carries the key in a URL fragment the backend does not see.
The secret is encrypted in the browser. What reaches the server is ciphertext stored in Postgres, not the message itself.
Decryption uses a URL fragment key. The API never receives that fragment, the decrypt key, or the plaintext.
A notification email points at the secret without the key. You share the full secure link, including the fragment, on a separate channel.
Plaintext, passphrases, recipient emails after send, and full URLs with fragments are not stored or written to logs.
bQuick Secret is a free product of Binary Quest Limited. Open it in the browser — there is nothing to install.
The web app, Go API, and database migrations are published under the MIT License.
Open secrets.bquick.io and enter the secret. Encryption happens on your device before anything is uploaded.
The API stores the encrypted payload. It does not receive the fragment key needed to read it.
Send the secure link, including #key, through a channel you trust. The email notice, when used, is keyless on purpose.
bQuick Secret runs in the browser. The source is public if you want to read or self-host it.
It stores ciphertext. The decrypt key lives in the URL fragment, which the backend never receives.
The notification email is keyless. You still need to share the full link, including the fragment key, yourself.
No. bQuick Secret is a browser app. Use the live site, or build it from the public repository.