Privacy Policy

How your images are handled

When you load an image, the browser creates a temporary local URL with URL.createObjectURL and releases it as soon as the Image object has decoded. Resizing, cropping and encoding then happen entirely inside a Canvas 2D context, and the result becomes a download through canvas.toBlob(). The icon forge assembles its .ico bytes in memory before handing the file over the same way.

No step in that chain writes pixel data into a network request. You can verify this yourself: open the Network panel in developer tools and filter for images — apart from the site's own static assets, none of your files appear. Disconnect the network and already-loaded images still crop and export.

One caveat: images live only in the current tab's memory. Refreshing, closing the tab or opening another one lets the browser reclaim that memory. There is no server-side copy to delete and no backup to recover — download anything you want to keep.

What we do not collect

Item by item:

• Your image files are never uploaded, cached or copied to any cloud location.
• File names, pixel dimensions and EXIF data (capture device, aperture, shutter, GPS coordinates) are neither read nor recorded.
• The only third-party script is Google Analytics 4, which counts page views. It starts with storage denied and stays that way unless you allow it. No heatmap, session-recording, advertising or A/B testing script is loaded, and there is no third-party font CDN.
• No sign-up or login exists; we do not collect email addresses, phone numbers, nicknames or any other identifying information.
• No device fingerprinting, no cross-site tracking, no user profiling.

The only exception is when you choose to email us — then we see what you wrote, handled under the retention rules below.

What is stored in your browser

One localStorage key holds your colour-theme choice: ssc-theme, containing light or dark. It stops the page re-detecting the system preference every time, contains nothing identifying, and disappears when you clear this site's data in your browser settings.

A second key, ssc-consent, holds your answer to the analytics banner (granted or denied) so the same question is not asked twice. Decline and no analytics cookie is ever created; allow and Google Analytics writes _ga and _ga_8VQHB6JZC7.

Nothing else is written to localStorage, sessionStorage, IndexedDB or cookies. When the home page hands an image to the converter it uses a module-level variable inside the same in-page navigation — nothing is persisted or written into the URL, which is why a new tab or a refresh asks you to pick the file again.

Hosting platform and access logs

This is a purely static site with no backend or database of its own; pages are served directly by a static hosting platform and its CDN. In that architecture the provider may keep access logs as an industry norm — IP address, user agent, request time, path and response status. That data is handled and retained by the platform under its own privacy policy; we do not read it, export it, or correlate it with individual visitors.

Cookies and third-party scripts

Our own code sets no cookies. Third-party code is limited to one service and is gated: Google Analytics 4 loads with storage denied, so a first visit writes no cookie and sends no identifier. Only after you press “Allow” does it write _ga and _ga_8VQHB6JZC7. If the hosting platform issues a technical cookie for security (blocking abusive requests, DDoS mitigation), that cookie is handled under the platform's policy; we neither read it nor use it for analytics.

• Provider: Google Analytics 4 (Google LLC), served from googletagmanager.com.
• What it sends: page path, referrer, approximate location derived from the IP address (the IP itself is not stored), device and browser, language, and a random client ID.
• What it never receives: your images, their file names, EXIF data, or anything you type into a tool — none of that leaves the browser.
• Retention: event data follows the property's retention setting, 14 months at most.
• Opting out: press “No thanks” in the banner, clear ssc-consent and the _ga cookies from this site's data in your browser, or install Google's Analytics opt-out browser add-on.

Adding any further third-party service would be announced on this page first, with the same details, before it goes live.

Outbound links and third-party content

Pages may link to other sites — for example the official documentation behind a platform's published specs. Following such a link takes you off this site, and any cookies or data processing afterwards falls under that site's privacy policy rather than this one. No third-party iframes, video players or social-sharing SDKs are embedded here.

Your rights

Under the PRC Personal Information Protection Law, the GDPR, the CCPA and comparable regimes, individuals may access, copy, correct and delete their information, withdraw consent and request portability. Because this site creates no accounts and retains neither images nor identity data, everything except the optional page-view counts described above stays on your own device — decline those counts and there is nothing about you to request at all. Consent is withdrawn at any time by clearing ssc-consent.

If you still want to make a formal request (for instance written confirmation that we hold nothing about you), email hello@imagesize.pro and we will reply within a reasonable period. Exercising any right never affects your ability to keep using the site.

Retention and deletion

• Images and exported results: current tab memory only, released when the page closes — no server-side copy.
• Local preference: ssc-theme remains until you clear site data or change browsers.
• Analytics, only if you allowed it: the _ga cookies expire after up to two years, event data in Google Analytics after its retention window (14 months at most). Declining keeps just ssc-consent.
• Email correspondence: exists only if you write to us, and is deleted once the enquiry is resolved, never kept longer than 12 months.

Children and minors

This is a tool site for content creators and developers, not designed for children under 13, and it collects no age or date-of-birth information. Since no personal data is collected at all, no retention or profiling of minors can occur.

Changes to this policy

If data handling changes — optional cloud saving, analytics or advertising — this page is updated first, together with the “last updated” date and version at the top, and a notice appears before the change takes effect. Earlier versions are available on request. This policy tracks what the code actually does; every claim in the current version is verifiable in your browser, including continued use while offline.

Contact

For privacy questions, complaints or rights requests, write to hello@imagesize.pro. That is the only contact channel — there is no live chat and no form to fill in. To check specific behaviour first, see the implementation notes at each step of the guide, or read the terms of service.