Privacy Policy

KickLab is a browser extension for Kick.com. This page explains exactly what data it touches, when, and why — in plain language, matching what's declared in the Chrome Web Store and Firefox Add-ons listings.

The short version

No personal data is collected, stored, or transmitted. KickLab has no analytics, no tracking, and no remote logging. The only data stored anywhere is your settings, kept in your browser's own extension storage. A handful of optional, off-by-default features send a small amount of data to make that specific feature work — each is listed below.

KickLab badges (off by default)

Chat → Display → KickLab badges shows a small badge next to your name in chat for other KickLab users, and theirs for you. If you turn it on, the first time you chat the extension sends your Kick user ID, username, and license key (if you're a Founding Supporter) to our own badge-lookup service (api.kicklab.app, a Cloudflare Worker we operate) so it can tell other KickLab users which badge to show you, and vice versa. While the setting is off — the default — no lookup or registration ever happens.

Founding Supporter license validation

Redeeming a license key, and the periodic re-check while you have one active, sends only the license key to that same Cloudflare Worker, which validates it against our payment provider (Polar) server-side and returns just whether it's valid. This happens regardless of the KickLab badges setting above. No other purchase or account details are sent or stored by the extension.

Monthly / Annual subscription activation

Activating a subscription sends the email address you checked out with to that same Worker, which looks it up against Polar and emails a one-time 6-digit code to that address — the email itself is never stored, only used for that one lookup. Entering the code returns an opaque activation token (not your email) that's stored on your device and used for subsequent status checks. Subscription status is kept in sync via Polar's webhooks server-side; the extension never sends your purchase details anywhere beyond that one activation step.

Watch time (off by default in the sense that nothing leaves your device)

Settings → Watch time records how long you've watched each channel, entirely in your browser's local storage. This is never transmitted anywhere — not to us, not to any third party — and can be cleared at any time from that same settings panel.

Highlighting your own @mentions

The extension reads your logged-in Kick username from the page and caches it in the page's own local storage so it can highlight @mentions of you. This stays on your device and is never transmitted.

Acting as you on Kick

For Multi-View's posting/replies/follows, and for features that act as you on the main site (Timeout/Ban, quick clip, stream-info edit), the extension reads your kick.com session_token cookie to authenticate those actions to kick.com only. It is never sent anywhere else and is not stored by the extension.

Multi-View's and Fullscreen Chat's live chat

To show each open stream's live chat, Multi-View and Fullscreen Chat connect directly to Kick's own public Pusher WebSocket — the same real-time channel Kick's own player uses internally — rather than polling or scraping. This is a read-only subscription to public chat messages; no personal data is sent to establish it. The extension also periodically checks our own config endpoint (api.kicklab.app/v1/config/pusher) for the current Pusher app key, so a future change on Kick's end doesn't require a new extension release — that request sends no user identifiers, just a lookup for the current value, and falls back to a hardcoded default if it's unreachable.

Shareable Multi-View links

Multi-View's "Copy share link" button builds a kicklab.app/mv/... link containing only the channel names (and layout) you chose to share — no account or personal data. Visiting that link runs a small script on this site that checks whether KickLab is installed and, only if you click "Open," reads the channels from the link and asks the extension to open them in Multi-View. Nothing is sent anywhere by just landing on the page.

Third-party emote data

The extension fetches public emote lists from third-party emote services so it can render their emotes:

• 7TV — 7tv.io, cdn.7tv.app
• BetterTTV — api.betterttv.net, cdn.betterttv.net
• FrankerFaceZ — api.frankerfacez.com
• Kick's own emote list/CDN — kick.com, files.kick.com

These requests send no user identifiers; they only ask for a channel's or the global emote set.

Permissions

• storage — saves your settings and syncs them across your signed-in browsers.
• notifications — the optional desktop alerts for a followed channel going live or an @mention in chat (both off by default).
• alarms — runs the periodic "is a followed channel live?" check on a timer.
• cookies — Multi-View posts chat messages, replies, and follows as you, reading your kick.com session_token cookie to build the auth header Kick's own API expects. Read on your device only, sent solely to kick.com.
• Host access to kick.com — required to run the content scripts that adjust the player and chat, and for the channel API calls Multi-View, the Following-sidebar hover preview, and the stream schedule calendar all make.
• *.live-video.net — Kick's Amazon IVS video CDN; Multi-View's custom player, and the Following-sidebar hover preview's optional live-video mode, both fetch segments directly from it.

No tabs, webRequest, or broad all-sites host permissions are requested; the extension runs only on Kick and the Kick-owned/third-party endpoints listed above.

Questions

KickLab is an independent project, not affiliated with Kick. If you have a question about this policy, a bug to report, or a feature request, email contact@kicklab.app — or use the "Contact us" link in the extension's own Settings panel.