Privacy Policy

Last updated: May 2026

Download Accelerator ("the Extension") is committed to protecting your privacy. This policy describes what data the Extension accesses and how it is used.

Data We Access

• URLs you enter or click — used solely to perform the download you requested. URLs are not stored beyond the active browser session.
• Browser cookies for the requested URL — forwarded to the native host (if installed) to enable authenticated downloads (e.g. behind a login). Cookies are never stored on disk or transmitted to any third party.
• Extension settings (number of connections, download folder, intercept toggle) — stored locally on your device using chrome.storage.local. Never transmitted externally.

Data We Do Not Collect

The Extension does not collect, transmit, or share any personal data. There are no analytics, no telemetry, no remote servers, and no third-party services involved of any kind.

Native Host (Optional)

If you install the optional native helper application, it runs exclusively on your local machine. It connects only to the download URLs you explicitly request and sends no data anywhere else. The source code is fully available on GitHub.

Permissions Explained

• downloads — required to save completed files to your disk.
• storage — stores your settings locally.
• cookies — reads cookies for the URL being downloaded, so authenticated files (behind a login) can be downloaded correctly. Cookies are passed only to the native host and only for your requested URL.
• nativeMessaging — communicates with the optional local native helper application.
• contextMenus — adds "Download with Download Accelerator" to the right-click menu on links.
• notifications — shows a notification when a download completes.
• <all_urls> — required for the optional intercept mode (capturing downloads from any website) and for reading cookies of any URL.

Changes to This Policy

If this policy changes, the updated version will be published at the same URL with a new "Last updated" date.

Contact

For questions or concerns, please open an issue on GitHub.