Privacy Policy
YBees ("we", "us") provides YouTube live-chat analytics, bot/troll detection, and optional moderation tools for channel owners. This page explains what we collect, why, and what control you have over it. YBees is an independent tool and is not affiliated with, endorsed by, or sponsored by YouTube or Google.
1. What we collect
Account information
When you sign in with Google, we receive your name, email address, profile picture, and Google account ID from Google's OAuth service. If you use the free guest option instead, we only store the YouTube channel handle you give us — no Google account is involved.
YouTube data
If you connect a channel via Google sign-in, you choose what to grant during Google's consent screen:
| Scope | What it's used for |
|---|---|
| Read your channel's basic info | Identify which channel you're connecting and show its name/avatar in the dashboard. |
| Read live chat & comments | Pull chat messages and comments from your streams so we can analyze them (sentiment, bot scoring, trends). |
| Manage live chat bans (optional) | Only requested if you use Auto-Block. Lets YBees ban a user from your live chat on your explicit approval — either per match, or automatically if you configure a rule to auto-approve. We never ban anyone without a rule you created matching that user. |
You can decline the ban-management scope during sign-in and still use everything else — you'll just be asked to grant it later, only if and when you try to use Auto-Block.
Chat content
Messages and comments from streams you connect are stored so we can show you history, trends, and per-user profiles. This includes the message text, the author's public YouTube username/avatar/channel ID, and timestamps — the same information already visible to anyone watching your stream.
Payment information
Wallet top-ups are processed entirely by Stripe. We never see or store your card number — Stripe handles that on their own hosted checkout page. We only keep a record of the amount, timestamp, and Stripe's transaction reference.
Automatically collected
Standard session data needed to keep you logged in (a session cookie) and basic request metadata (IP address, timestamps) for security and abuse prevention.
2. How we use it
- Classify chat messages for sentiment, bot/troll likelihood, and coordinated-behavior patterns, using large-language-model providers (Google Gemini, and OpenRouter as a fallback) and our own detection logic.
- Show you analytics, trends, and per-user reports for channels you've connected.
- Execute moderation actions (bans) you've explicitly configured or approved.
- Process wallet top-ups and track usage-based charges against your balance.
- Operate, secure, and improve the service.
We do not sell your data, and we do not use your chat data to train our own models.
3. Who we share it with
We share data only with the service providers needed to run YBees, each under their own privacy terms:
- Google — for OAuth sign-in and YouTube Data API access.
- Google Gemini / OpenRouter — chat message text is sent to these providers to classify stance and bot likelihood. No account credentials are ever sent.
- Stripe — for payment processing on wallet top-ups.
We do not share data with advertisers or data brokers, and we do not sell personal data.
4. Your controls
- Disconnect a channel at any time — this revokes our access token and stops any further scraping of that channel.
- Delete your account and associated data by emailing us at hello@ybees.ai.
- Revoke Google access directly from your Google Account permissions page at any time, independent of anything you do in YBees.
- Turn off Auto-Block or delete any block rule at any time — nothing bans anyone unless a rule you created matches them and you (or the rule) approved it.
5. Data retention
We retain chat data and analytics for as long as your account is active, so historical trends stay useful. If you delete your account, we delete your stored data within 30 days, except records we're required to keep for billing/tax purposes.
6. Security
Access tokens and session data are stored server-side and never exposed to the browser in a readable form beyond what's needed to operate the app. We recommend enabling standard Google account security (2FA) on any Google account you connect.
7. Children's privacy
YBees is intended for channel owners and is not directed at children under 13. We do not knowingly collect personal information from children.
8. Changes to this policy
If we make material changes, we'll update the date at the top of this page and, where appropriate, notify you directly.
9. Contact
Questions about this policy or your data: hello@ybees.ai