Privacy policy
Browser
extension
Your downloads go from your browser to Conflux on your PC. Nothing goes anywhere else.
Overview
The Conflux browser extension is a companion to the free and open-source Conflux Download Accelerator desktop app. Its sole purpose is to send download requests from your browser to your local Conflux client.
Information we access
When you start a download with Conflux (the right-click "Download with Conflux" menu, or automatic download interception), the extension reads only what it needs to fulfil that request:
- Target URL: the address of the file being downloaded.
- Referrer URL: the
Refererof the originating page, which some servers require to accept the request. - User-Agent: your browser's User-Agent string, to match what the server expects.
- File name and size: the suggested filename and byte length from the browser's download event.
The extension requests no host permissions. It does not read page content, cookies, or your tabs.
Where your data goes
Your data never leaves your computer. It is handed to the Conflux desktop app over the operating system's standard input and output pipes (the WebExtensions Native Messaging API).
- We operate no remote servers, cloud backends, or third-party proxies.
- No browsing activity, URLs, or download logs are collected, transmitted, sold, or shared with anyone.
Data storage
Your extension settings (auto-interception on or off, file extension filters, excluded domains) are kept in browser extension storage (chrome.storage.sync). Download URLs are never written to persistent storage by the extension.
Analytics and third-party code
The extension contains no tracking scripts, advertising networks, or telemetry. It talks to no external domains, only to the native messaging host registered on your device.
Open source
Conflux is open source under the MIT and Apache-2.0 licenses. The desktop app and this extension are publicly verifiable at https://github.com/manjeet2k/conflux.
Contact
Questions about this policy or Conflux security? Open an issue on our GitHub Issues page.