Privacy

Privacy Policy

Images Extractor is a local-only browser extension. It has no backend, no accounts, and no analytics - so there is no data for us to collect in the first place. This page explains that in specific terms.

Last updated 10 August 2026

The short version

  • We collect nothing. No accounts, no sign-up, no analytics.
  • Nothing you view or extract is sent to us. There is no server to send it to.
  • The extension reads a page only when you click its icon, and only the tab you are looking at.
  • This website sets no cookies and loads no third-party resources.

1. What the extension does on your machine

When you click the Images Extractor toolbar icon, it runs a script in the page you are currently viewing, collects the addresses of the images on it, and displays them in the popup. That list lives in the popup window only. Closing the popup discards it. Nothing is written to disk, saved to browser storage, or transmitted anywhere.

The extension does not run in the background, does not read pages you have not explicitly asked it to read, and does not monitor your browsing.

2. Permissions, and why each one is needed

Chrome requires an extension to declare every capability it uses. We request four, and no host permissions:

Permission Why it is required
activeTab Grants access to the single tab you are viewing, and only at the moment you click the extension icon. It expires afterwards.
scripting Lets us run the image-collecting script inside that tab. Without it there is no way to see the page's images.
downloads Hands an image's address to Chrome's own downloader when you click Download. We never see or store the file.
clipboardWrite Writes a URL or an image to your clipboard when you ask. Nothing is ever read from your clipboard.

Notably absent: broad host permissions. Many comparable extensions request access to all websites. We deliberately do not, which is why a small number of images cannot be copied - see the FAQ.

3. What leaves your browser, and when

Two actions cause a network request. Both go directly from your browser to the site hosting the image - never through us:

  • Copy image. To place a picture on your clipboard, the image's bytes have to be read, which means requesting it from the server that hosts it. That server sees a request from your browser, exactly as it did when the page first displayed the image.
  • Download image. The address is passed to Chrome's built-in download manager, which fetches the file the same way it would if you saved it by right-clicking.

Copying a URL and opening an image in a new tab behave exactly as they would anywhere else in your browser.

4. This website

This site is static. It sets no cookies, runs no analytics, embeds no trackers, and loads no fonts, scripts, or images from third-party domains - the photographs in the page header are hosted here alongside everything else, specifically so that visiting this page does not tell anyone else that you did.

Like any website, the hosting provider that serves these files may keep standard server access logs (IP address, timestamp, requested file) for operational and security purposes. We do not use those logs for analytics or profiling.

Some links point to GitHub, where the source code and the download live. GitHub is operated independently and has its own privacy policy, which applies once you follow such a link.

5. Children

The extension is a general-purpose developer and designer utility. It collects no personal information from anyone, of any age.

6. Changes to this policy

If the extension ever gains a capability that changes any of the above, this page will be updated and the date at the top revised before that version ships. Because the project is open source, the full history of both the code and this page is publicly auditable.

7. Contact

Questions or concerns are best raised as an issue on the GitHub repository, where they are answered in public.

Verify any of this yourself

You do not have to take our word for it. The entire extension is about 500 lines of readable JavaScript with no build step, no dependencies, and no minification. Read popup.js and manifest.json in the repository and you can confirm every claim on this page in a few minutes.