Expiring links

Expiring file links for sensitive transfers

Expiring file links reduce the amount of time a secure link can be used, which is especially useful for temporary client, vendor, and guest handoffs.

What expiration helps with

Expiration limits future service-mediated access after the intended delivery window closes. It reduces stale links sitting in email, chat, tickets, and browser history.

What expiration cannot do

Expiration cannot delete a file that someone already downloaded and decrypted. Senders should still choose recipients carefully and use short windows for sensitive files.

Account access vs secure links

Account-bound shares are better for known recipients. Secure links are useful for guests, but anyone with the full active link may be able to open it.

Audit and cleanup

A good expiring-link workflow should record lifecycle events, make active transfers easy to close, and archive old sessions or deliveries out of active views.

Frequently asked questions

What makes ZipPigeon useful for expiring file links?

ZipPigeon is useful when a sensitive file needs to reach a specific person without becoming an email attachment or a standing shared-folder permission.

Can ZipPigeon read my file contents?

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.

What metadata is still processed?

Operational metadata such as account information, recipient information, timestamps, file size, delivery state, and audit events may be processed.

Send the file. Keep control of the link.

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