DropKey is built for end-to-end encrypted messaging between registered users. Pairwise channels use ECDH + HKDF — and we also support one-time Sends when you need to drop a secret.
Encrypted channel — dev_ops ↔ deploy_svc
Built for teams who take security seriously
ECDH
P-256 key exchange
AES-256
GCM encryption
0
Plaintext on server
HKDF
Conversation keys
Open pairwise encrypted channels with any registered user. Messages are encrypted with per-conversation keys derived via ECDH (P-256) and HKDF. The server relays opaque ciphertext only.
Share passwords and secrets with up to 100 registered viewer names. Set expiry from 1 hour to 30 days. Only listed viewers — plus you — can open a Send.
Capabilities
Every layer is designed so your messages stay yours — from first handshake to auto-delete.
Per-conversation keys derived via ECDH (P-256) + HKDF. Chat messages are encrypted with AES-256-GCM before they leave your browser.
Sends and chat messages are encrypted in your browser before submission. The server stores only ciphertext.
Public key fingerprints let you confirm you are messaging the right person — not an impostor or MITM.
Set message retention from 1 hour to 30 days. Expired messages and Sends are permanently deleted every 30 minutes.
Passkeys, two-factor authentication, and email verification protect who can access your channels.
Strict Content Security Policy, short-lived Valkey sessions, and Laravel encrypted casts at rest for Sends and chat payloads.
Private messaging between registered users. The server relays ciphertext — it cannot decrypt content.
Open Messages, enter a registered user name, and open a pairwise encrypted channel.
Each user gets an ECDH (P-256) key pair in the browser. The public key is registered with the server; the private key stays local.
Messages are encrypted with AES-256-GCM using a per-conversation key derived via ECDH + HKDF.
The server stores and relays opaque ciphertext. It cannot decrypt message content.
A fingerprint of the recipient's public key is shown so you can confirm you are talking to the right person.
Each conversation can be configured to delete messages after 1 hour to 30 days.
From creation to decryption, your secret never touches our servers in plaintext.
Name it, add registered viewer names, write your secret, and pick an expiry between 1 hour and 30 days.
Optional password protection encrypts the message with AES-256-GCM. The key is derived via Argon2id in a Web Worker.
Only registered users whose names you listed can open the Send. You can always view your own Sends too.
Authorized viewers enter the shared password locally. Decryption runs off the main thread — we never see it.
When the timer runs out, the Send is permanently removed. No recovery, no residue.
Security model
DropKey is built on a zero-knowledge model. Chat messages and password-protected Sends are encrypted before they leave your browser. If you lose your local identity key or a Send password, the content cannot be recovered — by design.
| Layer | Protection |
|---|---|
| Client-side E2E | Send and chat content from server operator |
| Laravel encrypted cast | Send & chat payloads at rest |
| ECDH + HKDF | Per-conversation chat encryption |
| Identity key fingerprints | Wrong recipient or key substitution |
| Opaque chat relay | Chat ciphertext stored as-is |
| Passkeys + 2FA | Account access |
| Per-Send viewer ACL | Who can open a Send |
| Valkey sessions | Session hijacking surface |
| Content Security Policy | XSS and injection |
Support
Everything you need to know before opening your first encrypted channel.
No. Chat messages and password-protected Sends are encrypted in your browser before upload. We store only ciphertext and never receive your decryption keys. We cannot recover lost identity keys or Send passwords.
Each user has an ECDH (P-256) identity key pair. Per-conversation keys are derived via ECDH + HKDF, then messages are encrypted with AES-256-GCM. Both parties derive the same key independently.
Only registered users whose names you listed as viewers, plus you as the owner. There are no public links — access is strictly invite-based.
Sends use AES-256-GCM with Argon2id key derivation in a Web Worker. Chat uses ECDH (P-256) + HKDF + AES-256-GCM. At rest, Laravel's encrypted cast adds another layer for Send and chat payloads.
You choose an expiry between 1 hour and 30 days when creating a Send. Expired Sends are permanently deleted by a scheduled task that runs every 30 minutes.
Each user can have up to 15 active Sends at a time, with up to 100 viewer names per Send and a 1,000-character plaintext message limit before encryption.
Accounts support passkeys, two-factor authentication (TOTP), and email verification. Sessions are short-lived and stored in Valkey to minimize hijacking risk.
Yes. Chat and email leave plaintext copies in message history, logs, and backups. DropKey encrypts before transmission, limits access to named viewers, and auto-deletes on expiry.
The secret cannot be recovered. This is intentional — it proves we never had access to the decryption key. Only share passwords through a separate secure channel.
Open your first encrypted channel in minutes. Verify your partner, message with confidence, and let auto-delete handle retention.