client-side encrypted file transfer
ZipPigeon is built for security-aware teams that want file protection before bytes leave the sender device. Send the package, choose the recipient, and keep the file out of ordinary attachment and shared-folder sprawl.
Client-side encrypted file transfer matters when the file is sensitive enough that "just email it" feels wrong. ZipPigeon keeps the handoff focused: one package, the right recipient, and a clear access window.
Use this page for buyers comparing XChaCha20-Poly1305 client-side file encryption with HTTPS and storage encryption at rest; v3 account delivery separately protects payload keys with hybrid X-Wing recipient envelopes.
The browser encrypts file chunks with XChaCha20-Poly1305 before upload. ZipPigeon stores ciphertext and coordinates recipient access, expiration, revocation, and audit events without needing ordinary readable file contents.
Teams use it for log delivery, customer export transfer, diligence file exchange, private client delivery and similar files where a broad folder permission is more access than the job needs.
The service still processes operational metadata: account and recipient details, timestamps, file size, transfer status, download counts, and audit events. That boundary is part of the security model, not fine print.
ZipPigeon is useful when a sensitive file needs to reach a specific person without becoming an email attachment or a standing shared-folder permission.
The normal delivery model is designed so stored file data is encrypted and raw file keys are not sent to the server. Operational metadata is still processed.
Operational metadata such as account information, recipient information, timestamps, file size, delivery state, and audit events may be processed.
Use ZipPigeon when a file needs to reach the right person without becoming another attachment or shared folder to clean up later.
Open signed-in sender