← Stream Party

Privacy policy

Effective 8 November 2026 · Developer: myanpetra99

Stream Party synchronizes video playback and provides chat for people in an invitation-only watch party. It does not stream or copy your video. Party messages are shared with other participants and are not end-to-end encrypted. Anyone with the room code can join an active party.

Information handled by the extension

When data is used

The panel reads video-page information when you open it or choose a tab. Starting a party, manually joining, or opening a valid hosted invitation starts the party connection. A hosted invitation automatically joins using a generated name and opens the linked video. While connected, playback state is exchanged automatically, and chat messages are transmitted when you send them. Closing the chat panel keeps the party connected and shows new chat messages using your selected floating, toast, or icon style.

Purpose and sharing

We use this information only to provide and maintain synchronized playback, invitations, chat, reconnection, and security. We do not sell user data, use it for advertising, or use it for credit or lending decisions. We do not add advertising trackers or analytics SDKs to the extension. We do not read cookies, passwords, subscription credentials, unrelated page text, or video files.

The default service is hosted by Vercel, with active room data stored using Neon Postgres. These providers process data to operate the service. Hosting providers receive connection metadata such as IP addresses, request times, and user agents and may retain operational or security logs under their own policies. We do not log chat payloads in application logs. The optional test cinema loads its sample video from Google-hosted storage, which receives the network request. Your video website continues to process information under its own policy.

Other party participants receive your display name, messages, playback activities, and membership status, and may retain or copy what they see. If you select a custom relay, its operator receives party data; that operator’s privacy practices apply. Only use a relay you trust.

Security and access

Remote relay connections use WSS, hosted pages use HTTPS, and database connections verify TLS certificates. Plain WS is allowed only for a relay on your own device (localhost) during development. Local extension storage is managed by your browser; protect access to your device and profile. Party data is not end-to-end encrypted, so the service operator and infrastructure providers have technical access. Human access is restricted to your explicit support consent, security/abuse investigations, or legal obligations. No system can guarantee absolute security.

Retention and deletion

The relay retains up to 100 recent chat messages and playback activities for an active room. Leaving removes your membership, but earlier messages stay available to remaining participants. The last participant’s explicit Leave deletes the active room. An unexpected disconnect reserves membership for up to 45 seconds while host duties pass to the earliest connected participant once detected. A saved identity automatically reconnects; if it has expired, the extension rejoins the same room when it is still active. A native browser alarm wakes recovery for an active party if Chrome suspends the worker; it is cleared when you leave or the room ends. Inactive database records expire after 120 seconds and are physically removed during later room creation or health checks; this is not an immediate deletion timer. Provider logs and backups may retain data under provider retention policies.

Use Leave or close the connected video tab to stop sharing playback. Uninstalling removes the extension’s local settings. Revoke website access in Chrome’s extension settings to restrict video detection. Recipients may keep copied messages or invitations independently. For a privacy or deletion request, use the developer contact listed in the Chrome Web Store or the developer’s GitHub profile. Do not post private chats, invitation links, or reconnect tokens publicly.

Limited Use and policy changes

Stream Party’s use of user data complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. Data is used only for the disclosed watch-party functionality and related operation and security. Changes to this policy will be published here with an updated effective date.

Help & support · Developer on GitHub