Security
How the site is built to keep your files and your visit safe.
The strongest security decision ImgCruncher makes is structural: the tools do their work in your browser, so your images never travel to a server in the first place. You cannot leak what you never receive. This page covers that and the rest of how the site is kept safe.
Your images stay on your device
Every tool here processes your file locally using the browser Canvas and FileReader APIs. The image is read into your browser's memory, worked on, and handed straight back to you. It is never uploaded, stored, logged or seen by us. You can prove it: open your browser's network tab while using a tool, or switch off your internet after the page loads, and the tool keeps working because there is nothing to send.
Encrypted connection
The whole site is served over HTTPS, so the pages, scripts and styles you download cannot be tampered with in transit. Requests to the plain HTTP or www address are redirected to the secure canonical address.
No accounts, no passwords
There is nothing to sign up for, so there are no passwords, no stored personal profiles, and no account database that could be breached. The only thing the site remembers about you is your cookie choice, kept in your own browser.
Limited third-party code
The site keeps external scripts to a minimum. Advertising is served by Google, and a few tools load a well-known open-source library from a public CDN to do their job, such as a PDF renderer or a ZIP builder. These run in your browser like the rest of the tool and still do not send your images anywhere.
Reporting a vulnerability
If you find a security issue, please tell us privately so it can be fixed before it is made public. Email support@imgcruncher.com with the details and steps to reproduce it. We read every report, we will confirm we received it, and we are grateful for responsible disclosure. Please do not run automated attacks, test denial-of-service, or access data that is not yours while investigating.
What we ask of you
Keep your own browser and operating system up to date, since the security of an in-browser tool depends partly on the browser running it. And remember that once you download a file and share it elsewhere, its safety is in the hands of wherever you send it next.