Your data

Privacy policy

Effective October 16, 2026 - Version 1.2.0

UltimateKick, by thesomeguy, is a personal Kick viewing workspace with multiview, chat filters, player tools and discovery preferences, plus optional local browser-tab audio controls. It has no developer server, developer telemetry, advertising SDK or separate account. Optional chat analytics runs locally.

Local data

Show advanced options is a local display preference, off by default. It restores settings sections that duplicate player controls and category navigation. The checkbox is included in preference backups and resets to off with default preferences. Hiding these sections does not start or stop media work, reset other preferences, record activity or add a request, permission or data store.

Plain-text quote previews use text already observed in your current chat buffer. They shorten the source to 240 characters and stay in page memory until their panel closes. Copy quote writes the reviewed text to your clipboard only at your request. Append to native draft preserves existing text, formatting and any native reply selection; it creates no reply reference and sends nothing. Current chat filters, frame/channel ownership and a bounded combined draft apply. These previews are not stored or backed up and make no new request. Kick receives the text only if you submit the native draft.

Moderation file imports read only a local TXT or CSV file you choose, up to 64 KiB, 1000 rows and 100 unique valid usernames. Valid names and bounded rejected-row details remain in a temporary review preview; the file path and original contents are not saved or uploaded. Applying a preview changes command fields only. You can explicitly save up to twelve named moderation presets containing usernames, action, timeout and reason in extension-local preferences and settings backups. Presets contain no account binding, selected chat channels, command results or native draft. Loading one requires review and does not prepare or send commands. Remove preset, resetting preferences or uninstalling deletes saved recipes; exported backups remain on your device until you delete them. Closing the panel discards its import preview and pending read. The separate reviewed native command workflow still uses Kick's existing account permissions.

Optional HTTPS moderation-list imports start only when you choose Load HTTPS list. Chrome may ask for access to that file's host. The chosen server receives a normal GET request, including the file URL and your IP address; requests omit account cookies and referrers and do not follow redirects. Only public UTF-8 TXT/CSV responses up to 64 KiB are accepted, with a ten-second request deadline. The URL, original response and review preview stay in memory and are not saved to preferences or backups. Cancellation, a changed source/command/channel, pausing UltimateKick or closing the panel stops pending work. Previewing or applying a list does not submit a moderation command. An accepted host grant remains until you revoke it in Chrome's extension settings.

Toolbar notifications for mentions, replies to you, important tool messages, Favorites live starts and Following live starts are enabled by default and can be switched off independently. The unread toolbar count can also be disabled. Open Kick pages publish eligible events to a shared inbox readable from the toolbar on any website. Local extension storage keeps the latest 200 short notifications: channel, sender, title, up to 300 text characters including an available live stream title, rendered/observation time, occurrence count, read state, an available public channel-avatar address and up to 1000 deduplication keys/fingerprints. Avatars reuse already observed native links, live toasts or existing live metadata without another profile lookup; approved Kick image requests omit credentials/referrers and unavailable images use an initial. The menu can show all retained entries. Read and unread history survives page/extension reloads and browser restarts, until Clear, source-off/enhancements-off, an applicable identity change, the 200-entry limit or uninstalling removes it. It has no 24-hour expiry. Clear retains bounded duplicate-prevention keys and a watermark so delayed older updates cannot restore entries. Source tab/document click targets and current live diagnostics stay separately in session storage and disappear when the extension session ends. Opening the menu or restoring history does not mark entries read or replay alerts. Clicking a row marks it read and focuses/opens its channel without opening settings; the check button only marks read. The history is excluded from backups, is not synced and is never uploaded.

Personal toolbar alerts use your manual username/aliases, or detect your username from the rendered Kick account avatar's alt label when no manual override is set. Detection reads no private application state, cookies or authorization tokens. The last detected identity is stored locally with notification history to associate personal entries with their account; an observed identity/alias change removes personal entries. Detected identity and history are excluded from backups; a manual override and source choices are local preferences included in backups. New replies can be recognized from Kick's rendered Replying to label or its supported incoming native reply event. Your own messages, filtered messages and loaded/restored chat history are excluded; duplicate native/DOM observations are suppressed. These popup notifications need no Chrome notifications permission. Reading the shared inbox does not require the selected page to be Kick; receiving new replies/mentions still requires an open native chat.

Background live alerts use supported same-origin Kick channel and signed-in Following metadata while a Kick tab is open, including when it is unfocused and the toolbar menu is closed. The first periodic check establishes a baseline; subsequent bounded checks detect observed offline-to-live transitions. Failed or missing results are not interpreted as offline. A supported live-start toast inside Kick's native notification container also supplies an explicit live event, mapped to Following and to Favorites when that channel is in your saved favorites. It can arrive before periodic checks. Favorites rotate in batches, and unsupported account/response/toast layouts can prevent alerts. The worker's alarm wakes registered Kick documents and restores scheduling after worker sleep; browser/device sleep or a discarded page can delay checking. Live state and channel lists remain in page memory. Up to 100 tab/document schedules without credentials, chat text or audio are in Chrome session storage, separately from the shared inbox. Disable live sources/enhancements or close/navigate the tab to stop its schedule; already collected notifications remain available according to their retention and source settings. There is no closed-chat or closed-Kick monitoring service.

Desktop mention notifications are off by default and require a separate, explicit Chrome notifications permission. Eligible new mentions from open chats are handled by the extension's background worker and delivered through Chrome and your operating system. A notification shows the channel and sender; chat text is omitted unless you enable its short preview. Previews can appear on the desktop or lock screen. Usernames, aliases, visibility/preview choices and a 5-300 second cooldown are local preferences included in backups. Up to 128 SHA-256 message fingerprints and 20 originating tab/document references are kept in Chrome session storage for at most 15 minutes to deduplicate and route clicks across worker restarts. They contain no chat text; they are excluded from backups and lost when the browser session ends. Clicking returns only to the still-open originating document and does not mark inbox entries as read. Turning alerts or toolkit enhancements off clears owned notifications and click targets; removing permission also turns the preference off. No mention is sent to the developer or an external notification service.

The separate received-replies view is off by default. Incoming reply tracking also runs for the default toolbar reply source without requiring that additional view to be enabled. It observes incoming reply events on Kick's existing chat connection in the chosen open channel chats, including multiview chat panels. A normal same-origin public channel lookup confirms each chatroom. It does not create another connection, read outgoing packets or extract authorization tokens. Up to 200 replies or 1 MiB of serialized reply data across open chats stay in page memory: sender, recipient, channel, native message references, time, reply text and Kick's original-message preview. These previews do not restore deleted history. Replies are searchable locally and shown in user cards; they do not enter Autoclipping, sounds or the saved chat sample. Clearing received replies or activity, disabling both the received-replies view and toolbar reply source or enhancements, or closing/reloading the page clears this page index. A short eligible toolbar notification already delivered to the shared inbox follows its separate local-history/Clear/200-entry rules. Only preferences and a manual configured identity enter backups.

UltimateKick reads channel names and URLs, Following suggestions, live status and rendered chat messages, including usernames, badges and emotes. Following suggestions, mixed chat and the full user-configurable message buffer (100-100,000 messages, default 500) for local chat search and per-user history stay in page memory. Refreshing or leaving the page clears this full buffer. Its numeric limit is saved as a preference. Following lists and chat text are excluded from backups. Size estimates refer to message data, not total browser memory. Searches and filters run locally and do not request older messages from Kick.

Received native message references are collected only when the default-off reference or chat-restoration option is enabled. The existing Kick chat connection supplies message UUIDs, numeric sender/chatroom IDs, username, native content, creation time and an optional thread UUID. Original-message snapshots in received replies may have no creation time; they are labelled accordingly. At most 1,000 references or 1 MiB of serialized reference records stay in page memory. The observer creates no connection, reads no credentials or outgoing packets, and assigns no native ID from text equality or virtual row positions. Clear activity, disabling both options or the toolkit, closing or refreshing clears this RAM index. No message is sent by collecting a reference.

Explicit linked-reply preparation uses a complete received reference selected by you. A cancellable preview stays beside the native draft for at most five minutes; public account-avatar identity, current channel/room, document/editor, filters and reference availability are revalidated, including the top-level account for same-origin frames. Only your trusted native Send click or Enter arms a six-second draft match. The adapter inspects that existing same-origin chat-send body and adds the original reference; it sends no additional request, reads no cookies/authorization headers or private application store, and does not automatically click Send or retry. The native client supplies request options/credentials and keeps its response/error handling. Current draft matching is transient RAM data, bounded to 4,000 characters; send bodies are limited to 32 KiB. Shortened, unknown or changed references/drafts/scopes are rejected, native already selected replies take precedence, and Cancel/Escape removes preparation without clearing your draft. Closing, expiry or owner/account changes releases the preview. A request sent is not proof of delivery; Kick decides whether a deleted/threaded original can be replied to. No new permission or developer recipient is added.

Chat restoration is off by default and available only in the installed extension. Enabling it saves a smaller local sample: channel, username, displayed/observation time, text and a local identifier, plus the validated native reference above when available. Retention is 1, 6 or 24 hours, with at most 200 messages per channel, 10 channels and 1 MiB for messages and up to 2,000 deletion IDs/10 clear fences. Native content is limited to 1,000 characters and marked if shortened; emote codes can remain in the reference, while display text uses their labels. Badges, profile images and credentials are not saved. Expired entries are removed on access. Saved messages return to labelled history beside the native feed, Activity/search and user cards; they never replay sounds, notifications, games or Autoclipping. Exact received UUIDs reconcile deletions; old plain-text entries cannot be matched individually. Deleted/cleared text is removed unless its retention option is enabled. Writes are batched, so final unsaved data can be lost on closing. Storage changes reconcile already restored text in other extension pages. A full pending deletion buffer or failed deletion write attempts to reset saved history rather than keep potentially stale text; storage failure remains visible and cannot guarantee a durable reset. Clear saved chat deletes the sample and saved context; turning restoration or toolkit enhancements off also deletes them. No archive enters preference backups, page-origin localStorage or preview migration.

The optional mentions inbox keeps up to 500 newly observed mentions in page memory, including text, username, channel and observation time. Username aliases and sound rules are preferences saved locally; inbox entries and read states are not saved. Optional chat analytics keeps a bounded local sample of up to 5,000 messages for at most 30 minutes, to show message totals, observed chatters, rates and contributors over 1, 5 or 15 minutes. Observed chatter activity compares selected-period authors with authors in the retained 30-minute sample under the same filters, showing baseline time and truncation. Optional saved summaries retain its numeric counts, seconds and cap flag within the existing context limit. Loaded and restored history is excluded. These counts describe received chat, not all connected viewers. Clear inbox, Reset analytics or Clear activity removes the corresponding page-memory data. Refreshing also clears it. Up to four pinned user cards and their positions last only for the current page. Gift display options hide recognized KICKs chat elements locally; Kick may still load the hidden images.

User cards and participant statistics use that local buffer. User cards also display avatars, banners, decorations, badges and Joined/Followed dates available in Kick's native user popup. Opening a card uses Kick's existing profile menu and displays its public visual assets from Kick's image hosts; these profile details stay in page memory and are not saved to extension storage or backups. Optional deleted-message retention keeps up to 200 log entries containing previously observed text. Optional phrase/repeat review keeps up to 200 flagged messages in page memory. Giveaways keep up to 5,000 entry usernames, native badge roles and winners in memory while the page is open; an explicit Export results action saves them to a local file. Moderation queues and their submission log also stay in page memory. These messages and participants are excluded from preference backups.

Selected channels, named sessions, layouts, panel positions, viewing preferences, filters, favorite channels, review phrases, timeout shortcuts, saved moderation reasons and private username notes are saved in local extension storage. If enabled, VOD URLs, playback positions and known durations for resume/progress badges and volume levels for up to 100 recent channels are also saved locally. VOD progress badges ignore positions older than 90 days. Live buffer-delay estimates are calculated from the native player's downloaded ranges and are not stored. UltimateKick does not use Chrome's history API or send this data to the developer.

A custom notification MP3 is read only after you choose it through the system file picker. Its basename and a copy of the audio, up to 2 MB, are kept in local extension storage so alerts can use it after the browser restarts. The extension does not save the original filesystem path, scan folders, sync or upload the file. Playback is local and limited to 10 seconds per alert. Remove custom sound deletes the stored copy and restores the default tone; uninstalling removes it with the other extension data. Custom audio is never stored in Kick's site storage.

Save screenshot creates a PNG of the selected video frame on your device. Export backup creates a local JSON file containing your sessions and preferences, including notes, optional VOD positions and notification sound/volume preferences; it excludes chat messages and custom MP3 files. These files are shared only if you choose to share them yourself.

Additional message buttons are off by default. If enabled, they act on a chosen message still displayed in its native chat. Copy writes message text or a username to the browser clipboard only when requested and allowed by the browser. Tag appends a mention to your existing draft without submitting it. Hide changes this page's personal message filter, and timestamp display affects the bound row. Control bindings and any shared expansion state last only in page memory and are released when the chat or controls are removed. Button, collapse and placement preferences are saved locally and included in preference backups; no message transcript or live expansion state is added to a backup by this feature.

Recording captures only the selected native video and writes an indexed local WebM or H.264/AAC MP4 file. Downloading a VOD or clip reads the current player's media playlists and segments, then saves a local video file. WebM/MP4 conversion uses packaged tools and browser codecs on your computer; MP4 preserves compatible tracks without re-encoding, and Original source retains the supplied media format. It requests access to the specific media hosts, makes normal requests without account cookies or referrers, and does not upload video or chat. Playback URLs, including temporary playback signatures supplied by Kick, stay in memory and are not saved as a download history. Repairing a saved WebM reads only the file you select and writes a local copy with seek metadata. Selected files and their paths are not uploaded, stored in extension storage or included in backups.

Optional quick replay downloads the selected 15-180 seconds only after a deliberate Save action. It does not run a second stream, background media polling or a capture buffer. For live channels, Save reads that channel's public Kick metadata and videos list using normal same-origin requests to find the matching active DVR recording. Its playlists and selected media range are then read through the restricted media reader without cookies or referrers. If the recording trails playback, the requested save can check small playlist updates for up to 45 seconds; idle playback does not trigger these requests. Resolution selection is independent of playback and no media entitlement is changed. Output is a local WebM or MP4 file; playback URLs and media stay in page memory and are excluded from storage/backups. Cancelling, disabling or changing the player aborts unfinished output. Only replay enable, length, file format and saved-resolution preferences are stored locally. Kick/CDN availability and supported codecs can limit saving.

Optional ad blocking uses packaged Chrome rules to block recognized ad requests originating from Kick, without collecting a request log. It reads public Kick channel playback metadata using normal same-origin requests and checks a temporary playback signature's ad opt-out flag before selecting an address for the identical stream. Recognized native Workers can receive a validated live address or original VOD asset before loading. A packaged local filter runs in the website Worker and loads only the exact original same-origin Kick player SDK, without rewriting its text or exposing extension APIs. It processes recognized HLS ad markers in bounded live/VOD playlist responses; media segments and SDK/WASM responses remain native. No second stream or ongoing media buffer is added. Signatures are never fabricated or edited. Original VOD playlist probes omit credentials and referrers. Source addresses, bounded status counters and redacted fallback reasons stay in page memory, and marked advertising ranges are processed locally. No playback metadata is sent to the developer.

Optional manual quality memory saves the Auto or resolution/frame-rate choice you deliberately select in Kick's player as your playback preference. It observes native mouse and keyboard selections, not automatic video-size or Multiroom policy changes. The enable preference and saved quality are kept locally and included in settings backups. No channel history, playback address or external request is added. Turning it off stops recording new choices; the saved preference stays until you change it or reset preferences. Multiroom optimization retains its independent rules.

Optional First observed labels track the first new message observed from a user in a channel during this page's monitoring session. Already loaded native history is seeded without a label. The newest annotation fingerprints take priority, with up to 3,000 entries within an estimated 1 MiB data budget in RAM, including a 256 KiB insert-only hashed identity filter. Removing an old annotation does not forget that its user already wrote. Filter collisions can suppress a new label but cannot relabel a returning user. Native labels bind to the original observed row through weak references. No account-history or profile request is made. Turning the option off, clearing Activity or closing/reloading the page clears this data; only the enable preference is saved locally and included in settings backups.

Playback speed controls change only the selected native video. Manual speed and catch-up status stay in page memory and are reset when its source changes or the tools are disabled. Optional adaptive catch-up reads the current video's downloaded buffer and playback state, never an estimate of broadcaster timing from a server. It respects manual speeds, stops acceleration during pause, seeking or buffering, and leaves long rewinds for deliberate viewing. Only catch-up enable, target/start distances, maximum speed and the optional wide-player shortcut preference are saved locally and included in settings backups. No media, viewing history or additional network request is created by these controls.

Games reads only newly received eligible answers from one selected open native chat. The game's channel, round settings, prompts, custom question or word packs, drawings, answer attempts, usernames, scores and timers stay in this page's memory. They are not saved to extension storage or included in backups. Preparing a new session resets its points; Clear activity, a preference reset, disabling toolkit enhancements or reloading clears the session. The audience board displays public round content and scores; host controls and unrevealed answers are separate. Copy prompt writes text to your clipboard only when requested. You post it yourself; Games does not send chat messages, open a second chat connection or contact a game server.

Playback recovery is off by default. When enabled, it observes the selected native player's playback state and supported error codes, gives Kick time to recover, then makes a bounded retry of that player. Retry this player is a separate explicit action. Binding identifiers, retry times and status stay in page memory and clear when the page closes; playback URLs, session tokens and credentials are not copied into diagnostic results, storage or backups. Native retry makes ordinary Kick/media-host playback requests through the existing player. This feature does not reload the whole workspace, load external executable code or send data to the developer.

Kick and sharing

The optional detached Giveaways window controls the same giveaway in its original, still-open Kick page. Entries, scores, winners and a last received copy stay in the source page/window's memory; unchanged polls send status metadata only. Chrome session storage holds at most eight opaque routing bindings: a random window token, the originating tab/document and popup window identifiers. These bindings contain no participants, chat text, channel names or results, are excluded from backups, survive worker suspension and are removed when their window closes or the browser session ends. A reloaded, closed or replaced source document cannot receive actions; the window shows disconnection and cannot collect new entries. Its last received results may still be viewed or exported until the window closes. Closing the detached window leaves the source giveaway running. Reviewed draws require a current, closed participant pool, and are never retried automatically or posted to chat. Creating this packaged window uses no new permission or external service.

After completing a Games session, you can manually review eligible participants and copy them into a separate, closed giveaway. The copied usernames, channel, game scores, eligibility/exclusion rules and ticket weights stay in page memory. Creating the pool does not draw a winner or send a chat message. Draw winner is a separate requested action; a manual JSON export includes entries, scores, winners and the source game. A new game can keep that giveaway independent, while Clear activity, disabling enhancements or closing/reloading clears a game-derived pool and any pending review. These scores and pools are excluded from extension storage and preference backups.

Confirmed-event moderation monitoring is off by default. When enabled, it observes known ban, timeout, timeout-removal, unban, message-deletion and chat-clear events arriving through Kick's existing native chat socket. The observed channel, time, public user identifiers, supplied moderator username, native message identifier, explicit AI deletion flag and reported timeout expiry remain in page memory. Up to 200 events and 200 timeout deadlines share a 1 MiB serialized-text budget; separate small identity and connection-state indexes are bounded too. Unknown actor or expiry information is shown as unavailable. Reaching the reported expiry does not prove that Kick removed a timeout. The feature neither reads outgoing socket packets nor submits commands or fetches private moderation history.

A separate, default-off option retains a short snapshot when a confirmed native event clears chat. It selects only previously buffered, newly received messages from that channel since its last observed clear, excluding restored messages and messages hidden by your current chat filters. Each snapshot contains at most 100 usernames, plain message texts and observation times, capped at 128 KiB and included in the shared event budget. Current chat filters also apply when a snapshot is displayed. Switching snapshot retention off removes ready and pending snapshots. Clear observed events, Clear activity, disabling monitoring or toolkit enhancements, and page close/reload remove the event record and snapshots. Monitoring preferences alone are saved in local extension storage and preference backups; event records, deadlines and snapshots are never saved, backed up or uploaded to the developer. No extra network socket or permission is requested.

Native players, chats and images make normal HTTPS requests to Kick and its website services using your existing browser session. Kick's privacy practices apply. UltimateKick does not read or copy passwords, authentication cookies or account API tokens. Messages you submit through native chat are handled by Kick; Mix is read-only.

The Clip shortcut opens Kick's native editor using the existing player and session. Kick handles preview requests and clip publication under its own privacy practices. UltimateKick keeps that editor visible above Multiroom. Using this shortcut does not enable clip automation or send a clip to the developer.

Optional Autoclipping analyzes newly observed messages only in chats you select after pressing Start. Analysis uses bounded rolling samples (at most 5,000 messages per channel), message counts, distinct usernames, literal reaction phrases and commands from explicitly named users. Loaded history is ignored. Up to 50 detected moments, their titles, time ranges, output results and published clip links stay in page memory until the page closes. Test mode only adds review cards. Up to 100 recent activity events and ignored-message counts stay in page memory. An optional local diagnostic export includes counts, rule targets and event types, excluding chat text, clip titles, folder names and credentials. Rule thresholds, per-channel profiles, exclusions, named command users, title templates and output preferences are saved in local extension storage and preference backups. Monitoring does not automatically resume on reload. No chat analysis is uploaded to the developer or a separate service.

You can configure each profile to review, save to disk, publish on Kick, or save and publish. Automatic local saving requires choosing a folder with the browser's folder picker and granting access to the selected media hosts. The folder handle stays in page memory, is not saved to extension storage or backups, and is released on page close. Media is read on demand for each moment using the existing DVR downloader and local conversion tools; no second continuous stream or media buffer runs. Manual review saves use the normal file picker. Files remain on your device until you delete them.

When you explicitly start a publishing profile, UltimateKick reads the channel's public live information using a normal same-origin request, then asks Kick's native clip creator to publish the selected duration and title on your signed-in account. Those titles and video clips become public on Kick. It does not submit chat messages, read login-cookie values or make its own private publication API requests. Native publication uses Kick's latest footage at creation time; late jobs are returned to review. Cancelling after dispatch cannot undo a clip Kick already created. Unconfirmed publication is marked uncertain and is not automatically repeated. Automatic cooldown/hour-limit claims (channel, moment identifier, coarse action time and owning extension tab/document) remain in Chrome session storage for up to one hour, surviving worker restarts but clearing with the browser/extension session. They contain no chat text, video URLs or account credentials, and are excluded from backups.

Clip discovery requests a chosen channel's public metadata and clips from Kick. Clip-list and supported thumbnail requests omit account credentials and referrers. Up to 500 sanitized public clip records and a small, one-minute channel-ID cache stay in Toolkit memory until it closes. Searches and date filters run locally; no result library, clip search history or playback signatures are saved or sent to the developer. Play and Download open the native clip page; saving a video remains a separate user action.

Optional sidebar previews read a hovered or focused channel's public Kick metadata using a normal same-origin request. Only its name, channel ID, live status, title, category, viewer count and supported thumbnail URLs are kept in a 30-channel memory cache, with a one-minute freshness period. Preview images make normal image requests without a referrer to Kick's channel-thumbnail service or supported image/CDN hosts; the browser's existing Kick session can apply. No following list, account credentials or playback signatures are stored by this feature. Disabling it or closing the page clears the cache.

With toolkit enhancements enabled, channel audience counters and Favorites read public channel metadata and Kick's native active-chatters endpoint using normal requests and the existing browser session. Sanitized channel identifiers, display names, categories, stream titles, avatar/thumbnail URLs, viewer and active-chatter totals and freshness/error fields are retained in page memory; returned chatter lists are discarded after parsing and are never added to the message buffer or saved. The native channel header refreshes once per minute. Stream-list/sidebar requests load only visible entries, with two concurrent requests, an 80-channel memory cache, a one-minute refresh period and rate-limit backoff. Collapsed Favorites do not request their own metadata. The selected favorite channels and collapse preference are saved locally, separately from their fetched display data. Hover cards share the list cache or pending lookup and request an uncached channel's active total only on hover/focus; closing the card cancels its independent lookup. Leaving a view, hiding the page, disabling enhancements or closing it cancels outstanding work. Unavailable totals are not estimated from local messages. No fetched audience/display records are uploaded to the developer, saved in extension storage or included in backups.

Clicking Share copies a link containing channel names and view settings to your clipboard. Anyone you give it to can see those details. It contains no messages, credentials, session names or custom panel positions.

Optional native moderation helpers are off by default. Unban Requests navigation and local context show existing user notes, up to ten filtered buffered messages and up to eight confirmed events from this page/channel; restored text is excluded. Selection/view changes clear this displayed local context. The shared public channel-metadata lookup also supplies a validated numeric channel ID when helpers are enabled. Bounded copies of responses to Kick's own native request-list/detail, ban-list and user-card reads supply request/user IDs, usernames, appeal and ban dates, moderator name, appeal text up to 2,000 characters, sanction type/expiry and ban reason up to 255 characters. These received records stay in each owned document's RAM for up to 60 seconds, 200 records and 128 KiB; inactive browser execution can delay expiry. They are never saved, backed up or sent to the developer. Disable, page hiding, account/channel changes and received authentication/permission failures clear the corresponding records. Removed or unavailable native controls disable review actions.

Reviewing an appeal prepares a separate explicit confirmation. Only that confirmation invokes the matching native Lift ban or Reject appeal control. A packaged page adapter validates the existing native request's selected ID, action and body, then reads a bounded copy of Kick's result; it makes no extra decision or history request, reads no authorization headers/cookies and starts no retry. Unknown results remain unverified. A native user card with fresh ban data can open a ban-reason review. It uses the existing reviewed native command flow, preserves permanent/temporary type, recalculates remaining timeout minutes and explains that reapplying can reset the ban date or round expiry upward. It never performs an unban/reban sequence. Only explicit Send submits this reviewed action; putting it in chat or copying it does not send. A successful response without a returned reason is labelled accepted, with a request to verify native details. Cancellation never claims to undo a request already sent to Kick. Only the enable preference enters settings backups; existing user notes keep their normal storage/delete controls.

A moderation command is submitted only after you prepare a queue and click Send next, or review a quick action and click its Send control. It uses the selected channel's native Kick composer and your existing account permissions. Kick receives and handles that command; the developer does not receive it. Message review does not submit commands automatically. Reply in native chat selects Kick's existing message reference and keeps your draft. It sends nothing; you submit a reply only using Kick's native Send control. Tag username only appends to a native draft; opening a mention card sends nothing. Emote previews display the selected existing image from its Kick/provider host. Link preview panels contact YouTube or Streamable only after you choose Load preview. These websites may receive your IP address and their existing browser cookies; their privacy practices apply.

Manual follower checks in Message review are off by default. Each Check follower click reads a matching native user card in the selected channel and displays a positive date, an explicit native no-follow observation or Unknown. A temporary adapter can read at most two matching responses to requests performed by Kick's own card, without an extra profile/follower request or authorization access. It processes only bounded profile bodies and validates the selected user/channel plus native card controls. A RAM-only minimum-time input compares a confirmed timestamp; calendar-date-only duration stays Unknown. At most two five-second checks run across a page, one per owned chat document. Dated observations stay in page memory, are valid for one minute and are cleared on expiry, row removal, scope/visibility changes, disable or Toolkit closure. Browser timer throttling can delay physical expiry until execution resumes. No relationship or result enters local storage, backups or a developer service; only the enable preference is saved. Missing or unsupported data never means not following. Checks do not change giveaway entry rules, review profiles or moderation commands.

Optional community services

7TV, BTTV and FFZ emotes and remote blocklist subscriptions are off by default. Enabling a service asks Chrome for access to its specific API/CDN or the HTTPS list host you select. These hosts receive normal requests, including your IP address. 7TV channel lookup also reads public Kick channel metadata and sends the viewed streamer's public channel ID to 7TV. No chat messages, notes, account details, local filters or session libraries are uploaded. Metadata and list requests omit credentials and referrers; community images use anonymous requests without a referrer. Each service's own privacy practices apply.

Provider emote metadata is cached in local extension storage for an hour. Subscription URLs, titles and last successful list snapshots stay locally until removed. Enabled lists refresh while Kick is open at your selected interval (daily by default), or when you click Refresh. Disabling a provider or list stops applying it and initiating requests; an already pending request may finish. Backups contain subscription configuration and emote preferences, excluding downloaded snapshots and emote caches; newly imported subscriptions start paused. External JSON and artwork are treated only as data, never executable extension code.

Optional creator dashboard tools

Moderation > Creator dashboard is off by default. Enabling it requests Chrome access only to dashboard.kick.com and adds Focus and Session stats to the top-level Stream dashboard. The packaged adapter checks the Stream route before reading its existing preview, chat container and five session values. It does not read stream keys, revenue, account settings, private application state or authentication details; it makes no extra statistics request or stream/moderation change. Focus preserves the same native player, chat and unsent draft. Missing values remain unavailable. Displayed metrics and Focus/panel state stay in page memory and are not uploaded, saved or included in backups.

The enable preference stays in local settings and preference backups. A session-only ledger keeps at most 64 tab/document ID pairs for precise cleanup after worker restart or grant removal, with no URLs, usernames, metrics, chat or account data. Closing a tracked tab removes its pair; disable, pause and removal clear active bindings after cleanup. Chrome session storage ends with the browser session. Disable dashboard tools restores native presentation while keeping the browser grant. Remove dashboard access also revokes that origin. Restoring preferences does not grant access or open the dashboard automatically.

Deletion

A user card's temporary native-message reveal changes appearance only. The target is kept in page memory while that card and its bound native chat remain open. Closing the card, changing the chat owner or disabling chat tools clears the view. Saved filters, transcript storage and automation input rules remain unchanged.

The optional theater navigation reveal changes only the appearance of Kick's existing desktop navigation. It makes no extra requests, copies no controls and leaves search drafts in place. Only its enable preference is saved locally and included in preference backups. Turning it off restores Kick's navigation behavior.

The optional stream context menu reads the selected rendered channel link and available category. Opening the menu makes no extra request. Choosing Open, new tab or new window visits the chosen public Kick channel; browser pop-up rules apply. Favorite and hide actions change your existing local preference lists. Only the enable preference and those lists are saved and included in preference backups.

Clickable mention color preferences change appearance only. Sender-color mode uses the message author's already rendered color without a profile lookup. The color mode and custom color stay in local preferences and backups; no new identity, message archive or request is added.

Backup > Restore default settings > Review reset lets you review and confirm a full preference reset. It restores Toolkit and viewing defaults, removes saved lists, notes, VOD positions, channel volumes, subscription snapshots, the imported notification MP3 and the saved chat sample. Open channels and named sessions are preserved. A preference backup excludes chat messages and MP3 files. Reset stops Autoclipping monitoring but cannot undo an already submitted Kick clip. Browser host grants, cooldown protection and files already exported to your device remain in place.

Delete named sessions in Sessions, remove list entries in settings, or save an empty note to delete it. Remove a subscription to delete its saved list snapshot; cached emote metadata remains until overwritten, extension data is cleared or the extension is uninstalled. Clear activity clears local chat search, the mentions inbox and local analytics in memory; it does not delete the separately saved chat sample. Use Chat > Restore chat after refresh > Clear saved chat to delete that sample. Turning restoration or toolkit enhancements off deletes saved chat; its retention preference remains. Closing the Kick page clears in-memory messages, inbox entries, analytics and pins. Closing multiview clears its Mix buffer. Other saved extension data remains until changed, cleared or removed by uninstalling; turning off a feature does not delete its saved preferences. Optional host grants can be revoked in Chrome's extension settings. Exported files remain wherever you saved them.

The optional development preview uses Kick's local site storage. The installed extension imports that preview's settings and sessions without overwriting existing extension data. Uninstalling does not remove the original preview data; clear it separately in your browser's Kick site-data controls if needed.

Clear log removes the local moderation log; disabling deleted-message retention removes those retained entries. Clear review or disabling message review removes its flagged-message queue. Closing the Kick page removes participant statistics, flagged messages, giveaway entries, hidden-message selections and the command queue. Exported giveaway results and video files remain on your device until you delete them.

Chrome toolbar audio

The toolbar menu can list streams in other open Kick tabs using existing Kick site access. Channel names and player volume/mute state stay locally in memory, with a two-second discovery cache. Selecting a channel name switches to that existing tab and stream. The current single-player card combines its channel/status with the tab-volume controller; other cards use wide whole-tab sliders and editable percentages. Multiroom retains separate native stream controls. Whole-tab mute controls an already enabled UltimateKick gain session when present, otherwise Chrome's tab mute. Discovery alone starts no capture. The first volume adjustment can start a chosen tab's audio only with its existing Chrome toolbar-invocation grant, without a separate Enable step for another tab.

Toolbar cards can show the favicon address supplied by Chrome and public channel avatars already observed on open Kick pages. Each Multiroom tab is grouped into one entry with separate stream controls. Available icons load from their existing service without a referrer; the service may receive the image request and your IP under its normal practices. Missing images use a packaged or generic icon. No third-party favicon lookup, browsing-history read or additional permission is used. Icon addresses and group expansion stay in memory and are not saved or backed up.

Show browser tabs separately requests the optional tabs permission. It displays other HTTP/HTTPS tabs producing audio or muted by UltimateKick, including its zero-gain sessions, excluding tab IDs already shown under Other Kick tabs. IDs, titles, URLs, audible/mute state and owned gain/output status are read for switching and whole-tab audio controls. Up to 128 matching rows and a two-second discovery cache stay in memory; titles/raw URLs are not saved or backed up. Owned sessions supply a scalar output peak and 48 grouped amplitude values during menu refresh, displayed as a translucent white waveform behind the controls. Uncaptured cards indicate only recent audio activity. Status reads start no capture and create no audio file or saved measurement/waveform history. No unrelated page content, browser history, cookies or credentials are read, and no content script is injected into other websites. A bounded session ledger holds up to 256 tab IDs, opaque navigation nonces and SHA-256 URL digests for stale-action checks, without raw URLs, titles, content or audio. Tab closure removes its binding; browser-session end clears the ledger. Remove tab list access revokes the optional permission and clears the view. A granted list alone starts no capture. Remote gain changes use a matching owned session; the first slider/percentage change can start a selected target only with its existing toolbar-invocation grant. Otherwise Open tab directs the user to invoke UltimateKick there. Chrome tab mute requires no capture.

Tab volume is off until you adjust its slider/percentage, press Enter in its percentage field or choose Reset. The tabCapture and offscreen permissions are declared at installation so they are ready when you invoke the toolbar; opening the menu alone starts no audio processing. Chrome still requires that target tab's toolbar invocation. On Chrome 116+ the explicitly selected normal HTTP/HTTPS tab's audio is routed to the speakers through a local 0-600% gain/peak-limiting graph. Chrome internal and other restricted pages cannot be captured. No microphone, screen video or device audio is requested, and audio is not recorded, saved or uploaded. Volume and mute stay in an offscreen document's memory while the popup is closed or the worker sleeps. Current peak and waveform summaries come from the existing analyser after gain/limiting and remain in RAM, with no saved history or extra sampling timer. Up to eight owned sessions are supported. Stop, navigation/reload, tab closure, ended capture or disabling the extension releases streams; the last session closes the document. Individual native Multiroom stream controls remain separate from the whole-tab multiplier and its combined output waveform.

UltimateKick Studio

The toolbar's separate Studio tab shows local activity history, without desktop alerts, unread counts or toolbar badges. Extension-local storage retains up to 100 completed, ready, requested, failed or cancelled operations and queued clip handoffs: event type/status, time, source/file and project display names, output format/frame rate, byte size and caption count when available. It does not retain media bytes, full file paths, source URLs, credentials, transcript text or detailed error messages. A browser download handoff is recorded as Download requested, not proof that a file finished downloading. Clear history removes these entries without deleting projects, templates, models or downloaded files. They also disappear on extension-data clearing, uninstall or replacement by newer entries. History is separate from notification preferences and is excluded from settings backups, .ukstudio and .uktemplate files; it is not synced or uploaded.

Studio edits selected videos locally in a dedicated extension tab. Imported video bytes and temporary MP4 work files use the origin-private file system (OPFS); project metadata, source names/channel labels, crops, cuts, original-audio settings and text layers use IndexedDB. Completed imports retain their own media copy independently of the original Kick tab or an expiring URL. This data stays in this extension profile until you delete projects, use Clear Studio projects & media, clear browser storage, uninstall, or the browser removes local storage. Studio shows storage estimates/quota errors and never evicts another saved project automatically. Incomplete imports and disposable exports are cleaned up. Downloaded MP4 copies are separate files under your control.

Local files are read after selection/drop. Link and channel imports use the existing public Kick site-data adapter, with optional web.kick.com access requested from Studio. Metadata requests omit cookies, credentials and authorization tokens; no registered Kick API app is used. Selected playback bytes use bounded media readers and permissions for their origins. Thumbnail addresses are never used to guess media URLs. Catalog metadata/thumbnails stay in memory. External servers receive normal requests for selected public metadata, thumbnails and media, without a referrer. Native clip/autoclip handoffs keep at most 20 source descriptors, titles/channel labels and temporary media URLs in browser session storage with a 30-minute deadline and cleanup at the next available worker wake; dismissing/completing an import removes its handoff.

Named channel/format templates contain layouts, linked audio settings, backgrounds and your text content/style with relative timing in local settings. Preference backups include these templates; Reset all preferences clears them while keeping Studio projects/media. Projects, videos and export work files are excluded from those backups and sync. Text added to video appears in the local project and output. Export uses packaged code/font and local H.264/AAC encoding, including a packaged AAC WebAssembly fallback; processing buffers stay in memory. No video, project, text or audio is uploaded to the developer or a publishing service. Studio has no X/social account connection or automatic posting.

Studio V2 also stores imported audio, images, custom fonts, subtitle/word timing, effects and motion settings locally. User-selected microphone capture starts only after Record from playhead and browser permission, with monitoring off; commentary is written as a local WAV and added to the project. Capture stops when finished or the tab closes/hides. Thumbnails and waveform peaks are disposable local cache. Referenced template media is retained separately from project media; settings backups contain template metadata only, without the referenced files.

Optional automatic captions download a pinned, integrity-checked multilingual speech model from Hugging Face and its known model-delivery hosts after an explicit action and host grant. Those hosts receive normal download requests, including the IP address, without account credentials or audio/video uploads. The model is stored separately in this browser and can be removed through Remove downloaded model. Transcription uses packaged local code and the downloaded model data; after download it can run offline. Project/media deletion keeps the downloaded model and saved templates. No external transcription API, developer inference service or telemetry is used.

Save project creates an uncompressed .ukstudio file containing the current edit and all imported video, audio, images, custom fonts and caption text/timing, including source names/channel labels. The file is not encrypted and is saved to the destination you choose or your browser downloads; it is under your control separately from browser autosave. The extension keeps no persistent access to the selected external file. Load project reads only the selected/dropped file, verifies its metadata/media integrity and copies it as a new local project without replacing existing projects. Failed or cancelled copies are removed. Channel-template preferences, downloaded speech models, Undo history and disposable caches are excluded from project files. No project file is uploaded and no account or new host permission is requested.

Full montage templates are separate from older clip-template preferences. Their source-slot/scene definitions, both layouts, text/caption configuration, audio preparation and export settings are saved in Studio IndexedDB, with independent copies of included media/fonts in OPFS. Export template writes an unencrypted .uktemplate file containing those settings and fixed media, including their names/channel labels and any fixed caption text. Replaceable footage, model weights and work files are excluded. Import template verifies the selected file and saves a new local template without overwriting existing projects/templates. Preference backups and Reset all preferences do not include or erase full montage templates; delete them explicitly in Studio. Clearing Studio projects keeps saved templates and downloaded models.

Loudness measurement, music ducking, quiet-gap detection and caption review run locally. Projects retain preparation results, processing provenance, reviewed ranges and retry status; source edits can invalidate derived results. Cancel/retry preserves completed results and does not upload speech or media. Quiet-gap cuts require user approval. Named-range MP4 exports and cover PNGs use the local compositor and chosen download destination. Safe-area guides are excluded from outputs. No new account, host permission, remote executable code or publishing connection is introduced by these tools.

Studio retains panel/monitor preferences and zoom/scroll positions for up to 20 recent project IDs in local extension settings. Reset workspace layout clears this view state without changing projects or templates. Media synchronization, manual groups and clip attachments are local montage metadata included in project/template files. Migration retains one prior metadata copy per local project/template; deleting its owner removes that backup. No extra recording, network request, telemetry or permission is introduced by timeline selection and workspace controls.

Firefox desktop edition

The shared Studio activity history also applies to Firefox: up to 100 local operation summaries in the toolbar's Studio tab, with Clear history and no desktop alert, unread badge or browser-download completion claim. It requires no additional Firefox permission and remains separate from the Notifications inbox, project/template files and preference backups.

The Firefox edition requires Firefox 140 or newer and uses the stable add-on ID [email protected]. Private browsing is disabled. Its built-in data-consent declaration lists browsing activity, website content and personal communications: selected channel/page context loads Kick players and optional public services; native replies, reviewed chat/moderation drafts and explicitly enabled native clip outputs can send their selected content or received references to Kick. The developer operates no telemetry, account or collection server and receives none of this data. Existing feature controls, optional service grants, local retention and deletion rules still apply.

Firefox toolbar controls read the current page and supported open Kick streams. Optional Show browser tabs requests the tabs permission to list other HTTP/HTTPS tabs producing audio or muted by UltimateKick, deduplicated with Kick cards. Up to 128 matching rows, raw titles/URLs, existing browser-provided favicon addresses and a short discovery cache remain in memory. Icons reuse browser-provided addresses or already observed channel avatars without a favicon lookup service; image requests go to the existing service without a referrer. No browsing history, cookies, credentials or unrelated page text is read.

Adjusting a slider, exact percentage or Reset starts local 0-600% Web Audio processing for supported HTML video/audio elements. Access to another site is requested for that selected origin, directly from your toolbar interaction. The isolated audio script reads media elements and source eligibility, observes added media elements and routes eligible same-origin, blob or CORS-enabled media through gain, peak limiting and an analyser. It does not alter native player volume/mute, download media, capture a microphone/screen or record, save or upload audio. Existing native Multiroom stream controls remain independent. Protected/internal pages, sources without suitable CORS access, other audio processors and audio generated without accessible HTML media elements are outside this mechanism. Newly embedded non-Kick documents require appropriate site access and another volume adjustment.

A session ledger keeps at most eight active tab identities, URL hashes, opaque frame tokens, gain and mute state in extension session storage, separate from preference backups. A separate stale-action ledger is bounded to 256 tab/navigation bindings. Neither stores raw URLs, titles, audio, waveform samples or unrelated page content. Live graphs remain in their content documents when the toolbar closes or the event background sleeps. Current output peaks and 48 grouped waveform values are computed locally when status is requested and stay in memory without saved history. The toolbar paints those values as a translucent white waveform; before processing, its indicator only reflects recent browser audio activity.

Mute changes the owned gain session or Firefox's native tab mute when no gain session exists. Stop restores 100% gain and bypasses peak limiting. Web Audio cannot unbind a MediaElementAudioSourceNode, so its unity route remains connected until the document is disposed; disconnecting it would silence its player. Navigation/reload, tab closure and browser-session end clear the session identity. If you disable/uninstall the add-on, revoke site access or switch to another volume extension, reload affected media pages to dispose their retained route. Firefox autoplay policy can require a real interaction with the player before a suspended graph resumes. No Chrome tabCapture or offscreen API is used by this edition.

Limited use

UltimateKick follows the Chrome Web Store User Data Policy, including the Limited Use requirements. Data is used only for the personal Kick viewing workspace and its tools. It is not sold or used for advertising, profiling, credit or lending decisions. The developer cannot access your local data.

Contact and changes

Contact thesomeguy at [email protected]. Information you voluntarily send in a support request is used to answer it. Changes to this policy will carry a new effective date.