Request secrets without email risk
Generate a link and send it to anyone. They submit their secret through an encrypted form. Only you hold the decryption key — not even the sender can re-read what they submitted.
How it works
Four steps. Four seconds each.
Generate link
Your browser creates an encryption keypair. The private key stays in this tab; the public key goes into the link.
Send to someone
Share the link via Slack, email, SMS — any channel. The recipient doesn't need an account or any install.
They submit the secret
The recipient fills a form. Their browser encrypts the contents using the public key before submission. Our server stores ciphertext only.
Only you decrypt
Open the response in this tab. Your private key — which never left your browser — decrypts the secret. Even the sender can't re-read it.
Real workflows
Where teams actually use this
HR asks an employee for bank details
Onboarding requires the new hire's account number and IFSC. Send a Secure Receive link instead of a Google Form that stores PII in a spreadsheet.
Client sends server credentials
Agency onboarding needs WordPress admin, FTP, and Stripe keys. One link collects all of them — encrypted before submission, no inbox trail.
Contractor submits API keys
Day-one access requires their personal CI tokens. The contractor pastes them into the form once; you retrieve them once; the link dies.