Privacy Policy

1. Who we are

QuadBit LLC (“QuadBit”, “we”, “us”, or “our”) operates HypeTally, a streaming overlay platform with live overlays for YouTube, Twitch, and Discord; viewer donations through Stripe Connect; a visual overlay editor; and related dashboard tools for use in OBS and on the web. This policy explains what we collect and why.

HypeTally uses YouTube API Services. By using HypeTally, you also agree to our handling of information as described here and to Google’s practices described in the Google Privacy Policy.

2. Information we collect

Depending on how you use HypeTally, we may collect:

• Account data — email address and authentication credentials managed through our auth provider (Supabase), including email/password sign-in or Google account sign-in where offered.
• Creator profile data — display name, public overlay slug, YouTube video ID, live chat ID, Twitch channel settings, polling preferences, like goals, donation page settings, overlay HTML or editor documents you save, and related dashboard configuration.
• YouTube connection data — either a Google Cloud API key you paste into HypeTally, or encrypted YouTube OAuth refresh tokens and channel metadata when you connect YouTube through OAuth. Keys and tokens are stored on your profile and are not embedded in public overlay URLs.
• YouTube API Data (polled) — like counts from videos.list, subscriber counts from channel statistics where enabled, and new-member event details from liveChat/messages (such as display name, profile image URL, member level, and event time) for the IDs you configure.
• YouTube members roster — if you upload a CSV export from YouTube Studio, we store member display names, membership levels, prices, and tenure data you include in that file for roster overlays.
• Twitch connection data — Twitch user ID, login, display name, encrypted OAuth refresh token, and related channel configuration when you connect Twitch.
• Twitch API / EventSub data — subscription counts, follower counts, bits, raid events, hype train state, and live status for overlays you enable.
• Discord configuration — guild ID, voice/text channel IDs, role IDs, and related settings for queue, on-air, and donation moderation features when you link a server.
• Support Discord linking — optional Discord user ID and short-lived verification codes when you verify your account for support.
• Live chat data — display names, avatars, message text, badges, and tip or Super Chat amounts from YouTube, Twitch, or other platforms you connect (including via optional browser extension relay). Chat is buffered temporarily for overlay display and is not stored as a long-term message archive.
• Billing data — subscription status, trial status, trial or billing period end dates, plan tier (such as Standard or Friends), Stripe customer and subscription identifiers, and related billing metadata handled by Stripe. We do not store full payment card numbers on HypeTally servers. If you start a free trial without a card, Stripe may still associate your account email with a Stripe customer record.
• Donation data — when you enable viewer tips, we store Stripe Connect account identifiers, donation amounts, donor display names and messages viewers submit, donation page customization, and related dashboard settings. Card payments are processed by Stripe; we do not store full viewer card numbers. Stripe may send receipt emails to donors when an email is provided.
• Uploaded overlay assets — custom fonts, images, and videos you upload in the editor (stored in our infrastructure).
• Community designs — HTML, editor documents, and metadata you choose to upload to the designs gallery.
• Contact and support data — name, email, and message content you submit through contact forms; support tickets may include Discord username and thread identifiers.
• Analytics data — when enabled, page paths and interaction events through Google Analytics.
• Usage and technical data — request logs, cookies and session tokens needed to keep you signed in, OAuth state cookies, short-lived desktop plugin linking tokens, operational audit logs, and similar data needed to run and secure the Service. Authorized QuadBit staff may access account data when providing support, including limited admin impersonation for troubleshooting when necessary.

3. How we use YouTube API Services and other information

We use the information above to:

• Create and secure your account
• Call YouTube API Services and/or use YouTube OAuth to fetch likes, subscribers, members, and chat-related data for your configured channels and streams
• Call Twitch API Services and EventSub using your connected Twitch account for overlays you enable
• Use Discord bot APIs to read queue and on-air state for overlays and related dashboard features
• Display platform data in your dashboard and OBS overlays (including simple progress toward a like goal you set — calculated from the YouTube like count)
• Render members roster overlays from CSV data you upload
• Buffer and display recent live chat for chat overlays
• When you enable the HypeTally chat bot, read live chat for custom commands and post bot replies and HypeTally alerts (tips, members, subs, Discord queue) into YouTube and Twitch chat from a shared bot account you moderate
• Serve your OBS overlay URLs and dashboard settings
• Process subscriptions, start and manage free trials, and control plan access (including locking features when a trial ends without payment or a subscription lapses)
• Facilitate viewer donations through Stripe Connect, show them in your dashboard, and display donation alerts in OBS when configured
• Store and deliver uploaded fonts, images, videos, and editor documents
• Handle contact requests, support tickets, and optional Discord verification
• Show community designs you publish or apply
• Measure site usage through analytics when enabled
• Maintain, debug, audit, and improve the service

We do not sell YouTube API Data. We do not use YouTube API Data to build advertising profiles, harvest viewer identities beyond the new-member ticker events you choose to display, or create substitute metrics that replace YouTube’s official statistics.

4. How information is shared

Information may be shared with:

• Supabase — authentication, database hosting, and file storage for accounts, profiles, and uploaded assets
• Stripe — subscription billing (including free trials), trial end dates, and Stripe Connect viewer donations
• Google / YouTube — when our servers call YouTube API Services or use YouTube OAuth with your connected channel; Google also processes Google account sign-in when you use that login option, under the Google Privacy Policy
• Twitch — API calls and EventSub webhooks using your connected Twitch account
• Discord — bot APIs for creator server features; our support server for tickets, verification, and contact notifications when you use those features
• Google Analytics — aggregated usage analytics when a measurement ID is configured
• CDN providers — delivery of fonts, icons, and other assets used in overlays (for example Font Awesome or jsDelivr where referenced)
• Anyone with your overlay URL — overlays are public browser sources and may show current stats, queue state, chat messages, roster names, and donation alerts pulled from connected platforms
• Hosting providers — infrastructure that delivers the app

We do not allow unrelated third parties to serve advertisements inside HypeTally using your YouTube API Data.

5. Public overlays and gallery content

Your overlay URLs (for example like, member, subscriber, Twitch, Discord, chat, and donation browser sources) are designed to be loaded by OBS and may be accessible to anyone who has the URL. Do not put secrets in overlay HTML or uploaded assets. Community designs you publish may be visible to other users. Chat and donation overlays may show viewer display names and messages you choose to display on stream.

6. Cookies and device storage

HypeTally stores, accesses, or collects information on or from your device by placing or recognizing cookies or similar technology (such as session tokens and OAuth state cookies) so you can stay logged in, complete third-party connections, and so the app can operate securely. When Google Analytics is enabled, it may set its own cookies or use similar technology to measure site usage.

Overlay browser sources may keep short-lived in-browser state while open (for example the last like count, chat messages, or member list) and may use WebSocket connections so the ticker can update live; that state is not used as a long-term archive of platform data.

7. Data retention

HypeTally polls connected platforms for fresh data while your overlays or dashboard are active. We do not keep a permanent historical warehouse of like counts, Twitch events, or chat messages. Temporary display/cache of YouTube API Data (such as public like statistics) is limited to what is needed to run the Service and is not retained longer than allowed under the YouTube API Services Developer Policies (generally no more than 30 days without refresh or deletion).

Live chat used for overlays is kept in a short in-memory buffer for display and cleared during normal operation — not as a searchable archive. Members roster CSV data remains on your profile until you delete or replace it. Twitch and Discord configuration values remain until you disconnect those integrations or delete your account.

Your API key, OAuth tokens, video ID, live chat ID, and similar configuration values remain on your creator profile until you change, revoke, or remove them or delete your account. Those are configuration values you provide, not a stored copy of third-party audiovisual content.

8. Data deletion and access controls

You can update or clear connection settings in the dashboard, disconnect YouTube or Twitch OAuth, unlink Discord, rotate your YouTube API key at any time, clear uploaded members roster data, and pause polling. You can request deletion of your HypeTally account and stored profile data by contacting us; we will delete that data as soon as practicable and within 7 calendar days of a verified request, except where we must retain limited records for billing, security, or legal obligations (for example Stripe payment records).

Deleting data stored by HypeTally does not delete data stored by YouTube, Twitch, Discord, Google, or Stripe. Use each provider’s account tools to manage data they hold.

Revoking access: For HypeTally login, use account settings or contact us. For YouTube, remove or rotate your API key in the dashboard and/or Google Cloud Console, or disconnect YouTube OAuth in the dashboard. For Twitch, disconnect Twitch in the dashboard. For Google account permissions, review third-party access at Google security settings → Third-party access.

Third-party AI tools: The dashboard may let you copy prompts for external AI services. HypeTally does not transmit your overlay data to Anthropic or other AI providers; if you paste data into a third-party tool, that tool’s privacy policy applies.

9. Security

We use industry-standard practices such as encrypted transport (HTTPS), access-controlled databases, and separating public overlay routes from secret credentials. We do not request or store YouTube login passwords. No method of transmission or storage is perfectly secure, so protect your HypeTally password and YouTube API key.

10. Children’s privacy

HypeTally is intended for streamers and creators who can form a binding contract. 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.

11. Your choices

• Update profile and connection settings in the dashboard
• Connect or disconnect YouTube (API key or OAuth), Twitch, and Discord integrations
• Rotate or remove your YouTube API key at any time
• Clear uploaded members roster CSV data
• Pause YouTube or Twitch polling when you are offline
• View trial status and end date in the dashboard; add a payment method or subscribe before your trial ends through the Stripe customer portal linked from the dashboard
• Manage or cancel billing through the Stripe customer portal linked from the dashboard
• Stop publishing community designs or request removal of designs you own
• Limit analytics tracking through browser controls or extensions when Google Analytics is enabled
• Request account / stored data deletion as described above

12. Changes

We may update this Privacy Policy from time to time. The “Last updated” date at the top will change when we do. If we start using YouTube API Data in a materially new way not covered here, we will update this policy and require renewed acceptance where required. Continued use of HypeTally after an update means you accept the revised policy.

13. Contact

Questions or complaints about privacy practices for HypeTally? Email QuadBit LLC, visit our contact page, or start with the FAQ. For Google’s practices, see the Google Privacy Policy.