Privacy & permissions
Understand what stays locally, what disappears with the page and which optional features contact another service.
Two kinds of local data
| Lifetime | Examples |
|---|---|
| Saved in this installation | Preferences, sessions, lists, private notes, optional custom sound and supported volume/VOD progress. |
| Current page memory | Most chat activity, mention inbox/read state, analytics, game scores, giveaway pools and Autoclipping queue. |
| Local notifications and session routing | The latest 200 short read/unread notifications and bounded deduplication keys stay in local storage through browser restarts until cleared, disabled or evicted. Exact source references, detected identity, audio bindings, output limits and detached-window identities are session-only. These records are excluded from preference backups. |
Refreshing the owning Kick page clears or stops live activity. Backups include supported saved configuration, not live samples or media. A file you export remains on your disk until you manage it.
Optional saved chat is different
Save recent chat locally for restoration starts off. It keeps up to 200 messages per channel within ten channels and 1 MiB for 1, 6 or 24 hours. A labelled history pane beside native chat, Activity and user history share that sample. Received identities/deletion fences can accompany supported records; text without an identity stays an unlinked quote. Restored messages never drive live tools.
Inspect with Check saved chat
Read the saved counts and storage usage.
Clear saved chat
Remove the stored sample. If saving stays enabled, new messages can be collected afterward.
Turn it off
Disabling restoration or enhancements deletes saved chat. Clear activity is the separate RAM-only action.
Choose external access deliberately
| Feature | Access or connection |
|---|---|
| Community emotes | Chosen provider API/image hosts; 7TV can receive a public Kick channel ID. |
| Blocklist subscription | Only its selected public HTTPS origin. |
| Media download | The relevant supported video source host. |
| Desktop alerts | Optional Chrome notifications permission; short chat previews are separately opt-in. |
| Embedded link preview | The linked service after Load preview. |
Ordinary network requests expose your IP address to their destination. The developer has no account backend collecting your chat, notes or session library. This documentation site has no analytics or third-party search service.
Files and folders
Manual saves use browser file choices. Autoclipping's folder handle lasts for the current page session. Recorded/downloaded media, custom game packs and exported giveaway files are not uploaded to a developer service. Custom MP3 selection saves a local copy, not unrestricted access to its original folder.
Clear data and read the full policy
Use feature-specific clear controls for saved chat, activity, notes or channel levels. Backup's reviewed reset describes its wider scope. Browser permission grants are controlled separately in Chrome. The full Privacy page documents retention, optional hosts and the contact address.
Read the full privacy policyDoes importing settings grant access to every optional host?
No. Browser grants remain separate; newly imported subscriptions start paused.
Can my OS show a message preview on a lock screen?
Yes, if you enable the desktop preview. It is off by default.
Are exported files deleted when I reset preferences?
No. Manage files you saved on disk through your normal file tools.
Optional data and access at a glance
| Feature | Data handling |
|---|---|
| Tab boost | Capture/offscreen access is declared at installation. Only a volume/Reset action starts processing with the target tab's toolbar-invocation grant. Audio stays in the local speaker graph without recording/upload. |
| Other Kick tabs | Bounded RAM discovery and explicit existing-tab switching; no browsing-history database. |
| Public user-card details | Manual credential-free Kick read; short RAM cache and no saved relationship. |
| Playable sidebar preview | Optional official player.kick.com embed and its normal website dependencies after activation; no saved media. |
| HTTPS moderation list | Explicit selected-origin read without cookies/referrer; URL/IP reaches that host. No persisted response. |
| Creator dashboard | Optional dashboard.kick.com origin grant and a /stream-only adapter; no keys/revenue/account editing. |
| Manual follow date / appeal context | Native current-page observations only; transient results and no stored appeal text. |
| Saved chat context | Separate default-off bounded local inbox/metadata/summary store; never replays live automation. |
Toolbar access and local records
| Feature | Data handling |
|---|---|
| Browser tabs | Optional list access shows a bounded RAM view of playing or UltimateKick-muted web tabs, deduplicated with Kick cards. Site icons come from Chrome-provided addresses; image requests go to that service without a referrer or favicon lookup provider. No page content/history is read. Raw titles/URLs/icons and waveform history are not saved; navigation references/URL digests are session-only. |
| Shared notification inbox | Up to 200 short read/unread records, times/occurrences, available public avatar addresses and 1000 deduplication keys/fingerprints survive browser restarts locally, outside backups. Source routing stays session-only. Clear, source/enhancements-off, applicable identity changes and eviction remove records; there is no 24-hour expiry. |
| Notification clicks | Click a row to mark read and focus/open its channel; the check only marks read. No settings window opens. Read state survives repeated supported delivery; missing/coarse clocks can limit refresh matching. |
| New alerts | New chat/live observations still require supported open Kick sources, including background tabs. Collected notifications remain readable elsewhere after those sources close. |
Received native data and display preferences
| Feature | Data handling |
|---|---|
| Received message references | Default-off capture of bounded message/sender/room identities from existing supported native chat events. RAM references can prepare an explicit linked reply; optional restoration retains bounded identities and deletion/clear fences locally. Message text/reference data is outside backups. |
| Follower and moderation review | Fresh selected native-card/appeal responses provide short-lived identity, relationship, reason and decision status. Minimum follow time stays in the current review in RAM. No credentials or private editor state are read; no automatic eligibility, sanction, decision or retry is performed. |
| Show advanced options | A boolean display preference in the existing local settings and backup path. It hides duplicate sections without clearing their preferences, jobs or optional feature data. |
Firefox consent and audio access
Firefox 140+ has built-in required consent for browsing activity, website content and personal communications, covering selected Kick/service context and native communication outputs. The developer receives none of that data and has no collection server. Existing feature switches and specific optional host grants still apply. Private browsing is disabled for this edition.
Another site requests access only when you adjust its audio. The isolated script reads media eligibility and keeps gain/session/frame identities plus URL hashes in session storage. Samples and waveform peaks remain in memory; there is no microphone capture, audio recording, saved waveform history or upload. Stop restores 100%. The Privacy policy describes retained source routing and reload after disabling or revoking access.
Written for version 1.1. Some controls may be unavailable in an earlier installed release. See release notes.