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. RELAY 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 on the same machine. 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. Account, profile, library and security records may still be processed where required to operate and protect the ecosystem; they are 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.

The result is a clear division of responsibility: RELAY Web handles discovery and browser playback, Companion handles peer activity on the local computer, and PARALLAX provides the company and account infrastructure around those products.