Encrypted in your browser

Send a Secret

Email and chat systems can keep copies of pasted credentials indefinitely. Encrypt yours here first: the secret is encrypted in your browser against my published PGP key, and only the encrypted block ever leaves your machine.

API key, password, token, connection string. Stays in this browser tab.

Only the private key matching the fingerprint below can open this. Send it by email, Slack, WhatsApp, a ticket comment, anything.

A .env file, keystore, service-account JSON or export, up to 100 MB. Read in this browser tab and saved as an encrypted .gpg file you send instead.

What happens to your secret

  • It never leaves your browser. This page's code never sends your secret anywhere. Encryption happens in the tab you are looking at.
  • Only the matching private key opens it. That key lives on Jayen Ashar's machine and never on this website.
  • The channel no longer matters. Once encrypted, the message is safe to paste into email, chat or a ticket, all of which can keep copies indefinitely.
  • Rotate anyway when you can. Sending a credential you can revoke later is always safer than sending one you cannot.

The public key

Check the fingerprint against a copy you got some other way before you trust it, then verify with Jayen Ashar over a call or a channel that is not the one carrying the secret.

Identity
Jayen Ashar
Fingerprint
D82E 8ECA 3915 1787 2831 3511 CC34 98D6 F149 EDBB
Key type
Ed25519 certification key (19 January 2026) with a Curve25519 encryption subkey and an Ed25519 signing subkey
Show the armored public key
-----BEGIN PGP PUBLIC KEY BLOCK-----

mDMEaW4OPRYJKwYBBAHaRw8BAQdA/35HFbwzEoRWvThtFHuWUKJW/Fpy+mTEYvBv
o5upmf+0IkpheWVuIEFzaGFyIDxqYXllbkBqYXllbmFzaGFyLm9yZz6IkAQTFggA
OAIbAQULCQgHAgYVCgkICwIEFgIDAQIeAQIXgBYhBNgujso5FReHKDE1Ecw0mNbx
Se27BQJpbg8GAAoJEMw0mNbxSe2711YBAJLU14jWExm2JLrC+KzrnARJX7flDJoy
hW1FgG53iCJ4AQCE1lshQasGGB7oiQg5sLFGvxbS0R05cp62G1EqVf6uBrg4BGlu
DtoSCisGAQQBl1UBBQEBB0AGGJhYUBRYrsQnWO8ORViSXG75uj+ogwNvtsfJWn9n
ewMBCAeIeAQYFggAIAIbDBYhBNgujso5FReHKDE1Ecw0mNbxSe27BQJpbg8PAAoJ
EMw0mNbxSe27kNgA/1QZa2UsC4QSBo1CVZ38wFJCpWr/tbujvQrMaZh4ElKMAQDo
YuMXsnmQikfEU70OXP44mvuISWTM41D+z5zL5cq+CLgzBGnuEPMWCSsGAQQB2kcP
AQEHQGgNXaH59Tj3l5GteucwttVoob6xbvd9FLpJf7JipQOLiO8EGBYIACAWIQTY
Lo7KORUXhygxNRHMNJjW8UntuwUCae4Q8wIbAgCBCRDMNJjW8Untu3YgBBkWCAAd
FiEEtmY5VazIrK8YwEiZEOwjtqOL5WUFAmnuEPMACgkQEOwjtqOL5WV4VgEA+ZUW
7xO7F/wb68V+lFQ/N8SvddJtaKe92jO1aRPGxDEA/jHz5zgxOLQB6T+EyGWA4jEZ
WNrOHIC5GTcXloBz2ncA17kBAJ2bsa2rB+L433hFQLnfBmErircD0gAd/0Fg7kkN
zpdOAP95VudIejqdCeyOFfTem0TtsMtOWbov9RRB7kpoixIeAA==
=SNh4
-----END PGP PUBLIC KEY BLOCK-----

Prefer your own GnuPG?

Import the key above, then encrypt locally:

gpg --import jayen-ashar.asc
gpg --armor --recipient CC3498D6F149EDBB --encrypt secret.txt
gpg --recipient CC3498D6F149EDBB --encrypt credentials.zip

Send the resulting secret.txt.asc or credentials.zip.gpg the same way.