How Torrento handles website analytics, Android app data, companion pairing, subscriptions, and Torrento Connect service metadata.
Last updated: April 15, 2026
This Privacy Policy explains how Torrento ("Torrento," "we," "our," or "us") collects, uses, stores, and discloses personal data when you browse torrento.app, use the Torrento Android app, or pair and use Torrento Connect through a companion device. It applies when you use:
For the purposes described in this policy, Torrento is the controller of the personal data we process for our own service operations. You can contact us at info@torrento.app.
This Privacy Policy applies to personal data processed by us when:
This policy does not govern the privacy practices of your torrent client, your seedbox or NAS provider, Google Play, Firebase, AdMob, your email provider, or any third-party service you choose to connect to Torrento. Those services operate under their own terms and privacy notices.
When you access Torrento-hosted pages or API endpoints, our infrastructure and networking stack necessarily receive request data such as your IP address, user agent, timestamps, requested URLs, and related HTTP metadata.
In production, the website also uses Firebase Analytics to record page-view and site-interaction events, including page path, page location, page title, referrer, clicked destination, interaction labels, and page section metadata. This may involve cookies or similar identifiers managed by Google/Firebase.
The Android app stores operational data on the device, including:
This local data is processed on your device for app functionality. Because the Android app currently allows platform backup, some of this data may also be included in device-level backup or transfer systems controlled by Android or your Google account settings.
The Android app uses Firebase Analytics to record product usage events such as screen views, torrent-added events, torrent completion events, server-added events, purchase completion events, app-feedback prompt events, and Connect launch-prompt events.
If ads are enabled in your build and you have not purchased Remove Ads, the app also uses Google Mobile Ads (AdMob). The app requests consent status through Google's User Messaging Platform before requesting ads where that framework requires consent. AdMob and related Google advertising services may process device identifiers, advertising identifiers, IP address, approximate location signals, ad request metadata, and ad interaction data in accordance with Google's own privacy documentation.
The Android app uses Google Play Billing for:
For Remove Ads, the app restores purchase state from Google Play and stores a local boolean flag showing that ads have been removed.
For Torrento Connect subscriptions, the app may send your Google Play purchase token and package name to the Torrento Connect backend so we can verify entitlement with Google and unlock Connect-backed remote client import.
When the Android app bootstraps or refreshes a Torrento Connect mobile session, the Connect backend processes and may store:
In the pairing-first Connect flow, the backend creates an internal trust-owner record so the mobile device can pair a companion even before any explicit email-based account exists. In the current implementation, that record uses a synthetic non-routable internal email address solely as an identifier inside our database.
When you run a Torrento Connect companion, the companion itself stores local companion configuration on that machine. That local configuration can include:
The Torrento Connect backend does not need your torrent-client passwords or API keys to operate the service and does not store those credentials in its central database. It does, however, process and store companion-side metadata such as:
Torrento Connect processes pairing and remote-session data so the Android app and the companion can find each other and communicate. Depending on the route used, this can include:
When a session is on relay or proxy fallback, our backend transiently processes relayed request and response data so the Android app can control the paired companion remotely. The current implementation stores proxy request bodies only in short-lived server memory tickets and expires them quickly; it does not intentionally persist those proxied payload bodies in the normal session database. The backend does persist session metadata such as route used, timestamps, and aggregate bytes relayed.
Torrento Connect also includes account-oriented backend flows that may be used now or in future public-facing experiences. If you use those flows, we may process:
If you contact us by email or otherwise send us information directly, we process the contact details and the content of your message to respond, troubleshoot, and maintain support records.
We use personal data to:
Where the GDPR, UK GDPR, or similar laws apply, we generally rely on the following legal bases:
We disclose personal data only where necessary to operate the service.
We do not sell your torrent-client credentials. We do not disclose companion-stored torrent-client passwords or API keys to advertisers. We also do not use your locally stored torrent server credentials for our own marketing purposes.
Torrento and its service providers may process personal data in countries other than the country where you live, including countries that may have different data-protection rules. Where we rely on processors or services outside the EEA, UK, or Switzerland, we will rely on appropriate transfer mechanisms where required by applicable law, such as adequacy decisions or standard contractual clauses.
We retain personal data only for as long as necessary for the purposes described in this policy, including security, fraud prevention, compliance, and record-keeping.
We use technical and organizational measures designed to protect personal data against unauthorized access, loss, misuse, or alteration. These measures include authentication tokens, session controls, companion public-key trust, entitlement checks, and compartmentalizing credentials so that local torrent-client passwords remain on the device or companion where they are configured.
No system is perfectly secure. You are responsible for protecting access to your device, companion machine, torrent-client accounts, and local network. You are also responsible for the transport security of the torrent server endpoints you choose to configure. If you configure a client over insecure HTTP or another unencrypted path, traffic between your device or companion and that client may not be encrypted.
Depending on where you live, you may have rights to access, correct, update, delete, restrict, object to, or export certain personal data, and to withdraw consent where processing relies on consent. You may also have the right to complain to a supervisory authority.
You can also use product-level controls, including:
Torrento is not directed to children. We do not knowingly target or seek to collect personal data from children under 16. If you believe a child has provided personal data to us, contact us at info@torrento.app and we will review the request.
We may update this Privacy Policy from time to time to reflect product changes, legal requirements, or operational improvements. When we do, we will publish the revised version at this page and update the "Last updated" date above. Material changes will apply from the date the updated policy is posted unless a longer notice period is required by law.
If you have questions about this Privacy Policy, privacy rights requests, or data-protection concerns, contact Torrento at info@torrento.app.