Last updated: September 18, 2026
Advanced Download Manager ("the extension") is a Chrome extension that intercepts downloads and routes them to a downloader of your choice. This page explains what data the extension accesses, how it is used, and where it goes.
Summary
The extension does not collect, transmit, or sell any data to its developer or any third party. It contains no analytics, telemetry, crash reporting, advertising, or third-party SDKs of any kind. Everything described below either stays on your device or is sent only to a destination that you explicitly configure yourself.
What data the extension accesses
- Download metadata — the URL, filename, and HTTP referrer of a download you initiate, so it can be handed to the downloader you pick.
-
Cookies — using Chrome's
cookiespermission, the extension reads the cookies for the domain of a download you start, so they can be forwarded to a downloader that needs them to complete the request (for example, a file that requires a logged-in session).
The extension only reads cookies for downloads you actively initiate. It does not read cookies in the background or for sites you are simply browsing.
Where your data goes
Depending on how you've configured the extension, download and cookie data is sent only to:
-
Your own device — a local downloader app (e.g. Free Download Manager) via
Chrome's native messaging API, or a local RPC endpoint (e.g. Motrix/aria2 on
127.0.0.1). This never leaves your machine. - Your clipboard — when you choose "Copy as cURL," a ready-to-run command (optionally including cookies) is copied to your clipboard for you to run yourself.
- A remote service you configure — if you set up a remote downloader (qBittorrent Web UI, aria2 RPC, or SSH), the extension sends the download request and cookies directly to the host/URL you typed into the Options page. This is a service you run or control, not a server operated by the developer.
The developer never receives any of your data. There is no developer-operated backend, analytics endpoint, or third party that this extension talks to.
What the extension stores, and where
-
Downloader configuration (the local/remote downloaders and custom commands
you set up in Options — including any URL, username, password, SSH key, or API token you
enter for your own services) is stored using Chrome's
storage.syncAPI. This means it is synced across your signed-in Chrome browsers through your own Google account, governed by Google's sync and privacy policies — it is not sent to the developer. - In-progress download state (the URL, filename, referrer, and cookies for a download you just triggered) is held briefly in Chrome's session storage (or memory), is never synced, and is automatically cleared within seconds or when the browser session ends.
Because downloader credentials are stored in Chrome sync storage, keep this in mind if you configure a remote service with a password or API token: it will be available on any Chrome profile you're signed into, per Google's own sync behavior.
Permissions used
downloads— to intercept and redirect downloads.cookies— to read cookies for a download's domain when forwarding is needed.storage— to save your downloader configuration and options.notifications— to show status updates about downloads.nativeMessaging— to hand off downloads to a local app (e.g. Free Download Manager) on your machine.management— to detect whether a required companion app/extension is installed.host_permissions (<all_urls>)— required to intercept downloads and read cookies for any site you download from.
Data retention and deletion
Downloader configuration persists until you remove it from the Options page or uninstall the extension, at which point Chrome deletes its stored data. Per-download state is short-lived and clears automatically. You can also clear all stored settings at any time via the Options page or by removing the extension.
Children's privacy
This extension is not directed at children and does not knowingly collect data from children.
Changes to this policy
If this policy changes, the updated version will be posted at this URL with a revised "Last updated" date.
Contact
Questions about this policy or the extension's data handling can be raised via GitHub Issues.