Privacy Policy
Your images stay yours
Squeeze is built to be private by default. This page explains, in plain terms, exactly what happens to your images and data depending on which feature you use.
Last updated: August 4, 2026
How your files are processed
Single-image compression on the homepage, URL-fetch, bulk compression, Image Downloader, and other image tools send data to the Squeeze backend for processing. Compression and most tools keep images only in memory while processing. Image Downloader may briefly store extracted files in a temporary session folder so you can preview and select images; that session is deleted after ZIP download or when it expires.
- No permanent image archive, gallery, or database of your files.
- Temporary Image Downloader files are removed after download or session expiry.
- Image Downloader only fetches publicly accessible media — it does not bypass login or private content.
No accounts, no tracking
Squeeze has no accounts, no login, and no tracking cookies. We don't use analytics that identify you, and we don't build profiles.
The only thing we count is an anonymous compression counter shown on the homepage — a single running total of how many images have been compressed. It is not tied to any user, device, IP address, or individual file.
Third-party requests (URL fetch)
When you use the URL-fetch feature, the backend makes an outbound request to whatever URL you provide to retrieve the image. We apply SSRF protectionsthat block requests to private, internal, or otherwise restricted network addresses, so the feature can't be used to reach machines that aren't public.
Only fetch URLs you have the right to access. The content of those third-party sites is governed by their own policies, not this one.
Contact
Squeeze is an independent project with no company behind it. Questions about this policy or how your data is handled? Reach out via GitHub.
Looking for quick answers? Read the FAQ or start compressing.