Privacy Policy

Scope and responsible project

This Privacy Policy describes the information practices of the TorrentDeck application for Android and Windows. The Android application is identified by the package name com.mwd.torrentdeck. Official project pages that link to this policy may generate hosting logs, including IP addresses and request times, under their hosting provider’s practices. These legal pages do not embed AdMob or Firebase Analytics.

The official download page stores your selected language in your browser’s local storage under torrentdeck.site.language. This preference is not sent as a tracking event and can be removed by clearing this site’s browser data. Links to stores, releases, and other websites are subject to the destination provider’s privacy practices.

Davi Santos da Silva is the developer responsible for TorrentDeck and for personal data processing within his control. Studio MWD is the public-facing name used for the application. Send privacy questions and data rights requests privately to torrentdeck@studiomwd.com.

If you contact us, we receive your email address, message, and any attachments or diagnostic information you choose to provide. Sending a support request does not give us access to the files or application database on your device. Avoid sending unrelated personal information.

Privacy overview

• You do not need to create an account or provide a name, email address, phone number, or payment details.
• Android includes AdMob, Firebase Analytics and Firebase Crashlytics. Windows does not include these SDKs. Analytics and automatic crash reporting are optional and disabled by default.
• The app does not upload a central list of your torrents, magnet links, files, or metadata lookups to the developer. Enabled crash reports may contain runtime context, as explained in Section 06.
• Download state, library information, and settings are stored locally on your device.
• When you use BitTorrent, technical information is necessarily exposed to P2P network participants and operators.
• Update checks and application downloads may contact official distribution channels and external hosting services.
• Advertising choices are managed through Google’s User Messaging Platform (UMP); Analytics and crash reports have independent optional choices in Settings > Usage and diagnostics.

Information processed on your device

To perform the actions you request, TorrentDeck accesses and, where necessary, stores transfer-related information locally. This information is not uploaded to a server operated by the TorrentDeck project.

Downloaded and created files are written to folders that you choose or authorize. On Android, the default location is under Downloads/TorrentDeck. TorrentDeck also keeps a local database for sessions, preferences, and library records.

BitTorrent, peers, and trackers

When you request metadata, start a download, or enable seeding, TorrentDeck participates in the BitTorrent network. Depending on the source and swarm configuration, the application may communicate directly with:

• other users and BitTorrent clients, known as peers;
• trackers included in an imported source or selected when creating a torrent;
• distributed peer-discovery systems available to the BitTorrent session; and
• network services and devices required to establish those connections.

These recipients may receive or observe your IP address, connection port, info hash, technical client identifiers, piece availability, transfer volume, and connection times. Peers also receive available file blocks during downloads as well as subsequent seeding. An info hash may allow a third party to associate your connection with the known contents of a torrent.

Opening a TorrentDeck link can retrieve the small .tdeck package over P2P before the content-selection preview. Downloads of the selected collection files require confirmation. Transfers already confirmed may resume when you reopen the app. Creating a torrent or publishing a collection can start seeding from your device. Author, website, descriptions, and other metadata included in shared packages are visible to recipients.

Disabling seeding after completion does not prevent uploads while a download is active. Pausing or ending a transfer stops its ongoing transfer activity; it does not erase information already received by network participants.

P2P participants and tracker operators are independent third parties. The TorrentDeck project does not select every recipient, control their practices, or have the ability to delete data that they may retain.

Updates and application downloads

On Android and Windows, TorrentDeck may check for new versions over HTTPS. The update request identifies the app version and platform; it does not include your torrent list, magnet links, file contents, or a custom per-user identifier. Studio MWD and its hosting providers may receive your IP address, request time, and connection headers.

Application stores and installer hosting services may process visit and download information under their own privacy policies, independently of TorrentDeck’s optional Analytics and Crashlytics choices. Consult the policies available in the service you access.

Google AdMob advertising, Firebase Analytics and Firebase Crashlytics

AdMob on Android

The Android application integrates Google AdMob through the Google Mobile Ads SDK. Windows does not include this integration. No separate third-party advertising-network SDK or mediation adapter is integrated; advertisers and technology providers serving ads through Google may nevertheless process information under their own policies.

Full-screen interstitial ads may appear when you open download or package details, successfully add a download, or create a torrent or .tdeck package. The app enforces at least one hour (60 minutes) between displays across these actions, using a locally saved frequency limit. Closing and reopening the app does not reset this limit. Availability is not guaranteed: if an ad is not ready, the action continues without waiting for it. Loading an ad can involve data transmission even when no ad is ultimately displayed.

Google’s SDK documentation identifies IP addresses (including use for approximate location), app and ad interactions, performance diagnostics, and advertising, app-set, or other applicable device/account identifiers as data processed for ads, measurement, and fraud prevention. Ad content may also use cookies or similar storage. Google states that SDK transmissions use TLS. Processing varies with privacy choices, region, and ad configuration; non-personalized or limited ads can still involve data processing. See Google’s Mobile Ads data disclosure.

Advertising privacy choices

TorrentDeck uses Google’s User Messaging Platform (UMP) to update advertising consent information at startup and present an applicable form. Ads remain blocked until that initial flow finishes. If the update fails, ads are requested only if UMP permits them using the available consent state. When UMP requires a privacy-options entry, you can revisit it in Settings > Ad privacy (Configurações > Privacidade dos anúncios in Portuguese). Available choices depend on the messages configured for your region. Android settings also allow you to reset or delete the Advertising ID; that does not stop all SDK processing.

TorrentDeck does not send torrent names, magnets, info hashes, file contents, or collection descriptions as custom ad-targeting parameters. Google still receives the technical and interaction data described above. See Google’s Privacy Policy and how Google uses information from partner apps.

Firebase Analytics on Android

With your permission, Android uses Google Analytics for Firebase to understand app usage and improve the product. Its default collection includes installation and session identifiers, app opens and updates, engagement, device model, operating system, and general geographic information. TorrentDeck disables Advertising ID collection and advertising personalization for Analytics. The project can access usage reports in its Firebase/Analytics console. No custom events containing torrents, magnets, file names, or collection contents are implemented. See Firebase Analytics data collection.

Analytics is disabled by default until you enable Usage statistics and select Save choices in the optional Usage and diagnostics dialog. Both controls start off for new installations. Decline both, or dismiss the initial dialog, to continue without enabling either service. The app remembers your choice and does not ask on every launch. Change it at any time in Settings > Usage and diagnostics (Configurações > Uso e diagnóstico). Refusing there stops future Analytics collection; it does not erase data already sent. The choice and notice version are stored locally. Analytics consent is independent of AdMob and Crashlytics choices and does not authorize personalized advertising. Existing Analytics choices are preserved on upgrade and do not enable crash reporting or trigger another startup dialog. Closing the dialog from Settings without saving preserves existing choices. Google console sharing and retention settings also apply to previously collected data. See Firebase privacy information.

Firebase Crashlytics on Android

With your separate permission, Crashlytics sends crash and application-not-responding reports, stack traces, app version, operating system and device information, and installation identifiers to Google to diagnose failures and improve stability. The developer can view these reports in the Firebase console. If Analytics is also enabled, reports may include recent Analytics events as breadcrumbs. We do not set user IDs or add torrent names, magnets, file contents or collection contents as custom Crashlytics logs or keys. Automatic exception messages can contain runtime context, potentially including file paths or other values involved in a failure.

Automatic reporting is disabled by default. Enable Crash reports and select Save choices in Settings > Usage and diagnostics to authorize reporting independently of Analytics and advertising. The SDK may store reports locally while reporting is disabled; enabling it also permits sending pending reports. When refusal is applied, and on app openings without permission, the app requests deletion of unsent reports. Disabling this option stops future automatic reporting; it does not retract reports already sent. Your choice and notice version are stored locally. Crashlytics retains crash reports and associated identifiers for 90 days before beginning removal from live and backup systems. See Firebase privacy information.

Android permissions

• Internet: connects to peers and trackers, retrieves metadata, and checks for updates. It also supports AdMob, consent checks, and Firebase Analytics and Crashlytics requests on Android.
• SDK support declarations: the Android build also declares basic phone-state access, wake locks, and install-referrer access through its dependencies, supporting network/device operation and installation measurement.
• Network state: applies preferences such as Wi-Fi only and pause while roaming.
• Foreground service: keeps user-requested downloads and seeding active while the application is not visible.
• Notifications: displays transfer progress and background controls when you grant permission.
• Legacy storage: on older Android versions, writes files to the public Downloads folder. Current Android versions use the platform storage model without requesting broad file access.
• Advertising-related permissions: the integrated Google SDKs declare access to advertising identifiers and applicable Android advertising services. These declarations are distinct from runtime permission prompts; availability and controls depend on the Android version.

Denying a permission may disable only the feature that depends on it. You can review permissions at any time in the operating system settings.

Purposes and legal bases

Information is processed to:

• perform the downloads, uploads, creation, and organization that you request;
• save preferences and restore sessions locally;
• protect file and package integrity through format, path, size, and hash validation;
• provide updates and respond to support or privacy requests;
• measure Android app usage through Firebase Analytics when enabled;
• diagnose Android crashes through Firebase Crashlytics when enabled; and
• fund the Android application through ads, measure ad delivery, maintain ad security, prevent fraud, and honor privacy choices.

Where Brazil’s General Data Protection Law, Lei Geral de Proteção de Dados Pessoais — LGPD (Law No. 13,709/2018), applies, processing necessary to perform requested transfers and manage local settings is based on performance of the requested service. Security and abuse-prevention processing may rely on legitimate interests, subject to necessity and protection of your rights. Support correspondence is used to answer your request; relevant records may also be processed to comply with legal obligations or establish, exercise, or defend legal rights.

Optional Firebase Analytics collection and automatic Crashlytics reporting rely on your separate consent, which you can withdraw in Settings. Advertising processing follows the applicable privacy choices and legal requirements described in Section 06; permission to request ads does not by itself mean permission to personalize them. Accepting the Terms of Use is not consent to optional data processing. Advertising, Analytics and Crashlytics choices are described in Section 06. This policy does not replace consent where the law requires it.

Sharing and sale of information

TorrentDeck does not sell or rent your download history, magnet links, or files. Technical and advertising data are transmitted to Google when AdMob is used; usage and crash reports are sent when their respective optional choices are enabled, as described in Section 06. Ad delivery may involve additional technology providers. Some jurisdictions define certain advertising disclosures as a “sale,” “sharing,” or targeted advertising even without a monetary payment. The absence of a payment does not exclude those definitions. Consult the advertising choices in Section 06 and contact the project about your rights.

P2P participants receive information through the transfers and discovery described in Section 04. Studio MWD and website hosting providers receive requests for official pages and the update manifest. Application stores and installer hosting services receive requests when you access their distribution channels. Information sent directly to the project may also be disclosed when necessary to comply with law or a valid order, or to establish, exercise, or defend legal rights.

Retention and deletion

Local application data

Sessions, preferences, update caches, advertising-frequency records, and library records remain locally until you delete the relevant records or application data. Removing a transfer may offer a choice to keep or delete its files; it does not necessarily remove a separate library record, exported package, or backup copy.

On Android, clearing application storage or uninstalling normally removes private application data. TorrentDeck disables Android cloud backup for its private data. Public files are separate. On Windows, uninstalling preserves the user’s application data. After closing TorrentDeck, you can delete its private data folder, normally %LOCALAPPDATA%\TorrentDeck. If LOCALAPPDATA is unavailable, the fallback is .torrentdeck/TorrentDeck under your home folder. This removes saved sessions and library records; download folders and Windows preferences stored separately must be managed separately.

Files in public folders

Downloads and creations stored in public folders may remain after the application is uninstalled. Delete them through the system file manager or through an available removal option in TorrentDeck.

Information held by third parties

Records maintained independently by peers, trackers, website hosts, file-hosting providers, internet providers, and Google follow the applicable service policies. Analytics retention also depends on the project’s property settings; no fixed retention duration is specified here. Clearing local data does not delete those records. The project can address requests concerning data within its control, including through available provider tools, but cannot delete independent P2P records. Information sent directly to the project for support is retained only as long as reasonably necessary to respond, prevent abuse, comply with law, and establish, exercise, or defend rights.

Security

TorrentDeck uses controls including path and hash validation, .tdeck size and decompression limits, an allowlist of internal package files, a preview before downloads begin, and HTTPS for update checks. The application does not automatically open or execute downloaded files.

No system is completely secure. The BitTorrent protocol and UDP trackers may not provide end-to-end confidentiality. Evaluate file sources, keep your operating system up to date, scan potentially executable content, and use only networks that you trust.

International data transfers

BitTorrent swarms are global, so your device may communicate with peers and trackers in other countries. Website and installer hosting providers, and their infrastructure may also process technical data outside your country. Google, through AdMob, Firebase Analytics and Firebase Crashlytics, and applicable advertising technology providers may process data in countries where they or their service providers operate, subject to their transfer safeguards and applicable law.

Children and teenagers

TorrentDeck is not specifically directed to children and does not request an age profile or account. Minors should use the application only with the knowledge and guidance of a parent or legal guardian, in accordance with the store age rating, local law, and rights governing any material accessed or shared.

The current app does not verify users’ ages. Parental authorization to use the app does not itself authorize advertising, Analytics or Crashlytics processing. If you believe a child’s information has been processed improperly, contact the project without posting the child’s data publicly.

Your privacy rights and choices

Depending on applicable law, you may have rights to request confirmation of processing, access, correction, information about sharing, anonymization, restriction, deletion, portability, objection, or review of automated decisions, and to withdraw consent where consent is the legal basis. Brazilian users can learn more from the Brazilian data protection authority (ANPD).

Because TorrentDeck does not maintain accounts or a central download database, most application data can be managed and deleted directly on your device. For information controlled by the responsible developer, including support correspondence and applicable Analytics or Crashlytics records, submit a request to the private contact below. Reasonable information may be required to verify identity and prevent unauthorized disclosure.

Requests to exercise rights under the LGPD are free of charge and will be handled within applicable legal deadlines. If we cannot identify a relevant record or cannot fulfill part of a request because of a legal retention obligation, we will explain the reason. You may also raise a complaint with the ANPD or the competent consumer protection authority.

Advertising controls may be available through TorrentDeck’s privacy options, Android Advertising ID settings, and Google’s privacy controls. Withdrawing consent will not affect processing already performed lawfully before withdrawal. You can withdraw Analytics or Crashlytics consent in Settings > Usage and diagnostics, as described in Section 06. Changing ad preferences does not change that separate choice. You may contact the project about access, deletion, or objections concerning data it controls, without posting identifiers publicly.

Changes to this policy

This policy may be updated to reflect changes in TorrentDeck, applicable law, or third-party services. The effective version will display its “Last updated” date at the top of this page. A material change, including changes to advertising, analytics or diagnostics, may also be highlighted in the application, distribution page, or official website before or when it takes effect.

Updating this policy or continuing to use the app does not grant new consent for optional processing. Where a new purpose or material change requires consent, it must be presented for a separate choice before that processing is enabled.

Contact

Send privacy questions, data rights requests, and security reports to the private email below. Include only the information needed to describe your request; additional details can be arranged privately if necessary. Share sensitive information, such as magnet links, info hashes, file names, IP addresses, or identifiers, only if needed to handle your request.