Privacy Policy
Last updated: September 1, 2026
1. Scope & who we are
Motrix is a free, open-source download manager maintained by the Motrix open-source project (created by the developer known on GitHub as Dr_rOot / “agalwood”). In this policy, “Motrix”, “we”, “us”, and “our” refer to that project.
This policy covers: (a) the website at motrix.app, including the download and update service at dl.motrix.app; (b) the official Motrix desktop and server releases, including the 1.x and 2.x release channels; and (c) the official Motrix browser extension. It does not govern third-party websites, download sources, plugins, package hosts, or services you choose to connect to through Motrix.
2. Our approach: local-first by design
Motrix is designed to store its core task data and settings in the desktop app’s local data directory or the server’s configured data directory. The project does not operate a Motrix user-account or advertising-profile system. As of the date shown above, official builds do not intentionally include product analytics, advertising, or crash-reporting services. Network features are described below and may also depend on your configuration, installed plugins, and third-party services. This is a dated description of current official builds, not a guarantee about every third-party component or future release.
3. The website (motrix.app)
Our website is a static site served through Cloudflare’s content-delivery network. As of the date above, the site does not intentionally set analytics or advertising cookies, embeds no analytics or advertising scripts, and has no Motrix login, comment, or sign-up forms. Cloudflare may still apply security or delivery functionality under its own policies. On-site search runs in your browser; the site does not intentionally send search terms to a Motrix search service.
When your browser requests a page, Cloudflare processes standard connection information such as your IP address, requested URL, timestamp, and browser user-agent to deliver content and protect the service. Processing and retention depend on the project configuration and Cloudflare’s policies. The Motrix project does not intentionally use this connection data to build advertising profiles.
The service at dl.motrix.app distributes installers, update metadata, and the plugin registry. It does not provide Motrix user accounts. Requests to it are delivered through hosting and CDN infrastructure that may process access logs as described above.
4. The desktop application
Official builds and product analytics. As of the date of this policy, the project does not intentionally include product analytics, advertising, or crash-reporting services in official desktop or server builds. Operational logs, update checks, registry requests, downloads, and other network features described below are separate from product analytics. Future releases may change these data flows; material changes will be reflected in this policy.
Core app data is stored in the environment where Motrix runs. Desktop data is normally stored in the operating system’s application-data and logs directories. Server data is stored in the configured server data directory or container volume. This can include:
- Your task list and download history;
- Application settings and preferences;
- Local logs;
- Any Cookie, Referer, or custom HTTP headers you enter for a download (including those imported from a cURL command).
The app provides controls for clearing supported task and settings data. Removing the application data directory removes data stored there, but downloaded files, external backups, browser data, system logs, and data held by third-party services may require separate action.
Update checks. Depending on the app version, platform, and release channel, Motrix requests update metadata from dl.motrix.app and may use GitHub Releases as a source or fallback. These requests reveal your IP address to the service provider and may indicate the app version, operating system, architecture, and release channel through the requested URL or headers. Official update requests are not intended to include a Motrix account or advertising identifier. Available update controls vary by version and platform.
Downloads you start. Motrix normally connects to the download source you provide, directly or through a proxy you configure. The source, proxy, and related network providers can observe connection information such as your IP address and request headers, including any Cookie or Referer you supply. Ordinary download traffic is not intentionally routed through a Motrix-operated download proxy.
BitTorrent and magnet links. If you download over BitTorrent, Motrix participates in a peer-to-peer network. By its nature, this means the app exchanges your IP address with trackers, DHT nodes, and other peers so they can send you pieces of the file. The DHT feature is enabled by default and can be disabled in the app’s settings. This behaviour is inherent to how BitTorrent works and is not something Motrix adds.
BitTorrent tracker lists. When automatic tracker-source syncing is enabled, the app periodically requests community-maintained lists. Default sources include GitHub’s raw content service, with jsDelivr alternatives available; you may also configure other sources. The selected services receive normal connection information such as your IP address. The default interval is approximately 12 hours and can be changed or disabled.
Features that connect out only when you use them. Some capabilities make a network connection only after you enable or invoke them:
- GeoIP database — used to show the approximate country of BitTorrent peers. It is disabled by default. If enabled, the app downloads from the selected built-in or custom source, which receives normal connection information.
- Speed test — when you run it, the app transfers test data to and from the provider you select. Built-in choices include Cloudflare and Apple, and configuration may add other endpoints.
- Plugins — registry browsing, installation, and updates can contact dl.motrix.app, GitHub, or the package host shown for the plugin. Installed plugins may contact hosts covered by the permissions you grant. Review the package source and requested access before installing.
5. The browser extension
Single purpose. The Motrix browser extension exists to find or accept a download in your browser and hand that task to the Motrix App or Motrix Server you select. Related controls, such as showing task status, opening a task in Motrix, or asking Motrix to pause, resume, or remove a task, support that same purpose. The extension does not provide a Motrix account, advertising, or an unrelated browsing service.
Browser access and data processed. To provide this function, the extension requests permission to access websites and tabs, inspect relevant page content and network activity, manage eligible browser downloads, read cookies, connect to the local Motrix App through Native Messaging, save settings, and show notifications and context-menu actions. Depending on the feature you use, it may process:
- The target download URL or magnet URI, the source page URL and title, the selected resource or media-manifest URLs, a suggested filename, and resource metadata such as type, dimensions, or estimated size;
- Download-item information needed to take over a browser download or restore it to the browser if handoff fails;
- Referer and other page-derived request headers, cookies, and authentication information when needed for an authenticated download and allowed by the applicable setting or consent;
- The selected Motrix endpoint, pairing state and credentials, per-Server data permissions, extension settings, and task-control messages and responses.
Local inspection. Page-resource discovery happens in the browser. Opening a page does not by itself send the full page or the list of discovered resources to Motrix. The extension keeps bounded discovery metadata in browser session storage for the current tab. Sensitive request-header observations are kept only in memory, are not exposed to the extension popup, and expire after up to five minutes. Small image previews can be sampled from pixels the page has already loaded without fetching the image again. To estimate a file size, the extension may send a HEAD request or a one-byte ranged request, with browser credentials, directly to the target file host.
When data is sent. A task is sent when you create or submit it, use a “Download with Motrix” action, or enable browser-download takeover. Takeover is off by default and asks for confirmation before it is first enabled. Where identified by the extension, certain banking, government, and medical sites are excluded from automatic takeover. When you submit a task, the selected Motrix endpoint receives the data needed to perform it, which can include the target URL, source page URL and title, suggested filename, selected resources, and task-control commands. Cookies and request headers may also be included as described below.
Local and remote destinations. A task for the Motrix App on the same computer is sent over a local connection. For a Motrix Server, pairing identifies the Server but does not authorize browser data to cross devices: remote downloads must be enabled separately for that Server. Sending page-derived request headers and sending cookies or authentication information are additional per-Server permissions and start disabled. Grant them only to a Server you control. The Motrix project does not operate a relay that receives extension task submissions.
Connection security. Paired Motrix connections use the MBP1 protocol, including application-level encryption for task content. Use WSS for a remote Server on the Internet or an untrusted network. Plain WS is intended only for a trusted local network: although task content remains encrypted at the application layer, TLS does not protect its connection metadata or the Server identity during initial pairing.
Storage and deletion. The extension stores its settings, Server list, a random extension-install identifier, pairing credentials, and per-Server permissions in browser-local extension storage. These records remain until you change the related setting, forget or remove a pairing where applicable, or uninstall the extension. Discovered-resource metadata is temporary browser-session data and is cleared as tabs navigate or close and when the extension session ends. Data already submitted to Motrix is stored and deleted under the controls of that App or Server; uninstalling the extension does not delete tasks or files in Motrix.
Limited use. Data accessed by the extension is used only to provide and maintain its download-handoff purpose and related security. The Motrix project does not sell extension data, use it for advertising, creditworthiness or lending, or use browsing activity for an unrelated profile. In normal operation, task data travels directly between your browser, the selected Motrix endpoint, and the target download host, so the Motrix project does not receive or permit humans to read it. A project maintainer may access information only when you deliberately provide it for support, when needed to investigate abuse or a security incident, or when required by law.
Other recipients. The target file host receives any size-probe or download request directed to it. Chrome Web Store, Microsoft Edge Add-ons, and Firefox Add-ons distribute extension packages and updates and process related store activity under their own policies. As of the date above, the official extension does not intentionally include product analytics, advertising, or crash-reporting services.
6. Where your data can go
Depending on the features and configuration you use, data recipients can include Motrix hosting and update infrastructure; Cloudflare, GitHub, jsDelivr, Apple, browser stores, and other package or content hosts; BitTorrent trackers, DHT nodes, and peers; download sources and proxies; remote Motrix endpoints; installed plugins and the hosts you authorize for them; and other services you configure. This list describes common known flows and may change as you add custom sources, plugins, or integrations. The Motrix project does not operate an advertising data-broker service.
7. Children’s privacy
Motrix is a general-purpose tool and is not directed to children. The project does not intentionally request a user’s age or operate a child-focused account service. Connection data may still be processed by the infrastructure and third-party services described in this policy.
8. Data retention and your control
You can clear supported history and settings in Motrix and remove the app or server data directory when appropriate. Downloaded files, backups, browser data, remote-server data, plugin data, and third-party service records may need to be handled separately. Hosting, CDN, browser-store, download-source, and other providers determine their own processing and retention under their policies and the applicable configuration.
9. Your rights
Depending on where you live, privacy law may give you rights relating to personal information, such as access, correction, deletion, objection, or restriction. Many Motrix records are controlled through the device or server where you run the software. For data processed by a third-party provider, its own privacy process may apply. If you believe the Motrix project controls information about you, contact us using the details below. We will assess the request based on the information and systems the project can reasonably identify and control.
10. Where data is processed
The website and update service use globally distributed hosting and CDN infrastructure. Requests and related connection data may therefore be processed in multiple countries or regions under the providers’ policies and the project configuration. Services you configure, including download sources, proxies, plugins, and remote Motrix endpoints, may process data in other locations.
11. Changes to this policy
We may update this policy when features, infrastructure, providers, or legal requirements change. The “Last updated” date identifies the published version. For material changes, we may provide an additional notice through the website, app, release notes, or another appropriate channel, and we will request consent where applicable law requires it.
12. Contact us
If you have any questions or concerns about this policy or your privacy, you can reach us at support@motrix.app, or open a discussion or issue on our GitHub repository at github.com/agalwood/Motrix.