Plain language, and accurate
Privacy Policy
This page explains, in plain language, what happens to a photo you resize with this tool, and what (if anything) this site collects about your visit. The short version: resizing happens entirely in your browser, nothing you upload is sent to a server, and there is no account, no sign-up, and no tracking cookie.
What happens to the photos you resize
Every photo you choose on the image resizer is decoded, redrawn at the new size, and re-encoded entirely inside your browser's own drawing engine (the Canvas API). It is never uploaded to a server, never logged, and never stored anywhere outside your own device. This is a direct, verifiable consequence of how the tool is built: it is a static site with no backend database and no server-side image processing. There is no infrastructure on this site's end that could receive, log, or store a photo you select, even if someone wanted it to.
The same applies to every reference page on this site: the size presets page and the resizing guide are static content, served the same way to everyone, with no per-visitor processing at all.
Nothing is stored between visits
Unlike some tools on this site's template family that save a text field to local storage for convenience, this resizer does not keep any record of a photo you've selected once you leave or refresh the page. Each visit starts from an empty tool: choosing a photo, resizing it, and downloading the result all happen within that single page session, and nothing about the photo persists afterward.
The feedback button
Below the tool is an optional 'Was this tool helpful?' control. Clicking it sends a small, anonymous signal (just a thumbs up or thumbs down count, with no identifying information, no IP address, and no cookie) to this site's own backend, purely so the count can be tallied. A local flag remembers that you already voted, so you are not prompted repeatedly on later visits, but that flag identifies nothing about you personally; it only prevents a duplicate vote from the same browser.
Analytics
If this site has Cloudflare Web Analytics enabled, it uses a cookie-free measurement approach: Cloudflare's own privacy-first analytics product does not set tracking cookies, does not fingerprint visitors, and does not track individuals across other websites. It reports aggregate figures only, such as total page views, and no consent banner is required for this kind of tool precisely because it does not track individuals the way conventional cookie-based analytics do.
No accounts, no email collection
There is no sign-up form anywhere on this site, no password, and no email address is collected as a condition of using the resizer. The only way an email address reaches this site at all is if you choose to write to the contact address below on your own initiative, in which case ordinary email applies (the message sits in an inbox until it is read and, eventually, deleted or archived, the same as any other email you send).
Third parties
This site does not sell, rent, or share any data with third parties for advertising or marketing purposes, because it does not collect the kind of personal data that would make that possible in the first place. The resize itself runs entirely inside your browser's built in Canvas API; no third-party server or library is involved in processing a photo you select.
Children's privacy
This site does not knowingly collect personal information from anyone, including children, and by design has no sign-up flow through which personal information could be submitted in the first place.
Changes to this policy
If this policy changes, the updated version will be posted on this same page. Because this is a small, single-purpose tool with a simple, static architecture, changes here are expected to be rare and are typically limited to reflecting an actual change in how the site is built (for example, if an optional analytics or feedback feature is added, removed, or changed) rather than shifting terms retroactively.
Why the tool is built this way
Running the resize entirely client-side was a deliberate design choice, not just a convenience. A personal photo is exactly the kind of file people reasonably expect to keep private, and building the tool so it is architecturally incapable of seeing that file (rather than promising not to look at data it could technically collect) is a stronger guarantee than a policy statement alone. It also happens to make the tool faster, since there is no upload or download round trip to a server for every resize.
How this compares to an upload-based resizer
Many image resizing websites work differently: you upload a photo, a server somewhere resizes it, and you download the result from that server, which means your photo briefly (or sometimes not so briefly) exists on a computer you don't control. That approach isn't necessarily unsafe, but it does require trusting whatever that site's own privacy policy promises about deleting the file afterward. This tool sidesteps that trust question entirely by never having a server-side step in the first place: there's no upload to complete, no processing queue to wait in, and no deletion policy needed, because there's nothing on a server to delete.
Contact
Questions about this policy, or about the site generally, can be sent to contact@imageresizerpro.xyz. This is a small, independently run tool, so replies may take a little while, but every message is read.