Essential sign-in cookie
ZipPigeon uses an HttpOnly session cookie after sign-in. It keeps you signed in, supports workspace security, and is cleared when you sign out. In production it is sent only over HTTPS and uses SameSite=Lax.
Cookie policy
How ZipPigeon uses cookies
Learn which essential cookies and browser storage ZipPigeon uses for sign-in, security, file delivery, and saved preferences.
Email verification cookie
A short-lived HttpOnly cookie can keep an email verification flow tied to the same browser. It expires automatically and is cleared when the flow ends.
No advertising cookies
ZipPigeon does not currently set advertising or cross-site marketing cookies. Essential cookies are required for sign-in and account security, so there is no marketing-cookie consent switch.
Bot protection
Some public forms can load Cloudflare Turnstile when bot protection is enabled. Cloudflare may process browser and network signals needed to check the request.
Browser storage is separate
The app also uses local browser storage for settings, device keys, security hints, and short guest sessions. This data is not a cookie. Clearing site data can remove it and may require you to sign in or restore keys again.
Your choices
You can block or clear cookies in your browser. Blocking essential cookies will stop account sign-in from working. Signing out clears the active ZipPigeon session cookie.
Questions
Contact privacy@zippigeon.com with questions about cookies, browser storage, or privacy.
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.
Open signed-in sender