SyncWatch Privacy Policy

Updated 25 October 2026

SyncWatch synchronizes HTML video playback, pause, seeking, speed and content selection between participants in a room. It has no media library and does not transmit video or audio.

Data used for shared viewing

The selected relay server and room participants process:

• The room’s secret access code.
• The viewing-page URL, including parameters needed for content selection, and the selected episode, season and audio track.
• The display name you choose, which can be a nickname.
• Playback, pause, seeking position, speed, buffering and advertisement events.
• Quick messages and text you send in chat (up to 200 characters).
• A temporary connection identifier, regenerated when you connect.

These data pass through the relay to synchronize the room. HTTPS/WSS encrypt the connection, but the selected server processes the contents. End-to-end encryption is not provided.

Presence and friends

When presence sharing is enabled, roughly once per minute the extension sends your public installation identifier, display name, current room on the selected server, and hashes of friend identifiers allowed to see your status. Requests are signed by the installation’s private key and bound to the server, request body and time. The server receives the public key and signature. The private key stays on your device and is never included in invitation links. Hashing the access list does not prevent the server operator from associating connections between users.

Only confirmed recipients can see presence. Status expires after 150 seconds without an update; expired records are removed by a maintenance alarm. Turning sharing off sends a status-removal request and stops periodic sending and querying; if the network is unavailable, the expiry still applies. Changing servers revokes the previous presence. With multiple tabs, the first connected room on the selected server is published; solo tabs are not shown as shared viewing.

A friend invitation uses a separate random token valid for 7 days. The server stores its hash and expiry; creating a new link replaces the previous link. Friendship confirmations remain until the client acknowledges them, for at most 14 days. The friend list is stored in the browser; the server temporarily processes access lists and friendship confirmations.

What SyncWatch does not do

• No SyncWatch account, email address, telephone number, postal address or payment details are requested. Your chosen display name is shared.
• Viewing history and chat are not recorded in permanent application storage on the server. Current room state is temporarily held in memory.
• No page text, screen recording, video or audio is transmitted. The extension reads the URL, video elements and episode/audio controls needed for synchronization.
• Data are not sold or used for advertising, profiling or creditworthiness decisions.
• No analytics, trackers or third-party remote code are included.

Storage on your device

Room code, display name, server address, sync tolerance, toggles, language and appearance preferences are stored in storage.local. Tab connection intentions use storage.session. The room code and name are sent to the server and room participants when connecting.

The installation identifier and private key, friend list, incoming requests and acknowledgements are stored locally. Up to 50 chat messages and the draft are held in the background session’s memory; leaving or restarting the worker clears that history.

Permissions

• storage saves preferences and local installation data.
• alarms schedules connection maintenance, update checks and friend presence. The timer itself transmits nothing; the extension’s code performs the described requests.
• Access to websites and frames detects HTML video and player controls across sites whose domains cannot be listed in advance. Shared navigation is restricted to the current viewing site; leaving that site switches to solo mode.

Server infrastructure

The default relay runs on Cloudflare Workers. You can select your own compatible server. Room messages are relayed in real time without a permanent application chat archive. Your chosen server operator and Cloudflare process network connections according to their own operating policies, including any infrastructure logs.

Children

SyncWatch is not directed specifically at children. Data processing is described above; avoid sharing sensitive information in names or chat.

Changes

Material changes will update this page and its revision date.

Contact

Privacy questions: strikec71@gmail.com.