Secure file transfer

The receiver gets a unique link. Their browser generates a keypair — you verify the fingerprint before encrypting. The relay never sees the key.

Your API key

API key

Enter your API key to continue

File

Select file(s) — select multiple for vault mode

No file selected

Self-destruct

Link expires after

Relay permanently deletes blobs after expiry

Share this link

Send this link to the receiver. Their browser will generate a keypair. You'll see their fingerprint appear below — verify it with them before sending.

Waiting for receiver...

One-time session link

Share this link with the receiver

Encrypting & sending

File is being encrypted with the receiver's ML-KEM-768 public key. The relay will never see the plaintext or the key.

Upload progress

Initializing...

Downloading…

Decrypting file — key never left your browser.

Secure FileLink Download

Fetching encrypted chunks…

AES-256-GCM Key in URL fragment — relay never saw it Burn-on-read

Sent.

The receiver can now download the file. After one download it is permanently destroyed.

Transfer complete

—

ML-KEM-768 Burn-on-read Fingerprint verified Relay never saw key