Privacy, without the fine-print fog.
SideStream synchronizes playback between two browsers. It does not operate accounts, analytics, advertising, chat, or a media relay.
Only what synchronization requires.
After you explicitly grant permission, SideStream locally examines the currently rendered Telegram Web conversation to recognize complete protocol messages beginning with /ss1:. These messages contain short-lived WebRTC connection metadata and expire after ten minutes.
On supported video pages, SideStream locally reads the active service, title identifier, playback position, paused state, duration, and playback rate.
Your conversation and media stay yours.
SideStream does not read Telegram credentials or cookies. It does not store, log, sell, or transmit ordinary Telegram messages. It never captures, decrypts, relays, or redistributes video or audio.
Telegram says hello. WebRTC carries the controls.
Connection messages are sent through the Telegram conversation you select. Playback commands are sent to the other participant using WebRTC’s encrypted DataChannel. STUN infrastructure may process network addresses to establish a direct connection. No SideStream-operated server receives chat contents, playback activity, streaming credentials, or media.
Temporary by design.
Chrome extension storage remembers only your local consent choice. Signaling assemblies remain in memory until completion, expiry, reload, or tab closure. Peer and playback state remain in memory while the SideStream panel is open.
Built to satisfy Chrome’s user-data rules.
SideStream’s use of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Data is used only for playback synchronization, transferred only as necessary for that feature, never used for advertising, and never made available for human inspection.
Stop whenever you want.
Select Disable protocol-message access in the SideStream panel, close Telegram Web, close the panel, disable the extension, or uninstall it to stop processing. Uninstalling also removes the locally stored consent value.
Questions can be filed through the project’s GitHub issue tracker. Material policy changes will appear here with a new effective date.