Legal

Framework & Privacy Protocol

Parayoo operates as a peer-to-peer video chat experience with minimal signaling infrastructure. Review the operational rules, session controls, and privacy expectations below.

Terms and Conditions

Protocol Access

Protocol Access

By starting a session on Parayoo, you acknowledge that connections are established directly between users through peer-to-peer media negotiation. Access to signaling is limited to lawful personal communication and may not be used to reverse engineer, overload, or disrupt the service.

Identity and Authentication

You remain responsible for the security of the device, browser session, and local media permissions used to access Parayoo. We do not require account credentials for standard matching, and we do not request recovery phrases, wallet keys, or remote desktop privileges.

Content Transmission

Users retain responsibility for what they send during live sessions. Parayoo coordinates connection setup and session routing metadata, but abusive traffic, illegal material, signal flooding, or automated scraping activity may result in session termination or network exclusion.

Warning

Users who attempt to abuse connection setup, impersonate system messages, or distribute unlawful content may be blocked from future sessions.

Privacy Policy

Zero-Knowledge Architecture

Zero-Knowledge Architecture

Our signaling layer is designed to broker introductions between browsers without storing the actual live video or audio content exchanged during a normal session. Session metadata is minimized to what is required for connection setup, reliability, and abuse prevention.

Encrypted at Source

Media is protected in transit using browser-level WebRTC encryption before packets leave the device.

Ephemeral Session State

Temporary session data is cleared when a match is skipped, disconnected, or replaced by a new chat.

Cookie and Token Management

Parayoo does not rely on advertising trackers to run random chat sessions. Functional session tokens may be used to maintain a live handshake, connection state, and abuse controls, and they expire once the session ends or the browser disconnects.

Third-Party Infrastructure

Some connection paths may depend on standard WebRTC network infrastructure such as STUN or relay services. Those providers are used strictly to establish or stabilize communication paths and are expected to process only the minimum network data required for delivery.