Updated October 15, 2026
This policy covers JSTorrent's Chrome extension, desktop application and Android app, and the JSTorrent website. Behavior varies between the legacy application and the replacement currently being qualified; the replacement's new optional hosted context remains disabled until deployment and verification are complete.
Torrent metadata, download-folder access, settings and pairing information are stored locally. The native application owns downloaded files and the torrent engine. The extension connects to that application on your device. JSTorrent does not collect a general browsing history. Pairing credentials are local connection authority, not analytics identifiers.
The replacement keeps a random resettable installation identifier and coarse local counts of added torrents, completed downloads and foreground sessions. These values are separate from torrent names, hashes, paths, peers, trackers, logs and error text. They are pseudonymous, not anonymous: permitted requests can be correlated until the identifier is reset.
Ordinary BitTorrent operation contacts peers and discovery services, which can observe network addresses and protocol information. Desktop update checks contact the update service with version and platform information and whether usage statistics are on, off or not yet chosen. That choice is sent without any identifier, so we can count how many installations opt out. Depending on the version and disclosed statistics preference, an update check may also include the installation identifier. The replacement can preserve an older desktop installation's existing update identifier until you review the new disclosure. Once you review it, disabling statistics omits that identifier from update checks. Fresh installations do not send a new identifier before that review.
Usage statistics are on unless you turn them off. The choice is shown when you first open the app and stays available in its settings. Turning statistics off stops everything described in this section except what an update check needs: the version, platform and statistics-choice information above.
With statistics on, the app may also send basic compatibility information: which versions of JSTorrent and its controllers (the extension, the remote controller) connected to each other, and counts of requests one version could not handle. We use it to find and fix version mismatches. It never includes torrent names, hashes, file paths, peers, trackers or content.
There is no automatic crash-report upload. This does not mean that update requests or user-opened websites send no data: ordinary HTTP requests expose network addresses and request information.
Full share links keep torrent information in the link itself. If you enable Short link in the web or desktop Share panel, your device encrypts that information and uploads an encrypted copy to link.jstorrent.com, hosted by Cloudflare. Copies expire after 30 days. The decryption key stays in the link's fragment and is not sent to the storage API; the recipient's browser decrypts the copy before opening the share page. Anyone with the complete link can read it. The service can observe network addresses, request times and the padded size of the encrypted copy. It has no accounts, link listing or content analytics. The Short link choice is remembered on that client and can be turned off in the Share panel.
Include my IP address is a separate choice: it puts a direct connection address in the shared information. Leaving that unchecked does not hide your network address from a service you contact or from BitTorrent peers.
The remote controller at jstorrent.com and its relay are a hosted service. The connection between your browser and your JSTorrent is end-to-end encrypted; the relay cannot read your torrents or commands. To operate the service and keep it reliable, the service may record basic operational data such as network addresses, connection times and outcomes, and the versions of JSTorrent and the remote controller in use. This applies whenever you use remote access, independent of the in-app statistics choice.
Feedback and uninstall pages embed Google Forms and use Cloudflare Web Analytics. Navigating to a page can expose URL context to browser history, website logs and referrers, the embedded form and website analytics before a form is submitted. Review the context shown by the application before opening a feedback page and review your response before submission.
The replacement currently sends only its accepted environment fields to feedback: platform and version, plus Android release and manufacturer/model where applicable. New optional installation identifier, days since first use and aggregate usage fields remain release-disabled. If enabled in a later verified release, they require the disclosed preference and can be omitted for a feedback navigation. The extension has its own local identifier and never adopts the native application's identity.
With extension usage statistics enabled, feedback and uninstall links also include the operating-system family, browser version reported by its user agent (which may be reduced), extension version, the last JSTorrent extension page and an allowlisted connection result code. The page is selected from fixed extension routes; arbitrary browsing URLs, queries, fragments and raw errors are excluded. Connection context is kept only for the browser session. Turning statistics off omits this context and clears it; the extension version remains. Review the feedback link before opening it.
Older clients may construct different feedback context. Receiving pages accept only bounded known fields and render values as text. Filtering a page's display or form does not erase a URL already received by browser history or a website server.
Support diagnostics in the replacement produce a local, reviewable report of build, package and closed update-status facts. Preparing, copying or saving that report uploads nothing automatically. You choose whether to share it. Public issue reports and their attachments are public; review screenshots, logs and other attachments for private information before submitting.
Usage-statistics controls can disable permitted identifier/counter context; reset controls create a new product identifier and clear local counters. These actions do not delete downloaded content and cannot retract data previously sent to recipients. Website analytics and submitted Google Forms have their own recipient policies.
For privacy questions, use the JSTorrent issue tracker. Do not include private library data or credentials in a public issue.