Confirm the recipient
Check the recipient address, account identity, or secure-link delivery path. For high-risk files, verify the recipient through a second channel before sending.
Checklist
Use this checklist before sending contracts, client files, tax documents, HR paperwork, logs, incident evidence, or other sensitive files.
Check the recipient address, account identity, or secure-link delivery path. For high-risk files, verify the recipient through a second channel before sending.
Use account-bound access for known recipients when identity matters. Use secure links when low-friction guest access matters, and treat the link like a private credential.
Prefer tools that explain where encryption happens, how file keys are handled, and whether the service receives readable file contents during normal delivery.
Do not put unnecessary secrets into filenames, notes, titles, email subjects, labels, or other fields that may remain operational metadata.
Choose a short access window, cancel or archive transfers when done, and remember that expiration stops future access but cannot recall completed downloads.
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.
Send a private file