Tarraz Logo Tarraz Download Manager ← Return to TDM
Official Compliance Policy

Privacy Policy for TDM Extension & Desktop App

Effective Date: October 11, 2026  |  Applies to: Browser Extension (1.4.1, 1.4.2+) & TDM Windows Desktop Companion

The Tarraz Downloader Extension is the official companion for the Tarraz Download Manager (TDM) Windows desktop software. TDM detects user-authorized downloadable media and files on enabled websites and hands them off to the local TDM desktop software on your personal computer for multi-threaded acceleration. The extension runs in an isolated Manifest V3 environment with zero third-party advertising, zero analytics trackers, and no remote code execution.

Google Chrome Web Store Core Disclosures:
  • No Data Selling: We do not sell, rent, monetize, or transfer user data to third parties, data brokers, or advertising networks.
  • Single Purpose: All data observed is strictly used to discover and hand off downloadable media to the local TDM desktop software.
  • No Cloud Storage of Media Credentials: Authentication cookies and request headers are never transferred to Tarraz cloud servers.

1. Data Collection & Scope of Use

On enabled websites, TDM observes HTTP request URLs, media response headers, Content-Type, and Content-Length. Media observations and necessary request authorization headers reside temporarily in browser session storage for up to 15 minutes and are removed by periodic cleanup within a further 5 minutes, bounded to a maximum of 2 MiB and 32 browser tabs. Page navigation, tab closure, or detection preference changes immediately invalidate and clear these observations. The extension strictly avoids inspecting response bodies, reading user input, or tracking general browsing history.

When analyzing multimedia streams, preparing format lists, or dispatching an authorized download, relevant URL-scoped session cookies and headers from the originating tab may be passed strictly over local loopback to the authenticated TDM desktop service at 127.0.0.1. These credentials are used exclusively by your local desktop application to establish authenticated connections with the media's originating CDN server (for example, cloud drives or purchased video downloads). Browser media cookies and authorization tokens are never sent to Tarraz cloud servers.

Background Stream Preparation

By default, approximately 500ms after visible video or audio starts playing in an active, non-private tab, the extension may transmit the page URL, relevant session cookies, and observed stream metadata to an already running and authenticated TDM desktop app. The desktop app contacts the origin server to prepare available format resolutions. This process never launches a closed desktop application, nor does it select or download any file. Hovering alone does not trigger analysis. To minimize background activity, only one background analysis runs at a time, enforced with a minimum 15-second throttle between starts. Users can disable this at any time by toggling "Prepare media lists when video starts playing" off in Extension Options for click-only on-demand detection.

Display labels and opaque selection IDs remain cached in worker memory for up to 90 seconds (maximum 16 lists) and contain no raw media URLs or cookies. Desktop catalogs containing stream URLs and temporary credentials automatically expire after 2 minutes and are purged within an additional 60 seconds (maximum 16 catalogs retained in memory).

2. Chrome Permissions Justification

3. User Control & Data Retention

Users retain full autonomy over the extension at all times:

4. Purchase, Licensing and Updates

Purchase details (email, transaction reference, and selected subscription tier) are processed securely for licensing validation. During desktop software activation, TDM submits the license key, customer email, and a pseudonymous cryptographic hash of the PC identifier over HTTPS to the Tarraz licensing API to bind the license to that PC. License and payment records are kept strictly isolated from browser extension media data. Desktop update checks query the Tarraz release endpoint solely for version metadata and executable installers. No browser media data is ever transmitted during licensing or update checks.

Trial verification also sends that hashed PC identifier and a random request nonce to the Tarraz licensing API over HTTPS. When upgrading an existing installation, its protected local trial start may be sent to preserve the remaining trial period. The server retains the first recorded trial start and expiry for that identifier so deleting local settings does not grant a new trial. Signed trial checks are cached locally for up to three days, within the original 30-day trial. Checks occur when the app is used; no browsing URLs, raw hardware identifiers, purchase email or passwords are needed for trial verification.

Installation activity reports

The desktop app sends a random installation identifier, app version and installation, activity or uninstall events over HTTPS. The service records receipt times to estimate installed and recently active copies. These reports do not include browsing history, download URLs, file names, purchase email or hardware identifiers and are separate from licensing. Offline reports are retried while the app runs. Uninstall reporting is best effort; no reporter remains running after uninstall. Aggregate installation counts do not identify unique people.

5. Contact & Publisher Support

For inquiries regarding this privacy policy or data rights, please contact the publisher:

Tarraz Group
Official Portal: https://tdm.tarraz.com
Developer & Support Inquiries: developer@tarraz.com