Watch Party extension privacy
The SecureChat Watch Party browser extension keeps a group's playback in sync on YouTube and Netflix. This page covers what it accesses, what it sends, and what it keeps.
The short version
The extension reads your secure-chat sign-in so you don't have to log in twice. Only while you are in a watch party, it sends what you're watching and where you are in it to secure-chat's server so everyone else can follow. Chat in a party is relayed, never stored.
1. What the extension accesses
Your secure-chat sign-in
When you are signed in at secure-chat.uk, the extension reads your session token so it can connect to your account's watch parties. It is held in the browser's extension session storage on your own machine, is sent only to secure-chat's own servers (api.secure-chat.uk and auth.secure-chat.uk), and is discarded when you close your browser. It is never written to disk and never sent anywhere else.
The page you are watching
The extension only runs on the sites listed in its permissions: YouTube, Netflix and secure-chat.uk. It does not run on, read, or have access to any other page.
On a supported site, while you are in a watch party, these are sent to secure-chat's server so the rest of the party stays in sync:
- which site and which video or title you are on, and its link
- play, pause, seek position and playback speed
- whether an ad is currently playing, so the room can wait for it
- the video's title, for the party's queue
Messages you send in a party
Chat messages, emoji, GIFs and reactions are relayed to the other members of that party. They are held in the server's memory only while the party is running and are permanently discarded shortly after the last person leaves. They are not written to any database, are not readable by anyone outside the party, and cannot be recovered afterwards, including by us.
2. Requests the extension makes
| Where | Why |
|---|---|
api.secure-chat.ukauth.secure-chat.uk | Signing in, and relaying playback state and chat between the members of a party. |
secure-chat.uk | Reading your existing sign-in, and checking whether a newer version of the extension is available. |
api.klipy.com | Only when you open the GIF picker. Your search term goes to Klipy, our GIF provider, which (like any site you load) sees the request's IP address. Nothing identifying you or your account is attached, and your searches are not linked to your secure-chat account. |
Thumbnail images shown in a party's queue are loaded from the streaming site's own image servers, the same ones the page itself uses.
3. What the extension doesn't do
- No browsing history, and no record of what you watch outside a party.
- No analytics, telemetry, fingerprinting or advertising identifiers.
- No selling or sharing of data with third parties.
- No access to pages other than youtube.com, netflix.com and secure-chat.uk.
- No reading of your Netflix or Google account details.
- No downloading, recording or copying of video, and nothing that touches copy protection. It reads the player's position in the same way the page's own controls do, and it does not interfere with advertising: on YouTube it pauses the room until a member's ad has finished so nobody is pushed ahead.
4. Retention
Watch parties are temporary by design. A party exists in server memory while people are in it. When the last member leaves, it is deleted along with its chat, queue and playback position, after a short grace period that exists so a dropped connection or a closed tab can be rejoined. Nothing about the party is kept afterwards.
Your secure-chat account itself is covered by the secure-chat privacy policy. This page describes only the browser extension.
5. Your choices
- Leaving a party stops all playback information being sent.
- Signing out at secure-chat.uk invalidates the token the extension holds.
- Removing the extension from
chrome://extensionsdeletes everything it stored locally.
6. Changes
If this policy changes in a way that affects what is collected or where it is sent, the date at the top of this page changes with it and the change is described in the extension's release notes.
7. Contact
Questions about the extension or your data? We're happy to help.