Privacy Policy
This Privacy Policy describes how StreamerCatalyst collects, uses, and shares information when you use our Twitch streamer toolkit, and the choices you have. Please read it alongside our Terms of Service.
1.Overview
StreamerCatalyst LLC ("StreamerCatalyst", "we", "us", or "our") provides a toolkit of features for Twitch streamers, including AI chat personas, channel-event and rewards tracking, moderation automation, a stream planner, analytics, chat tools, stream overlays, and a tipping feature that lets a streamer receive voluntary payments from their community. This Privacy Policy explains what information we collect, how we use it, who we share it with, and the choices and controls you have.
By connecting your Twitch account and using StreamerCatalyst, you agree to the practices described here. If you do not agree, please do not use the service.
2.A note for streamers, viewers, and tippers
StreamerCatalyst is used by three kinds of people:
- Streamers (broadcasters) who sign in with Twitch and configure the modules for their channel.
- Viewers and chatters in those channels, whose public activity (chat messages, redemptions, cheers, follows, and subscriptions) may be processed so the streamer's chosen tools can work.
- Tippers who send a streamer money through that streamer's public tip page. You do not need a StreamerCatalyst account to tip, and we never sign you in or create a login session for you. See Tipping: payments, tippers, and payouts.
3.Information we collect
a) Information we receive from Twitch when you connect
We use "Sign in with Twitch" (OAuth). We do not see your Twitch password. When you authorize StreamerCatalyst, Twitch provides us with:
- Your Twitch user ID, login (username), and display name;
- Your account email address;
- Your profile image URL; and
- OAuth access and refresh tokens that let us call the Twitch API on your behalf within the permissions you grant.
Tokens are encrypted (AES-256-GCM) before we store them and are used only to operate the features you enable.
b) Information generated as you use the modules
Depending on which modules you turn on, we store configuration and operational data such as:
- AI personas: per-viewer persona profiles synthesized from public chat, short rolling buffers of recent messages, broadcaster-defined "lore" / facts, AI-observed community patterns, a cross-channel record of viewers who have opted out, and each channel's own record of the opt-outs and opt-ins made in it.
- Events / Rewards: your reward and redemption rules, gift-sub and cheer (Bits) transactions, and per-viewer cumulative gift/Bits totals used to award rewards.
- Chatters: chat commands, regulars, quotes, giveaways and entries, activity counters, title grants, command counts, and bot API keys you generate.
- Modomation: redemption rules, VIP records, moderation events, an AutoMod cache, and ML moderation suggestions.
- Stream Planner: the boards and items you create.
- Numbers (analytics): stream sessions and follow, subscribe, gift, cheer, and resub events, plus aggregated metric buckets.
- Widgets: widget configurations, any custom widget code you write, uploaded assets, and overlay data.
- Tipping: your tipping settings (currency, minimum/maximum and preset amounts, who absorbs the processing fee, and your message and anonymity rules), your donation goals and any manual adjustments or off-platform tips you record, your tip ledger, and a reference to your Stripe connected account together with the status flags Stripe reports back (whether charges and payouts are enabled, what verification Stripe still needs, your country and settlement currency).
c) Viewer and chatter information
To power the features a streamer enables, we process public activity in that streamer's channel — for example chat messages (and the username/user ID attached to them), Channel Points redemptions, Bits/cheers, follows, and subscription events. This is processed on the streamer's behalf to provide the toolkit.
d) Payment information
Paid subscriptions are handled by Stripe. Stripe collects and processes your payment details directly; we do not receive or store full card numbers. We store a Stripe customer reference and your plan/subscription status (such as your tier and renewal dates).
Tips sent through a streamer's tip page are also processed by Stripe, and streamer payouts run on Stripe Connect. That flow is described in its own section below — see Tipping: payments, tippers, and payouts.
e) Information we receive from Tiltify
If you connect a Tiltify account, you sign in on Tiltify's own page. We store your Tiltify account ID, username, profile slug, and avatar so we know which campaigns are yours and the dashboard can show which account is connected. No Tiltify password or token is stored.
For a charity campaign you link, we receive its name, its cause, and its totals, and for each donation its amount and the donor's display name and comment as the donor entered them on Tiltify. We use them to run your alerts, rules, timers, goals, analytics, and Event Page.
f) Technical and log information
Like most web services, our infrastructure processes technical data such as IP addresses (used for rate limiting and abuse prevention), request metadata, and error logs. We use a small number of cookies described below.
4.Tipping: payments, tippers, and payouts
If a streamer turns on the Tipping module, their channel gets a public tip page at
streamercatalyst.com/tip/<twitch-login>. Anyone can tip there without a StreamerCatalyst account.
Payments run through Stripe, and streamer payouts run
through Stripe Connect.
a) What we store about a tip
For each tip we record an internal tip ID, the channel it was sent to, the amount and currency, our fee calculation, the message you wrote (if any), the time, the payment status (pending, settled, refunded, or disputed), and a Stripe payment reference so the payment can be reconciled, refunded, or defended in a dispute.
b) Anonymous tips versus tipping under your Twitch name
- Anonymous tips carry no identity. There is no "type your name" box on the tip page, and the tip record stores no user ID, login, or display name. The streamer sees only the amount and your message.
- Tipping under your Twitch name is opt-in and verified. If you choose it, you complete a Twitch authorization that requests no permissions at all (an empty scope). We receive only your Twitch user ID, login, and display name, carry them in a short-lived signed token (valid for about ten minutes), and store them on the tip record so the streamer can thank you. This does not sign you in to StreamerCatalyst and sets no login cookie.
c) What we never receive
Card numbers, bank details, billing addresses, and the identity documents Stripe collects never reach us. Card entry happens on Stripe's own hosted checkout page, and streamer identity verification happens inside Stripe's hosted onboarding.
d) Fraud and abuse prevention on the tip page
Every tip submission is checked by Cloudflare Turnstile, which processes technical signals about the request (including your IP address and browser characteristics) to distinguish people from bots. We also rate-limit tip attempts per IP address. This is used to blunt card testing and abuse, not for advertising or cross-site tracking.
e) Streamer payouts (Stripe Connect)
To receive tips, a streamer onboards to Stripe Connect (Express). Stripe collects their identity details, date of birth, and bank account directly. We store only the connected account ID and the status flags Stripe returns to us. We never see or store bank or identity-document data.
f) Tip messages and names are published
Tip messages — and your Twitch display name if you tipped under it — are shown to the streamer and can be posted publicly in their chat and on their on-stream overlays. Streamers can hold messages for approval, strip links, or filter profanity, but you should treat anything you write in a tip message as public. See How we share information.
5.The Twitch permissions we request
When you connect, we request only the baseline Twitch scopes below. The permissions that let us act on your channel — create a reward, add a VIP, act on a held message, send a shout-out, run an ad — are requested later, the first time you set up the feature that needs one, and never before. You control which modules you actually use, and you can revoke access at any time from your Twitch Connections settings.
| Scope | Why we request it | When we ask |
|---|---|---|
user:read:email | Identify your account and send you account, billing, and service notices. | At sign-in |
user:read:moderated_channels | See which channels you moderate, so you can be offered mod access to those channels. | At sign-in |
moderation:read | Confirm who a channel’s moderators are when granting dashboard access. | At sign-in |
channel:read:subscriptions | Read your subscribers so modules can react to subs and resubs. | At sign-in |
bits:read | Read Bits / cheers so modules can react to and track them. | At sign-in |
user:read:chat | Read your channel chat so AI personas and chat tools can respond. | At sign-in |
user:write:chat | Send chat messages on your behalf (bot replies, command output). | At sign-in |
user:bot | Let the account you choose read and send chat as an authorized chat bot. | At sign-in |
channel:bot | Operate as a chat bot in your channel. | At sign-in |
moderator:read:followers | Read follow events for analytics and follow-triggered automations. | At sign-in |
channel:read:redemptions | Read Channel Points redemptions to power the Events / Rewards module. | At sign-in |
channel:manage:redemptions | Create and manage the Channel Points rewards you configure. | When you set up the feature |
user:read:emotes | Read available emotes for the emote picker in message templates. | At sign-in |
moderator:read:chatters | Read your current chatter list for the Chatters module. | At sign-in |
moderator:manage:shoutouts | Send the native Twitch shout-out for !so and auto-shoutouts. | At sign-in |
moderator:manage:announcements | Post chat announcements for the auto chats you set to announcement delivery. | At sign-in |
moderator:read:shoutouts | Read shout-out activity so shout-outs are not repeated or duplicated. | At sign-in |
channel:manage:vips | Grant and remove VIP status for the Modomation VIP tools. | When you set up the feature |
moderator:read:vips | Read your current VIP list for those same tools. | At sign-in |
moderator:read:automod_settings | Read your AutoMod configuration so moderation automations respect it. | At sign-in |
moderator:manage:automod | Approve or deny messages AutoMod has held, where you automate that. | When you set up the feature |
moderator:read:blocked_terms | Read your blocked-term list for moderation tooling and suggestions. | At sign-in |
moderator:read:chat_settings | Read your chat settings (slow / follower-only / sub-only mode). | At sign-in |
moderator:read:warnings | Read warnings issued in your channel for the moderation history view. | At sign-in |
moderator:read:banned_users | Read bans and timeouts for the moderation history view. | At sign-in |
moderator:read:unban_requests | Read unban requests so they can be surfaced to your mod team. | At sign-in |
moderator:read:suspicious_users | Read Twitch’s suspicious-user signals for moderation suggestions. | At sign-in |
moderator:read:chat_messages | Read moderation actions taken on chat messages in your channel. | At sign-in |
moderator:read:moderators | Read your moderator list to resolve who has mod access. | At sign-in |
channel:read:polls | Read polls so modules can react to them. | At sign-in |
channel:read:predictions | Read Predictions so modules can react to them. | At sign-in |
channel:read:hype_train | Read Hype Train events so modules can react to them. | At sign-in |
channel:read:ads | Read your ad schedule so automations can work around ad breaks. | At sign-in |
channel:manage:ads | Start or snooze ad breaks where you configure an automation to do so. | When you set up the feature |
channel:manage:broadcast | Set your stream category and title where you enable the chat commands that do so. | When you set up the feature |
channel:read:goals | Read your Twitch creator goals for the Numbers analytics module. | At sign-in |
channel:read:charity | Read your Twitch Charity campaign and its donations for goals, alerts, and analytics. | At sign-in |
Tipping needs no additional permissions from a streamer. Separately, a tipper who chooses to tip under their Twitch name completes an identity-only authorization that requests none of the scopes above — it returns their user ID, login, and display name and nothing else, and it does not sign them in to StreamerCatalyst.
6.Cookies and similar technologies
Cookies the service needs
- Sign-in —
sessionkeeps you signed in for up to 7 days, andoauth_stateprotects the Twitch sign-in step for 5 minutes. Both areHttpOnly,Secure, and same-site restricted. - Tiltify sign-in —
__Host-sc_tiltify_stateis set only when you click Connect Tiltify, and protects that sign-in step for 10 minutes. It isHttpOnly,Secure, and same-site restricted. - Event Page sign-in —
sc_event_viewerremembers you on a streamer's Event Page after you sign in there with Twitch. It is set only when you ask to sign in. - Referral links —
sc_refis set when you follow a streamer's referral link, so the longer trial that link offers applies when you sign up. It lasts 30 days and is cleared when you sign in. - Your cookie choice —
sc_consentremembers your answer to our cookie question, including a "Reject all", for 6 months, so we do not ask again. - Infrastructure — our hosting provider (Cloudflare) may set cookies necessary for security and delivery of the service.
- Bot protection on tip pages — Cloudflare Turnstile checks that a tip submission comes from a person rather than a bot. It processes request signals (including your IP address) and may store a short-lived token in your browser for that check. The public tip page sets no login cookie.
Only if you accept
- Where you came from —
sc_srcrecords the link or website that brought you here, the page you landed on, and when, for 30 days in your browser. If you create an account, it is saved with the account so we can tell which posts and listings bring streamers. It is cleared when you sign in. It is first-party, not shared, and not used for advertising.
Your cookie choice
You have not chosen. Nothing about where you came from is recorded unless you accept.
We ask only when you arrive from a link or another website, and we never block the page to
ask. A new answer here takes effect at once; Reject all also deletes sc_src.
We do not use third-party advertising or cross-site tracking cookies.
7.How we use information
We use the information described above to:
- Provide, operate, and maintain the features you enable;
- Authenticate you and keep your account and channel secure;
- Generate AI personas, suggestions, and message content for the modules you use;
- Process payments, manage subscriptions, and send related notices;
- Process tips, route payouts to streamers, keep the tip ledger and donation goals accurate, and handle refunds, chargebacks, and reconciliation;
- Detect and prevent payment fraud, card testing, and abuse of the tipping features, and meet the anti-fraud and record-keeping obligations that come with processing payments;
- Send service and account notifications (for example release notes, billing reminders, and feedback follow-ups);
- Monitor, debug, prevent abuse of, and improve the service; and
- Comply with legal obligations and enforce our Terms of Service.
8.How AI features work
Several modules use AI. AI personas and command/message generation are produced using Cloudflare's Workers AI and AI Gateway. To generate output, relevant context (such as recent public chat for the channel and the configuration you set) is sent to these AI services.
- AI output can be inaccurate, unexpected, or generated in a tone you did not intend. Streamers control which AI features run in their channel and are responsible for the output posted there.
- Broadcaster-defined "lore" and persona data are used only to serve that channel.
- We do not sell your data or your viewers' data, and we do not use it to build advertising profiles.
9.How we share information
We do not sell your personal information. We share it only as needed to run the service:
- Twitch (Twitch Interactive, Inc.) — to authenticate you and to read/write the channel data you authorize.
- Cloudflare — our hosting, storage (KV, D1, object/asset storage), networking, AI, and bot-protection (Turnstile) provider.
- Stripe — to process subscription payments and, for the Tipping module, to run tip checkout, hold the payer's payment details, onboard streamers to Stripe Connect, verify their identity, and pay them out. Stripe also acts as an independent controller for its own payment, fraud-prevention, and regulatory purposes under the Stripe Privacy Policy.
- The streamer you tip — and, in effect, their audience. If you tip under your Twitch name, that name, the amount, and your message are shown to the streamer and may be posted publicly in their chat and on their on-stream overlays. If you tip anonymously, only the amount and message are shown. Treat a tip message as public.
- Legal and safety — when we believe in good faith that disclosure is required by law, or is necessary to protect the rights, property, or safety of StreamerCatalyst, our users, or the public.
- Business transfers — if StreamerCatalyst is involved in a merger, acquisition, or sale of assets, information may transfer as part of that transaction, subject to this policy.
These providers process information on our behalf or as independent controllers under their own privacy policies.
10.Data storage, security, and location
StreamerCatalyst runs on Cloudflare's global network. Your information is processed and stored on Cloudflare infrastructure in the United States and Europe. We do not offer region-locked storage, and we cannot promise that a given record stays within a single country or jurisdiction — see International users and data transfers below. Twitch OAuth tokens and session records are encrypted (AES-256-GCM) before storage. We apply reasonable technical and organizational measures to protect information, but no method of transmission or storage is completely secure, and we cannot guarantee absolute security.
Tip records live in our own database as described above; payment credentials, bank details, and identity documents live with Stripe, not with us.
11.Data retention
We keep information only as long as needed to provide the service and for legitimate business or legal purposes:
- Sign-in sessions expire automatically after a period of inactivity.
- Short-lived caches (such as deduplication and rate-limit records) expire on their own within minutes.
- Analytics retention depends on your plan tier, as shown on the pricing page.
- Tip and payout records are financial records. We keep them — including the amount, currency, status, payment reference, any tip message, and the tipper's Twitch name where the tip was not anonymous — for as long as we need them for accounting, tax, and dispute or chargeback purposes, typically up to seven years. That applies even after a goal is archived, tipping is switched off, or the channel disconnects.
- When you disconnect StreamerCatalyst or close your account, we delete or de-identify the associated channel data within a reasonable period, except where we must retain limited records (for example billing history and the tip and payout records above) to meet legal obligations.
12.Your choices and controls
- Disconnect anytime — revoke StreamerCatalyst's access from your Twitch Connections page, which stops further access to your channel.
- Viewer opt-out — a viewer's AI opt-out applies across every channel using StreamerCatalyst AI, not only the channel they asked in, and it stops persona processing in channels that adopt the module later. Opting back in is per channel, so a viewer can return to one channel while staying opted out of the rest. Both are self-service at ai.streamercatalyst.com/privacy/ai, where a viewer can also see and delete the AI data we hold for them per channel. A streamer cannot lift a viewer's opt-out on their behalf, and opting back in does not restore data already deleted.
- Broadcaster-initiated deletion — streamers can delete the data we hold about an individual viewer in their channel (for example a viewer's AI persona, message buffer, and related records).
- Tip without identifying yourself — where a streamer allows it, the tip page lets you tip anonymously, and no identity is attached to the tip. Tipping under your Twitch name is always a deliberate, separate step.
- Tippers' requests — you can contact us about a tip at support@streamercatalyst.com. Please include the Stripe receipt or payment reference: for an anonymous tip that reference is the only way we can locate the record, because the tip itself carries no identity. We will delete or de-identify what we are not required to keep as a financial record — see Data retention.
- Access, correction, and deletion — you can request a copy of the personal information we hold about you, ask us to correct it, or ask us to delete your account and data, by emailing privacy@streamercatalyst.com. We may need to verify your identity first.
- Notifications — you can manage in-product notifications from your dashboard.
13.Children's privacy
StreamerCatalyst is not directed to children. Twitch requires its users to be at least 13 years old (and, where applicable, to have parental consent), and you must meet Twitch's age and eligibility requirements to use our service. We do not knowingly collect personal information from children under 13. If you believe a child has provided us information, contact us and we will take appropriate steps to delete it.
Tipping carries stricter requirements: to send a tip you must be old enough to lawfully use the payment method you tip with and be its authorized user, and to receive tips a streamer must be at least 18 and pass Stripe's identity verification. See our Terms of Service.
14.International users and data transfers
StreamerCatalyst is operated from the United States and relies on a global infrastructure provider. If you access the service from outside the United States, your information may be processed in the United States and other countries that may have different data-protection laws than your own.
Where information originating in the European Economic Area, the United Kingdom, or Switzerland is transferred to a country that is not covered by an adequacy decision, we rely on the data processing agreements we have with the processors described in How we share information — including Cloudflare and Stripe — which incorporate the European Commission's Standard Contractual Clauses and, where applicable, the UK International Data Transfer Addendum.
15.Changes to this policy
We may update this Privacy Policy from time to time. When we make material changes, we will update the "Last updated" date above and, where appropriate, provide additional notice. Your continued use of the service after an update means you accept the revised policy.
16.Contact us
Questions, requests, or concerns about this Privacy Policy or your data? Email us at privacy@streamercatalyst.com.