sg-send-encrypted

Zero-knowledge encrypted file transfer encrypts files client-side using AES-256-GCM before uploading them. The server never sees the plaintext, ensuring the payload remains confidential while generating a secure download link.

To send a file securely with AES-256-GCM encryption, provide the payload and choose optional email delivery. The system wraps it in an SGMETA envelope, encrypts it, uploads it via MCP, and returns a verified download URL.

Yes, you can send a secure file download link via Sherpa WorkMail. After the zero-knowledge encrypted file transfer completes, the system can optionally deliver the share link directly through Sherpa WorkMail.

Yes, zero-knowledge encryption prevents the server from reading your files. By wrapping the payload in an SGMETA envelope and applying AES-256-GCM encryption client-side, the plaintext data stays completely inaccessible to the server.

An SGMETA envelope is used in secure file sharing to wrap the payload before encryption. It structures the data for AES-256-GCM encryption and subsequent MCP upload, ensuring transfer integrity and proper key fragment generation.

To verify transfer integrity before sharing an encrypted download link, the system validates the upload via the SG/Send MCP. It generates a download URL with a key fragment only after confirming successful transfer.