⚡

HyperFetch Privacy Policy

Browser extension for Chrome and Edge · Last updated 3 September 2026

HyperFetch does not collect, transmit, or store your personal data on any server we control. The extension talks to one place and one place only: the HyperFetch application running on your own computer, at 127.0.0.1. There is no HyperFetch account, no analytics, no telemetry, and no remote service that receives anything about you or what you download.

What the extension handles, and why

To hand a download to the desktop application, the extension passes it the same information your browser would have used to fetch the file itself. Without these, a download that requires a login would arrive as an error page instead of the file you asked for.

The download URL — the address of the file you chose to download, and the address of the page you were on, so the application can send a correct Referer to servers that require one.
Cookies for that specific address — read with Chrome's cookies permission, scoped to the URL being downloaded and nothing else. This is what lets a file behind a login download successfully. Cookies for sites you are not downloading from are never read.
Your browser's user-agent string — so the application identifies itself to the server the same way your browser did.
Page content, only to spot media — a content script runs on pages to detect video streams and show the "Download with HyperFetch" badge. It reads the page to find media links. It does not read, store, or transmit anything else, and it sends nothing anywhere until you click.

All of it is sent to http://127.0.0.1:21456 — a loopback address, meaning your own machine. Loopback traffic never reaches your network, your router, or the internet.

What is stored, and where

The extension keeps a small amount of state in Chrome's local extension storage on your device:

A pairing token — a random value shared with your local application so that website JavaScript cannot send downloads to it.
The local address the application was found on.
Your toggle settings from the popup.
A short queue of pending downloads, held only while the application is closed, and cleared once they are delivered.

This never leaves your device. Uninstalling the extension removes it. Cookies passed to the application are used for the transfer and are not written to disk by it.

What we never do

We do not sell or transfer your data to third parties.
We do not use your data for any purpose unrelated to the single function of the extension: sending a download to your own computer.
We do not use your data to determine creditworthiness or for lending purposes.
We do not run analytics, tracking, advertising, or fingerprinting of any kind.
We do not operate a server that receives your browsing history, your downloads, or anything else about you.

Why the permissions are what they are

cookies — to download files that require you to be signed in.
downloads — to cancel a browser download once the application has accepted it, so the file is not fetched twice. Only when you switch that option on.
webRequest — to notice video stream manifests (.m3u8) that a browser cannot save on its own.
contextMenus — the right-click "Download with HyperFetch" item.
storage — the local settings described above.
<all_urls> — because a download can start from any site. The permission is broad; what is done with it is not.

Children

HyperFetch is a general-purpose download tool and is not directed at children under 13. We do not knowingly collect information from anyone, of any age, because we do not collect information at all.

Changes to this policy

If this policy changes, the revised version will be published at this address with an updated date. Material changes to what the extension does with your data will also appear in the extension's store listing.

Contact

Questions about this policy, or about what the extension does, can be raised at github.com/tanumay-deb/HyperFetch/issues.