Watchside — Privacy Policy

Last updated: 2 September 2026

Applies to: the Watchside browser extension for Chrome and Firefox, and the watchside.app website.

Watchside shows you which of your friends are watching Twitch, and lets you join them. This policy describes exactly what it handles, where that goes, and what it never touches. It describes the software as it is actually built, not as a category of software generally behaves.

Watchside does not sell your data, share it with third parties, or use it for advertising of any kind. There is no advertising in Watchside and no advertising or analytics SDK in it.

Who runs it

Watchside is an independent project. Contact: anoteros.dev@gmail.com — the same address for privacy questions, support, and data deletion requests.

Where your data goes

Everything Watchside stores about you is in two places, and nowhere else:

1. Your own browser, in the extension's own storage (chrome.storage.local on Chrome, browser.storage.local on Firefox).
2. Watchside's backend, hosted on Supabase.

Beyond that, the extension loads some images and looks up emote sets, which means your browser contacts a small number of other servers. None of them is sent your account, your friends, or anything you write, but a request is a request, so they are listed here in full:

Scroll the table sideways to see every column.

No account, user id, friend code, token or cookie of ours is attached to any of them, and Watchside sends nothing to 7TV about who you are, who your friends are, or what you type.

What any web request unavoidably reveals

We would rather say this than let the list above imply more than it can.

Every request a browser makes — including the ones above, and every request to Watchside's own backend — necessarily tells the server it is talking to your IP address, because that is how the reply gets back to you. This is true of every website you visit and is not something an extension can opt out of.

Watchside does not store your IP address, and never puts one in the database. There is no IP or device column anywhere in it, and no IP appears in analytics, in feedback, or in anything another user can see. Our hosting provider processes IP addresses in the ordinary course of serving and protecting the service, as any host does; the same is true of 7TV and Twitch for the images above.

What Watchside handles

Scroll the table sideways to see every column.

The Twitch authorisation Watchside stores

When you sign in, Twitch issues Watchside a credential that represents your connection. Watchside stores it on its server, encrypted, and removes it from your browser entirely.

Why it is kept. Watchside is trying to answer one question honestly: does seeing where your friends are watching actually lead you to creators? Answering it means asking Twitch a question at the moment a friend leads you somewhere, and Twitch only hands over the means to ask once, when you sign in. Keeping it is the only way to ask later.

How it is protected.

• It is encrypted before it is written down, with a key that is not stored in the database. Someone with a complete copy of the database still cannot read it.
• It is never sent to another user, never shown in the extension, and never written into analytics or logs.
• It never comes back to your browser. Not even to you.

How it ends.

• Disconnect Watchside on Twitch and the credential is destroyed, along with anything Watchside worked out about your relationship with creators. Your Watchside account and friends are untouched.
• Delete your Watchside account and it goes with everything else.
• Signing out does not remove it — signing out ends a session, it does not withdraw a permission.

What it is used for. Exactly one thing, described in full in the next section.

The one check Watchside makes with it

When you click JOIN in Watchside to watch a creator your friends are watching, and you have granted the Twitch permission described below, Watchside asks Twitch a single question at that moment:

Did this person already follow this creator?

The answer — yes or no — is recorded once against that JOIN, and is used only to produce aggregate figures about whether friends help people find creators they were not already watching.

When it happens, and when it does not.

• Only for a JOIN you clicked in Watchside, on a creator a friend was watching. That is the whole population.
• Not when you browse Twitch normally, type a channel name, follow a link, or arrive any other way. Watchside asks nothing about those.
• Not if you have not granted the permission. Watchside carries on working and simply records nothing.
• Not afterwards. If the check cannot be made at the moment you join, that JOIN has no answer and never gets one later.

The permission. This needs one Twitch permission, user:read:follows, which you are asked for on Twitch's own consent screen when you connect Watchside. It is optional: everything in Watchside works without it, and granting it never changes who you follow. It is the only Twitch permission Watchside asks for beyond signing you in.

What Watchside does not do with it.

• It does not read the list of creators you follow. It asks about one creator, the one you just joined, and nothing else.
• It does not watch whether you follow someone afterwards, and it does not claim that Watchside caused any follow. It records only what was already true at the moment you joined.
• It does not go back over JOINs you made in the past.

How it ends. These answers are Twitch-derived, so they follow the credential: disconnect Watchside on Twitch and they are deleted, along with the credential itself. Deleting your Watchside account deletes them too, with everything else. Signing out deletes neither.

Your own Watchside activity — that you clicked JOIN, that you arrived, how long you watched — is Watchside's own record of its own product, and is not deleted by disconnecting Twitch. Deleting your Watchside account does delete it.

Two kinds of chat, with two different lifetimes

The stream session that appears when you and your friends are watching the same thing is deliberately temporary: it is swept after thirty minutes and is not a history you can scroll back through.

Group chat is not. A group is a place you made on purpose, so its messages stay until the group is deleted or your account is. If you want a conversation that disappears, use the stream session; if you want one that lasts, use a group.

Your visibility setting

The account panel lets you choose whether friends see your activity, see only that you are online, or see nothing at all. This is applied when your presence is written, not when somebody reads it — if you have chosen to hide your activity, the channel is never stored, so there is nothing for anyone to read.

Analytics, specifically

Watchside records how the product is used so we can tell whether it works. It is built so that it cannot carry personal content:

• Every property is a small fact — a count, a bucket, a true/false, or a short word from a fixed list. Values are capped at 64 characters and unknown keys are discarded by the server, so there is no way to attach a message, a search term, a URL, an email address or a token even by mistake.
• Never recorded: message bodies — from either the stream session or from group chat — which emote you used, what you searched for, your friends' identities, who you blocked or muted, email addresses, friend codes, browsing history, or any Twitch or Supabase token.
• Twitch channel names are recorded for social events — a friend's activity being shown to you, a JOIN, a shared watch. This is how we can tell whether Watchside actually sends people anywhere. It is a channel, not a URL, and only for channels Watchside itself surfaced or you acted on. Watchside does not record your browsing generally, on Twitch or anywhere else.
• Watchside records how long you watch a Twitch channel. This is described in full under "Viewing time" below.
• On Firefox, diagnostic events are not recorded at all. See "Technical and interaction data" below.
• Events are labelled with the build they came from, so beta data can be deleted separately from anything else.

How you found Watchside

If you arrive through a campaign link, Watchside records which campaign it was. A campaign link looks like watchside.app/c/lirik-oct — the last part is a short code naming a campaign, which might be a post on TikTok or X, or a mention by a particular streamer.

Here is exactly what happens and what is kept:

• The link carries one short code and nothing else. It does not contain anything about you, and it is the same link for everybody who sees it.
• The code is held on your own device until you sign in to Watchside. If you never sign in, it is never sent anywhere, and it is discarded after seven days whether you sign in or not.
• When you do sign in, Watchside stores that code against your account, along with when it happened. Watchside works out what the campaign means — which channel it was, which streamer it was associated with — on its own server, from a list it keeps. None of that comes from the link, so a link cannot claim to be something it is not.
• The first campaign you arrived through is kept as how you found Watchside, and is not overwritten if you later click a different Watchside link. The most recent one is kept separately.

What this is not. It is not a cookie, not a tracking pixel, and not a third-party analytics or advertising product — Watchside uses none of those, anywhere. It cannot tell where else you have been, and it does not follow you across sites. It records that a campaign brought an account, and nothing about the browsing that happened in between.

Why it exists. Before spending real effort or money telling people about Watchside, we want to know which of those efforts actually bring people who go on to use it. Without this, the honest answer would be that we have no idea.

The link may carry extra labels for the advertising platform. A campaign link can end with things like ?utm_source=reddit — standard marketing tags that let the platform we placed the ad on, and the browser stores, count how much traffic a campaign sent them in aggregate. Watchside itself ignores them completely. They are generated by us from the campaign's own definition, they say nothing about you, and nothing in Watchside ever reads one back: editing them changes nothing at all, because the short code is the only thing that decides anything. The browser store links carry the same kind of label, which is how Google and Mozilla can tell us "this many people reached the listing" without telling either of us who they were.

A friend's invite is a different thing. watchside.app/i/… links record which Watchside user invited you, which is covered elsewhere in this policy. The two are stored separately and neither replaces the other.

Deleting your Watchside account deletes this along with everything else.

Viewing time

Watchside records how long you watch a live Twitch channel. When you are watching a channel, Watchside measures that stretch of time and records its length, together with the channel name.

We are stating that plainly because it is a real change in what Watchside keeps. Until now Watchside recorded how long you watched with a friend; it now also records how long you watched.

Why. Watchside's purpose is to bring people to streams together. We cannot tell whether that works without knowing whether it leads to people actually watching — and whether they come back to a streamer they met through Watchside. Without this, we can only measure the part of your viewing that happened to involve a friend, which tells us nothing about how much difference Watchside made.

If you have more than one stream open, each one is counted separately. Two streams open for an hour are recorded as two one-hour stretches, not one. That is how we can tell how much Twitch viewing Watchside is part of; it is not a claim that you were sitting there for two hours, and we do not describe it that way.

A stream still counts while its tab is in the background — on another monitor, or behind something else. We also record how much of each stretch the stream was the one you had in front of you, because "playing in the background" and "the thing you were watching" are genuinely different and we would rather not confuse them.

What is recorded for each stretch of viewing:

• how long it lasted
• how much of that time it was the stream in front of you
• which channel
• whether you got there by pressing JOIN in Watchside
• whether a friend was watching with you at any point during it
• why it ended — you closed or left the stream, the stream ended, you signed out, or Watchside stopped being able to observe

What is not recorded:

• Not the video, the title, the category, the viewer count, or anything else about the stream. The channel name and a duration are the whole of it.
• Not what you watch generally. Only channels on Twitch, and only while Watchside is running and you are signed in.
• Not other tabs. Watchside only ever looks at Twitch. A stream counts whether or not it is in front of you, but nothing else you have open is seen at all.
• Not offline channels. Sitting on a channel with no stream running records no viewing time.
• Not time we did not observe. If your computer sleeps or the browser stops Watchside in the background, the interval is closed at the last moment we could actually see, and the gap is never counted as viewing.

What is stored on your device: only the stretches of viewing currently in progress — one per stream you have open — and each is deleted as soon as it ends. If you are not watching anything, there is nothing about your viewing stored on your device at all.

This is not shared with anyone. It is not visible to your friends, it is never sold or shared with third parties, and it is not used for advertising.

Feedback, specifically

If you send feedback from the account panel, we receive what you wrote, plus a small set of diagnostics assembled by the extension: the Watchside version, the build, which Watchside tab was open and whether the panel was collapsed, the Twitch channel you were on and whether you were on a channel at all, how many friends you have, whether a stream session existed, and whether the two realtime connections were healthy. On Chrome it also includes your browser name and major version (e.g. "Chrome 141"); on Firefox that field is omitted, because it is browser information and Watchside collects none of that on Firefox.

That is the complete list, and it is enforced by the server, which rebuilds it field by field and discards anything else. Feedback never carries tokens, cookies, message contents, what you were typing, or the identities of your friends. We can see who sent it, so that we can follow up.

What Watchside never does

• No advertising, ever, and no use or transfer of your data for personalised, retargeted or interest-based advertising.
• No third-party analytics or tracking of any kind. No Google Analytics, no Meta pixel, no TikTok pixel, no advertising SDK, no fingerprinting, and no cross-site tracking. The watchside.app website sets no cookies and makes no requests to anyone else at all. Campaign links (see "How you found Watchside") carry a code Watchside itself issued, and nothing about you.
• No selling or sharing of personal data with third parties.
• No reading of web pages. Watchside runs on twitch.tv only, and only to place its own panel and read which channel the page is showing. It does not read Twitch chat, scrape the page, or run on any other site — it cannot see any other page you have open. (It does load emote and avatar images from the servers listed under "Where your data goes"; that is fetching a picture, not reading a page.)
• No credential handling. Sign-in goes through Twitch's own OAuth page via the browser's identity API. Watchside never sees your Twitch password, and the extension contains no client secret.
• No Twitch access token in the page. Provider tokens stay in the extension's background script and are never given to the content script — the part that runs alongside Twitch's own code.
• No remote code. Everything Watchside executes ships inside the extension package. Nothing is downloaded and run.
• No use or transfer of your data to determine creditworthiness, or for lending purposes.
• No use or transfer of your data for any purpose unrelated to Watchside's single purpose — showing you which friends are watching Twitch, and letting you join them.

Permissions, and why

• identity — to sign you in with Twitch.
• storage — to keep, on your device: your sign-in session, your panel position and size, the people you have muted, your analytics session id, and the stretches of viewing currently in progress.
• alarms — to refresh your sign-in session periodically. The extension's background script is shut down when idle on both browsers, so this is the only way to schedule that.
• notifications — for the optional desktop alert when several friends gather on one channel. You can turn it off in the account panel.
• Watchside's own backend — sign-in, presence, friends, groups and rooms.
• https://7tv.io/* — looking up the emote set for the channel you are watching, as described above.

Where the two browsers differ. The Firefox add-on names our single Supabase project as the only backend it may reach. The Chrome extension asks for https://*.supabase.co/* — broader than it needs, though it reaches only that same project — and additionally lists https://cdn.7tv.app/*, which later builds drop because an image does not need a host permission to load. Neither difference changes what Watchside does or what it collects; the permission a browser shows you is a ceiling, not a description of use.

Watchside requests no access to sites other than Twitch, and cannot read any other page you visit.

What Firefox tells you at install

Firefox asks for consent to data collection in its own words, from what the add-on declares in its manifest. Watchside declares four things, and they map to the table above:

Scroll the table sideways to see every column.

Watchside does not declare personally identifying information: no email address, phone number, postal address, demographics or biometrics is collected anywhere. Your Twitch handle, display name and avatar are your own public Twitch profile, and they are covered by authentication information.

Technical and interaction data: Firefox collects none

Firefox has a fifth category, technical and interaction data — device and browser information, and crash and error reports. Mozilla only allows it as an optional permission, which would mean asking you a second question at install.

We would rather not collect it than ask. On Firefox, Watchside sends no error reports at all: three diagnostic signals that the Chrome extension does record — a caught error, a realtime connection changing state, and a group message being refused — are dropped inside the extension and never reach our server. They are not queued, not retried, and not sent later.

So there is no consent prompt and no analytics switch in Watchside for Firefox, because there is nothing to consent to or switch off. Everything else on this page still applies: the data listed above is what the add-on needs to do what it does, and Firefox asks you about it once, at install.

Watchside collects no device information on any browser, and no browser information on Firefox.

On Chrome, those three diagnostic signals are still recorded. They carry a call site and an error code from fixed lists — never a message, a URL, an exception text or a stack trace — exactly as the analytics section describes.

Your choices

• Hide your activity or go invisible — account panel, at any time.
• Mute somebody — local to your device; nothing is sent.
• Block somebody — removes the friendship, stops all Watchside contact between you, and is never disclosed to them.
• Sign out — clears the session from your device. It deletes nothing on the server: your account, your friends and your history are all still there when you sign back in.
• Delete your account — in the account panel, whenever you want. No email, no waiting on us.

It asks you to type your Twitch username first, because it cannot be undone. Deleting removes your profile, friendships, friend requests, group memberships, group and stream messages, presence, blocks, invites, referrals, badges, feedback and your analytics history. Nothing is kept back.

Two things worth knowing before you do it. Groups you created are deleted for everyone in them — a group cannot outlive its owner, so tell the others first if that matters. And messages you sent disappear from conversations other people can still see, which may leave gaps in them.

It does not touch your Twitch account, and it does not unfollow anybody.

• Uninstall — removes everything Watchside stored on your device. Data on the backend is removed on request as above.

Children

Watchside is not directed at children and follows Twitch's own minimum age requirements. Do not use Watchside if you are not permitted to use Twitch.

Changes

The product is changing, and this policy changes with it. Material changes will be reflected here, with the date at the top updated. The current version is always at watchside.app/privacy.

Watchside is not affiliated with, endorsed by, or sponsored by Twitch Interactive, Inc. or 7TV. "Twitch" is a trademark of Twitch Interactive, Inc.