Private torrent streaming is not only about encrypting an account page. The important question is where peer connections, torrent transfer and media preparation actually happen. PARALLAX Companion is designed so those activities remain on the user’s Windows computer instead of passing through PARALLAX infrastructure.
Companion exposes a secured loopback service. Loopback means the service listens on the same machine and is addressed through a local endpoint rather than a public internet server. RELAY Web asks the browser for permission to reach that local service. Companion can then inspect a selected release, connect to peers and prepare a browser-compatible stream for playback on that device.
PARALLAX servers do not become a relay for the torrent payload. They provide account functions, catalogue presentation and the web interface, while Companion performs torrent networking locally. This separation reduces the amount of source activity that needs to reach PARALLAX and makes the trust boundary understandable: the local engine handles the transfer; the browser displays the result.
That does not mean PARALLAX sees no information at all. A verified account stores the email address, password hash, profile information and preferences required to operate the service. Signed-in features can store library selections and viewing progress so users can continue across the ecosystem. Security records such as session timestamps, device descriptions and IP addresses may be retained where necessary to protect accounts and prevent abuse. These are account-service records, not copies of Companion torrent traffic.
Companion also needs strong local security. RELAY verifies that it is talking to a compatible local service, uses a controlled pairing and permission flow, and avoids exposing the engine as a general public endpoint. Users should install Companion only from the official Companion download page, keep it updated and review the browser’s local-device permission when prompted.
Transparency matters when the connection fails. RELAY distinguishes a missing or stopped Companion from a pairing error. A first-time user receives installation guidance, while a returning user can continue browsing and start Companion from the system tray when ready. Playback attempts explain that the local engine is required instead of silently failing.
The result is a private torrent streaming model with clear responsibilities. RELAY Web handles discovery and browser playback. Companion handles peer activity on the local computer. PARALLAX stores the account data users ask it to synchronize, while torrent transfer and media preparation stay off PARALLAX servers.