Skip to content
StreamJuiceDesktop
About Progress Get involved
Beta testing
LEGAL / 01

Privacy policy.

Clear answers about the information this website collects, how StreamJuice Desktop and KCW Labs services use information, and the choices you have.

Effective November 10, 2026 • StreamJuice, a KCW Labs project
ON THIS PAGEWho we areWebsite informationCookies and preferencesDesktop applicationYouTube and Google dataTwitch dataTikTok & TikFinityKickKCW Labs connection servicesSharing and securityRetention and requestsYour rightsContact
StreamJuice Desktop beta

Website form submissions are saved privately and also sent as restricted-access notifications to Discord. Selected beta testers use Discord for ongoing testing communication. Local giveaway data remains governed by the separate desktop sections below.

1. Who operates StreamJuice

StreamJuice is a project of KCW Labs (referred to as “StreamJuice,” “KCW Labs,” “we,” “our,” or “us”). This policy applies to the StreamJuice pages at kcwlabs.xyz/streamjuice, the beta and suggestion forms on those pages, StreamJuice Desktop builds made available to you, and the KCW Labs connection services used by those builds.

For privacy questions, deletion requests, and account-related inquiries, contact support@kcwlabs.xyz.

2. Information collected on this website

Feature suggestions

When you submit a suggestion, we receive the idea type, title, and message you provide, plus your name and email if you choose to include them. We use these details to review ideas, improve the product, and reply when appropriate. You do not need a Discord account to submit a suggestion.

Beta applications

When you apply, we collect your name, preferred initial contact method, the email address or Discord username that matches your choice, streaming platform, operating system, and any optional channel and setup details. We use this information to review applications, send invitations, coordinate testing, and collect feedback. You can apply by email even if you do not currently have a Discord account. If selected, you must have or create a Discord account and use the designated KCW Labs Discord testing space for ongoing participation.

Private Discord notifications for both forms

After either form is submitted, KCW Labs keeps the submission in private server-side files and also sends the submitted details through a server-side webhook to a restricted-access channel in our KCW Labs Discord server for internal notifications and review. The Discord copy can include the form type, submission timestamp, name and contact information if provided, and the information entered into the form, such as suggestions, platform and operating-system choices, and setup details. We do not post these submissions in public channels or in channels intended for the beta tester community. Only people with the relevant server or channel permissions can view them; Discord itself also processes content delivered to its service under the Discord Privacy Policy.

Communication during beta testing

If you become a tester, invitations may first be sent by your chosen contact method, but beta communication takes place through Discord. Your Discord username, messages, testing reports, attached files, and communications may be accessible to KCW Labs and, when you post in shared tester channels, other members who have permission to view those channels. Avoid sending passwords, account tokens, private viewer information, or other sensitive details through the forms or testing channels.

Technical website information

Our hosting provider may process ordinary technical connection records, such as IP addresses, request timestamps, and browser information, for site delivery, diagnostics, and security. KCW Labs services use rate-limit records to prevent abuse.

We do not sell beta application or suggestion details. We do not add beta applicants to unrelated marketing lists solely because they submitted a beta form.

3. Cookies and similar storage

This StreamJuice site has its own consent controls, separate from the main KCW Labs home page. You can accept optional technology, reject it, or change your selection at any time using in the footer.

CategoryPurposeChoice
EssentialSession and form-security functions, with local browser storage to remember your consent selection.Always active
AnalyticsGoogle Analytics may measure visits and page use if you opt in. It is not loaded without your consent.Optional, off by default
Embedded mediaPermission for potential future third-party embedded videos, which may set their own cookies when played or loaded.Optional, off by default

After you accept analytics, Google Analytics 4 starts measuring the page you are viewing. Google may process page views, referring sites, browser and device characteristics, cookie identifiers, and general interactions for website usage reports. This integration keeps advertising consent off. StreamJuice does not send beta or suggestion form contents, activation keys, or in-app giveaway activity to Google Analytics. Read how Google uses information from sites that use its services.

You can use the site and submit forms with essential storage only. Your choices are remembered in your browser. Turn Analytics off in Cookie preferences to stop further website analytics collection. Browser controls can remove cookies already present. The current walkthrough is hosted on this site. The embedded-media setting applies to future videos from external providers.

4. Desktop application data

The giveaway engine operates on the streamer's computer. Depending on the connected platform and enabled features, it processes viewer names, platform user or channel IDs, profile-image links, relevant commands, optional entry notes, and subscription, gift, share, or redemption information. These fields support entry rules, bonuses, repeat-command checks, alerts, winner selection, and claims.

Session entrants and recent activity

Automatic chat entrants and recent entry activity are held for the current app session and clear on normal closing and startup. Recent activity also expires after 24 hours while the app is running. Entries identified as manually added are saved locally between launches. During migration from older builds, entries whose source is ambiguous are cleared.

Winner confirmation and local History/Analytics

New winner details and claim text initially remain in memory. After the winner overlay closes, a confirmation form can show the winner name and claim message for review. Clicking Save to Analytics writes the reviewed details to local History/Analytics. With the global Skip Log Modal setting enabled, winners remain in Recent Winners for optional logging during that session.

Each saved win has one record and can be updated using Edit Log. A claim received after an earlier save remains in memory until a further explicit log update. Saved records may include the giveaway title and key, source platform, winner identifier and name, entry count, spin and claim times, claim status, the confirmed claim message, and any fulfillment note you enter. History/Analytics keeps the latest 100 records you choose to save. A saved record remains until you delete it or a newer save exceeds that limit and replaces the oldest record. Saved logs remain available through account disconnection and expiry of temporary session caches.

Settings, displays, and diagnostics

The app saves giveaway designs and settings, dashboard layout, window preferences, manually added names, linked reward configuration, blocked-user settings, alert preferences, and uploaded media locally. Settings and saved History/Analytics are ordinary local files. OAuth tokens use operating-system credential encryption. Export and recovery files have the separate encryption described below.

The streamer controls what appears in the wheel, alerts, outgoing messages, and OBS overlays. Those choices can make names, profile images, entry notes, or winner details visible to their audience. Selected images, fonts, styles, and other remote resources can load from platform hosts or content providers, which receive the connection information needed to deliver them, including the device's IP address.

Local diagnostics record technical events, timestamps, software and operating-system versions, connection status, timing, and selected error codes. The diagnostic writer limits recorded fields to exclude account names and IDs, chat contents, tokens, and request bodies. It keeps a current file and up to 14 dated archives, rotating when new logging occurs. Use Help → Open Logs Folder to find logs. KCW Labs receives them when you choose to send them for support.

5. YouTube API Services and Google data

StreamJuice Desktop uses YouTube API Services. Google OAuth grants the connected channel's permissions for discovering live broadcasts, reading live chat, recognizing giveaway commands, and posting enabled announcements and responses. Google's consent screen can describe broader YouTube actions covered by the requested permission than the specific features implemented in StreamJuice.

Information used for these functions can include channel names and IDs, broadcast and chat IDs, relevant chat text, viewer channel IDs, display names, profile-image links, entry notes, and claim messages. The desktop processes these fields for its authorized giveaway functions and selected displays.

Authorization and where information goes

Authorization codes and refresh tokens pass through the KCW Labs YouTube authorization service. It adds the application's server-held client credential, contacts Google, and returns the token response to the desktop. That exchange processes access and refresh tokens on the server. The relay handles those token values transiently and writes rate-limit counters separately. Desktop authorization tokens are stored with operating-system credential encryption. Routine YouTube broadcast and chat requests run directly between the desktop and Google.

Our use of Google user data is limited to providing and supporting the YouTube functions you authorize. Use and transfers of that data are governed by the Google API Services User Data Policy, including its Limited Use requirements where applicable. StreamJuice's local History/Analytics describes its own giveaway activity.

Access and deletion

Disconnect YouTube in the app to stop the connection, attempt token revocation, and initiate removal of associated local session caches. Saved History/Analytics remains under the separate controls in section 11. You can also revoke access through Google Account third-party connections. When the app detects authorization that cannot be refreshed, it initiates associated cleanup and asks for reconnection. Local file expiry and exported copies have the handling described in section 11.

Review the Google Privacy Policy. By using the YouTube integration, you also agree to be bound by the YouTube Terms of Service. Use is subject to the YouTube API Services Terms.

6. Twitch

Twitch provides authorized chat commands and configured events, including subscriptions, cheers, and Channel Point redemptions. StreamJuice uses relevant names, IDs, profile images, eligibility information, and event details for entry rules, bonuses, linked rewards, alerts, claims, and enabled messages.

The current connection runs from the desktop to Twitch. Authorization tokens are protected in the device's local credential store. Disconnecting Twitch attempts provider-side revocation and clears associated local session data and linked reward configuration. Saved History/Analytics remains under the separate controls in section 11. Manage provider access through Twitch Connections. Twitch's processing is described in its Privacy Notice.

7. TikTok LIVE through TikFinity

TikFinity is independently provided third-party software. KCW Labs and StreamJuice are not affiliated with TikFinity, and TikFinity is distributed separately from StreamJuice. Register for, download, and install it yourself through the TikFinity website. TikFinity runs on the same computer and supplies configured TikTok LIVE events through a local connection. StreamJuice processes relevant names, user IDs, profile-image links, chat commands, subscriptions, shares, and gift information for giveaway rules, bonuses, alerts, and claims. Gift and share progress can accumulate in session memory for configured bonuses.

Enabled outgoing TikTok messages are handed to the configured TikFinity connection. TikFinity and TikTok handle their own account sign-in, authorizations, and data practices. Disconnecting TikTok in StreamJuice clears its associated local session data and stops that local TikFinity connection. Saved History/Analytics remains under the separate controls in section 11. Manage separate TikFinity or TikTok account access through those services.

8. Kick

The Kick integration processes usernames, user IDs, profile-image links, chat commands, subscriptions, gift events, and accepted Channel Point redemptions for enabled rules, bonuses, rewards, alerts, and messages. Kick sends subscribed webhook events to the KCW Labs relay before the desktop retrieves relevant events.

The relay verifies deliveries and queues supported events. For chat deliveries, it queues command-like messages beginning with an exclamation mark and a valid sender ID. Supported subscription, gift, and accepted-redemption payloads can contain participant details needed to interpret the event. The desktop also makes authorized requests to Kick. When importing a valid entrant backup, a currently linked Kick service is used to fetch fresh profile fields for its stored IDs. An entry being older than 24 hours in the backup does not by itself exclude it from that check. A successful lookup rebuilds the imported profile fields, including after reconnecting Kick. Profiles that cannot be resolved are skipped.

Kick authorization codes and tokens are processed by the KCW Labs connection service during sign-in and refresh. Desktop tokens use operating-system credential encryption. The relay stores hashes of issued access tokens, expiry information, and broadcaster associations for delivery access. Its event retention is described in section 9.

Disconnecting Kick attempts token revocation and removal of configured event subscriptions, and clears associated local session caches and linked reward configuration. Saved History/Analytics remains under the separate controls in section 11. In-transit deliveries or failed remote requests may require further provider or support action. See the Kick Privacy Policy, Kick Terms of Service, and Kick Developer Terms.

9. KCW Labs services

KCW Labs processes the authorization exchanges described above to keep application client credentials on the server and enable the selected integrations. The current YouTube relay persistently stores rate-limit counters. The Kick relay stores delivery-access hashes, broadcaster associations, and queued event data in private server storage.

The Kick desktop feed serves events received during the preceding 10 minutes. Each new accepted event delivery runs cleanup of queued rows older than 20 minutes. Cleanup is triggered by deliveries, so stored rows can remain longer while deliveries are idle. Expired Kick access-hash records are removed during subsequent authorization exchanges. Contact us to request removal of server-held information you are entitled to have deleted.

Hosting and server backup systems can also hold operational records or copies. Access is restricted to operating and supporting the service, addressing security issues, and meeting applicable obligations. A request about server data should include enough channel or event information to locate the relevant records, without including an authorization token.

Activation, downloads, and updates

The desktop app sends your activation key on initial activation and uses a randomly generated installation credential to check activation, release the installation, and request protected updates. The licensing service stores a hash of that credential, a link to the license record, and license status and expiration information. It does not use a hardware fingerprint. Private download links are temporary credentials tied to a license. The service checks their validity and uses hashed values and request counters to limit abuse. Hosting access logs may record requests to these endpoints.

On Windows, the installation credential and signed offline activation are encrypted for the current Windows account. When writable, the app saves a copy beside the installed or portable program and keeps a recovery copy in the Windows registry. An app-data cleanup or reinstall can leave the activation available. To release an installation, go online and choose Help → Manage License. Contact KCW Labs for help with a lost activation.

Announcements

The app fetches a public KCW Labs announcement feed. The app keeps which notices you have read on your device. It does not send read status, linked account details, or an installation credential with this feed request.

10. Sharing and security

Website feature suggestions and beta applications are also sent to Discord through a private-channel webhook for KCW Labs internal notifications and review as described in section 2. Selected testers communicate through Discord; members with access to shared testing channels may view messages posted there. Discord processes those messages according to its own privacy practices. This website submission processing is separate from the desktop application's local giveaway records.

Other information moves to the platform or third-party software you connect, through the KCW Labs authorization or Kick delivery services where described, and to the audience you select through chat or broadcast displays. Hosting providers, optional website analytics providers, and support providers may process information needed for their functions. We may also process or disclose information where required by law or necessary to investigate abuse and protect the service.

Our purposes for platform information are the authorized giveaway and connection features described here. We do not sell platform data, website submissions, or local winner lists, or use platform information to build advertising profiles.

Desktop token storage uses the operating system's credential encryption where the integration is available. Export and recovery files use authenticated encryption with a random key stored in the local app configuration directory. That key has a separate role from the operating system's token protection. Protect your device, app data directory, exported files, and copies you make. Security depends on the surrounding system as well as the application's safeguards.

11. Retention, backups, and deletion

InformationCurrent handlingYour controls
Website submissionsPrivate server-side files plus restricted-access Discord webhook notifications. Retained as reasonably needed to review suggestions, evaluate beta applicants, coordinate testing, handle disputes, or meet applicable requirements; copies in backups and Discord may follow additional retention processes.Contact us to request access, correction, or deletion of KCW Labs-controlled copies, including the related Discord channel messages where identifiable and applicable.
Beta testing messagesDiscord messages, reports, and attachments are kept as reasonably needed for testing, support, safety, and administration, subject to applicable requirements and Discord's own practices.Ask KCW Labs about messages and files we control; use Discord's controls and privacy processes for information it handles independently.
Website analyticsOptional GA4 records follow the retention settings of the KCW Labs property. Google applies separate rules to aggregated reporting.Turn off Analytics in Cookie preferences, clear browser cookies, or contact us about an applicable data request.
Licenses and installationsPrivate license and activation records support issuance, renewals, access checks, and resets. Expired links stop working. Signed offline activation lasts up to 30 days after the last successful check, capped by any license expiration.Use Help → Manage License to release a PC. Contact us about stored license records or a reset.
Automatic entrants and recent activityTemporary entrants clear on normal closing and startup. Recent activity also expires after 24 hours. Kick backup imports use the seven-day file limit, current connection status, and fresh profile lookups.Edit or reset the active pool, close the app, or disconnect the service.
Manual entrants and settingsSaved locally between launches. Linked reward setup can include platform reward names, IDs, costs, and broadcaster associations.Edit the relevant settings or names, reset a pool, remove linked reward setup, or remove local app data. Platform disconnection removes relevant linked reward configuration.
Unsaved winners and later claimsSession memory until explicitly saved, closed, or removed by applicable platform expiry.Review Recent Winners, save the chosen details, or leave them unsaved.
Saved History/AnalyticsThe latest 100 records you explicitly save. Records remain until you delete them or a newer saved winner replaces the oldest record beyond that limit. Account disconnection and temporary cache expiry preserve saved logs.Use Edit Log to update a record or Delete Saved Record in Analytics to remove it. Contact support for help locating local history files.
Exported entrant poolsEncrypted files in your selected location. Import refuses files at least seven days old and checks platform availability. When Kick is linked, Kick IDs in an eligible backup are processed through fresh profile lookups even if the saved profile details were retrieved more than 24 hours earlier. Exported data contains entrant identities and counts, timestamps showing when the backup and entrant records were created or refreshed, and available profile-image links.Delete exported files and copies when no longer needed or when removal is required. Keep the local backup key only while access to eligible backups is needed.
Crash recoveryEncrypted entrant-only checkpoints can be restored for up to one hour. Normal closing removes the recovery file. Availability and expiry are checked on launch.Use Import Entrants List → Restore Previous Session when offered, or close the app to clear recovery data.
Diagnostics and connection recordsLogs follow the archive limit above. OAuth tokens remain protected locally while needed for the connection. Server records follow section 9.Disconnect accounts, manage provider access, remove local logs, or contact us about server-held information.

Deleting a website submission from KCW Labs server files does not automatically remove its Discord notification copy, and deleting a Discord message does not necessarily remove copies held in server backups or by Discord. We will address identifiable KCW Labs-controlled copies in response to applicable deletion requests, subject to lawful retention needs and technical limitations. When the information is no longer needed for the stated purposes, it is deleted or otherwise handled under our applicable retention and deletion practices.

Temporary Kick entrant and winner caches have a 24-hour source-data lifetime, and temporary YouTube caches have a 30-day lifetime. For a Kick import, the successful profile lookup supplies fresh field values and their new cache timestamp. Saved History/Analytics has its own retention controls described in the table.

Local cleanup requires the app to run. Expiry is evaluated during operation and on a later launch. The seven-day backup rule controls software acceptance of an import. Exported files, copied keys, and device backups remain in storage until their owner removes them. A lost key can also make an otherwise eligible backup unreadable.

Confirming a winner, editing a field, encrypting an export, or fetching fresh profile fields leaves the source of platform-derived data and the applicable platform obligations relevant. The lifetimes above describe implemented controls and do not extend a platform's permission to retain or use information.

Disconnecting a platform initiates removal of its temporary local entries, activity, unsaved winner details, and relevant reward configuration. Saved History/Analytics follows its explicit deletion and 100-record controls. A valid Kick backup can be imported after reconnection by fetching fresh profile fields. Storage failures are reported for attention and can be retried. Server relay data and exported copies have the separate handling described above.

Externally revoked access is handled when the app detects it. Deleting local StreamJuice data affects StreamJuice's copies. Information held by the platform is managed through that platform's own tools and request processes.

12. Your privacy rights and requests

Depending on your location, you may have rights to access, correct, delete, restrict, object to, or receive a copy of personal information. Where processing relies on consent, you can withdraw it without affecting prior lawful processing. You may also have a right to complain to a local data-protection authority.

Contact support@kcwlabs.xyz about website submissions, KCW Labs relay data, or other information we handle. We may ask for enough information to verify the request and locate the records. Applicable requests are handled within the periods required by law and relevant platform requirements.

For a streamer's local giveaway records, you can also contact that streamer. The streamer controls the device, local files, broadcasts, and exported copies. KCW Labs can provide removal instructions and coordinate a request about the services we control. Direct access to the streamer's device requires their participation.

Website submissions support product feedback, beta selection, related correspondence, and restricted Discord notifications used for internal review. Where applicable, we rely on the lawful bases relevant to responding to your requested service or beta application, our legitimate interests in managing feedback and operating and securing the program, and any consent required by law. Optional website analytics uses your preference where required. Account authorization enables the selected platform features. Applicable contractual, consent, security, and legal requirements govern the processing described here.

13. Children and international access

StreamJuice Desktop is intended for streamers who are permitted to connect and operate their platform accounts. This website does not knowingly solicit personal information from children below the applicable age of digital consent. If you believe a child supplied information, contact us for removal.

Our website and service providers may process data in the United States or other locations. Where legally required, we will use appropriate safeguards for international transfers.

14. Policy updates

Features, platform requirements, and privacy practices may change as the desktop application develops. We will update this page and its effective date when material changes occur, and provide further notice or request fresh consent when required.

15. Contact

KCW Labs / StreamJuice
support@kcwlabs.xyz
https://kcwlabs.xyz/streamjuice/

QUESTIONS ABOUT YOUR DATA?Get in touch ↗
StreamJuiceMade by KCW Labs · © 2026
PrivacyTermsContact
✦ Your privacy, your call.

We use essential storage to run this site. Optional analytics helps us understand visits. Choose what works for you.

YOUR CHOICE

Privacy preferences

Choose which optional technologies this StreamJuice site may use. Essential storage keeps forms and preferences working.

Essential

Security, form protection, and remembering your privacy choices.

Analytics

Optional, consent-based Google Analytics to understand site usage.

Embedded media

Allow future videos embedded from third-party platforms. No external video is loaded without this permission.

You can change this at any time using Cookie preferences in the footer. Read the cookie details.