Privacy Policy — Image Size Finder Data & Privacy Terms

Welcome to ImageSizeFinder.com. This Privacy Policy explains how we handle information when you use our website and tools.

1. Local image analysis

ImageSizeFinder.com is designed as a privacy-conscious utility. When you use the core tool to inspect image dimensions, file size, EXIF, GPS, DPI, or other metadata, your image files are processed locally in your browser and are not uploaded to our servers for analysis. Because the analysis happens on your device, you stay in control of the files you open in the tool.

AI Image Detector is an exception to local-only processing. When local checks are inconclusive, it may automatically upload the selected image, including its filename and embedded metadata, to our server for a deep scan. Depending on the configured provider, image data may be processed by our model service, Hugging Face or Replicate. Importing an image by URL sends that URL to our server, which requests the image from its host. Detection results and image hashes may be temporarily cached. Provider retention is subject to its policy; do not submit confidential images to this feature.

2. The browser extension

Image Viewer & Size Finder is a Chrome extension published by us. It is covered by this policy and is subject to stricter limits than the website.

It makes no network requests. The extension contains no analytics, no telemetry, no crash reporting, no remote configuration and no update-channel phone-home. The only network read anywhere in its code is the image you explicitly asked it to inspect, fetched in that page's own context so EXIF and an exact byte count can be shown. That read never leaves your browser.

We receive nothing. No browsing history, no page URLs, no image URLs, no image contents, no identifiers. There is no server component, so there is nothing for us to store, log or disclose.

Permissions, one by one. The extension declares exactly these, and you can verify the list in its manifest:

contextMenus — adds the right-click entries on images. It cannot read page content.
activeTab — granted by Chrome only when you click one of our own menu items, scoped to that tab and that action. This is what lets the viewer open without any standing site access.
scripting — injects the viewer overlay into the page you invoked it on.
storage — saves your settings (background colour, whether the info panel opens, whether click-to-open is enabled) in local browser storage. These never sync off your device and are never transmitted.

Access to all websites is optional. The extension installs holding no host permissions. Broad site access is requested only if you turn on click-to-open in its settings, at the moment you turn it on. Switching it back off revokes the permission itself, not merely the feature. You can also revoke it at any time from chrome://extensions.

Location data is never shown. When an image contains GPS coordinates, the info panel reports only that location data is present. The coordinates themselves are never displayed, stored or transmitted.

It is auditable. The extension has no build step and no minifier: the JavaScript Chrome installs is the JavaScript we wrote. You can read all of it without trusting us — open your browser's developer tools on any page and look under Sources → Content scripts. A public source repository is planned for a later version, but it would not tell you more about the installed package than the package already does.

3. Technical information needed to operate the website

Like most websites, our hosting, CDN, security, and infrastructure providers may temporarily process basic request data such as IP address, browser and device details, request time, referrer, and security logs. We use that information only as needed to deliver the website, prevent abuse, troubleshoot issues, and keep the service available.

4. Cookies, local storage and analytics

We use Google Analytics 4 (GA4), Plausible and Rybbit to understand visits and improve our tools. These services may process page URLs, referrers, browser/device information, IP addresses or approximate location, and usage events. Tool events can include the tool name, input/output format, file count, file-size range, processing time, success/error status and downloads. We do not intentionally send image contents, filenames or embedded EXIF/GPS metadata in these analytics events. GA4 may use cookies and browser identifiers. Browser-local image processing does not mean that visiting this website involves no network requests or tracking. We also use cookies or local storage for language preferences and tool-use state.

5. Advertising and third-party services

We currently display advertising through Adsterra. Google AdSense ads are not currently enabled; Google Analytics is a separate service. Adsterra and its advertising partners may receive IP addresses, browser/device details, page/referrer information and ad interactions, and may set or read cookies, identifiers or web beacons to deliver and measure ads and prevent fraud. Their processing and retention are governed by their policies and applicable settings. Hosting, CDN, security and analytics providers also process request data to deliver their services. We do not send the images handled by our local tools to advertising providers.

You can block or delete cookies and site storage in your browser, restrict third-party requests, or use Google’s Analytics opt-out tool below. These controls have different scopes: deleting cookies does not stop future requests, and the Google opt-out does not disable Adsterra, Plausible or Rybbit. Blocking scripts may affect site features. For privacy questions or requests about data we hold, contact [email protected]. This policy does not itself obtain consent or change your browser settings.

6. Data retention

Because core image analysis happens locally in your browser, we generally do not retain the image files or embedded metadata that you inspect with the tool on our servers. Operational logs, security records, and provider-level technical data may be retained for limited periods as required for service delivery, abuse prevention, or legal compliance.

7. Changes to this policy

We may update this Privacy Policy from time to time. When we do, we will post the revised version on this page and update the "Last updated" date at the top.

8. Contact

If you have questions about this Privacy Policy, contact us at [email protected].

Feedback via Tally

If you open our feedback form, your browser connects to Tally, which hosts the form and processes your submitted feedback and optional email address. Tally may receive technical connection data such as your IP address and browser information. We use feedback to investigate problems, improve tools and reply when appropriate. We do not automatically attach images, filenames, image metadata or the current page URL. Do not include confidential information. To request deletion of your feedback, contact [email protected]. See Tally’s Privacy Policy.