Security and trust boundaries

Last technical review: 14 July 2026

This page explains the protections and user-visible trust boundaries you can rely on, including what Telepathy does and does not secure.

The video path

Telepathy does not proxy, upload or redistribute the video/audio stream. Each viewer receives media directly from the video provider. The Telepathy server processes room participation, playback coordination, chat and reactions, plus the operational metadata described in the privacy policy.

Not end-to-end encrypted: HTTPS/WSS encrypts traffic in transit to the Telepathy service, but room messages and controls are readable by the backend so it can relay them. Do not treat a room as an end-to-end encrypted messenger.

Room access

The room code/link is the room credential. Anyone who receives it can join while the room exists. Codes are random and rooms disappear when empty, but there is currently no separate room password or host approval queue. Share links only with intended participants.

Accounts and operator access

Account passwords are stored as salted scrypt hashes, not plaintext.
Account sessions use random server-side tokens with a 30-day expiry.
Operator access uses hardened credential storage, centralized attempt restrictions and expiring access controls.
Account deletion removes associated identifiable records from the live service as described in the privacy policy.

Abuse and resource controls

The service applies rate limits, authorization checks, input validation and bounded resource use. Database operations use parameterized queries. These controls reduce risk; they are not a claim that software can be perfectly secure.

Optional player and ad detection

Optional AI assistance uses scoped, expiring authorization and traffic controls. As detailed in the privacy policy, a request may include the watched-page URL and a limited technical representation of page structure, but excludes page text, scripts and form values. Ad skipping is off by default and is limited to the intended watch-party context.

Data lifecycle

Server-side data is limited to the categories and retention periods in the privacy policy. Live room state is temporary and may be lost during a service interruption. Chat content is not retained as durable history by default; an operator that enables content logging must disclose that configuration.

Availability boundaries

Real-time room state may be interrupted during infrastructure failures or maintenance. Participants may occasionally need to reconnect or recreate a room. Telepathy uses health monitoring and recovery controls, but does not promise uninterrupted availability.

Self-hosted deployments: the person or organization operating the service is responsible for secure configuration, access control, updates, backups and incident response.

Reporting a security issue

Email privacy@telepathy.video with a minimal reproduction, affected version and impact. Do not include passwords, active session tokens, room credentials or other people's data. No public bug-bounty program is promised by this page.