Privacy Policy — Kick Stream Helper

Last updated: 2026-05-24

This policy describes how the Kick Stream Helper Chrome extension handles user data.

What this extension does (brief)

Kick Stream Helper is a single-purpose Chrome extension that routes only kick.com network requests through an external SOCKS5/HTTPS proxy so that the Kick streaming site remains reachable in regions where direct access is degraded.

The proxy is activated only when both of the following are true:

• The user has explicitly opted in via the onboarding screen on first install.
• The active browser tab is currently on kick.com.

In every other situation, the extension stays idle and does not influence any network request.

What data we collect

We do not collect, log, or transmit any user data to servers operated by the extension developer.

The extension stores only a small set of local preferences required for it to function:

• Enable/disable state.
• PAC mode selection (lite or full).
• Coexistence flag (whether another proxy extension was detected on the most recent check).
• A cached copy of the remote feature-flag configuration document.

All of these values are kept inside chrome.storage.local. They never leave the user's browser and are not synchronized to any remote backend.

Third-party proxy provider

Network traffic destined for kick.com is forwarded through an external SOCKS5 proxy provider while the extension is active. That upstream provider may retain connection metadata such as connection timestamps and source IP addresses in accordance with its own privacy policy.

The developer of this extension has no control over the data-handling practices of the upstream proxy provider. The identity of the upstream provider may change over time without notice, so users should not assume a specific operator behind the proxy endpoint.

Remote configuration fetch

Approximately once per hour, the extension issues an HTTPS GET request to:

https://kick-stream-helper.pages.dev/api/config.json

This file contains only feature-flag values consumed by the extension, such as a global kill switch, a host allowlist, a minimum supported extension version, and other schema-whitelisted fields. No telemetry, identifiers, or user-generated content is transmitted in this request.

The request carries only the standard information that any HTTP client sends: the browser's default User-Agent string and the user's public IP address as visible to the network. The request is processed and logged according to Cloudflare's standard logging policy for static asset serving; no additional tracking is performed by the extension or its developer.

Cloudflare's privacy policy is available at: https://www.cloudflare.com/privacypolicy/

No tracking technologies

The extension does not set or read any cookies, does not embed analytics scripts, does not load tracking pixels, and does not include any third-party trackers.

Permissions used

The extension requests the following Chrome permissions:

• proxy — to apply a PAC script that selects an upstream proxy for kick.com hosts.
• storage — to persist local preferences inside chrome.storage.local.
• webRequest — to observe authentication challenges from the upstream proxy so they can be answered automatically.
• webRequestAuthProvider — to supply proxy credentials in response to those challenges without showing a browser-level credential prompt.
• alarms — to schedule the hourly remote configuration refresh described above.

Host permissions are narrowly scoped to kick.com and four content-delivery hostnames required for media playback. The extension does not request <all_urls>.

Coexistence with other proxy extensions

If another proxy extension is detected as the active controller of Chrome's proxy settings, this extension defers and does not apply its own PAC script. In that case the user sees an in-extension banner explaining the conflict.

Detection relies solely on the standard chrome.proxy.settings.get levelOfControl value exposed by Chrome. The extension does not enumerate, fingerprint, or otherwise probe other installed extensions.

Changes to this policy

If this policy changes, the «Last updated» date at the top of the document will be revised. Users are encouraged to review this page periodically.

Contact

Questions or concerns about this policy can be sent to:

support@kick-stream-helper.pages.dev

Compliance certification

The developer of Kick Stream Helper certifies the following with respect to user data:

• We do not sell or transfer user data to third parties outside the approved use cases of providing the single advertised functionality of the extension.
• We do not use or transfer user data for purposes unrelated to the extension's single purpose.
• We do not use or transfer user data to determine creditworthiness or for lending purposes.