YouTubers Discord bot
Privacy notice
Last updated: July 28, 2026
YouTubers uses Google sign-in only to verify the YouTube channel a Discord member chooses and to apply a configured creator role.
Information used for verification
After you approve Google's `youtube.readonly` permission, the verification service calls YouTube's channel endpoint for the selected channel's ID, title, and publicly reported subscriber count. The bot associates that result with your Discord user ID and the server where you ran `/verify`.
What we retain
The shared verification database retains your Discord user ID, Discord server ID, YouTube channel ID, channel title, subscriber count, and the time the record was last refreshed. This lets administrators rescan tier roles without asking you to sign in again.
What we do not retain or retrieve
The bot does not receive your Google password. It does not retain Google access tokens, refresh tokens, or token-expiry values after a verification completes. Although Google's consent screen describes the broader read-only YouTube scope, this implementation only calls the channel endpoint above; it does not call endpoints for videos, watch activity, or other private account data.
Google API Limited Use
YouTubers' use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is used only to provide the channel-verification and Discord-role feature described here. It is not sold, used for advertising, or used to train machine-learning models.
Website analytics
The site automatically uses Vercel Web Analytics for aggregate traffic statistics such as page views, referring pages, device type, browser, and approximate region. Vercel Web Analytics does not use cookies or permanently store a visitor identity; its short-lived visitor hash resets after 24 hours and is used only for aggregate reporting.
The site also sends cookieless Google Analytics measurement pings with analytics storage denied. Google may receive limited event information such as the page, timestamp, referrer, user agent, coarse location, a random number, and the denied consent state. No Google Analytics cookie or persistent Analytics client ID is stored by this site. Advertising storage, advertising user data, and ad personalization are always denied.
Neither analytics integration receives the Google sign-in details used for YouTube verification, the one-time Discord verification token, or the bot's saved verification record.
Affiliate links
Our public homepage may include clearly labeled affiliate links to third-party services. If you follow one, the provider may use a referral cookie to attribute your signup. We may receive non-cash hosting credit from a qualifying referral. We do not share your Discord account data, Google account data, or YouTube subscription information with affiliate providers.
Public Discord presence
The homepage may show the aggregate number of members online using Discord's public server widget. Our server fetches and caches only that count for display. The site does not display or retain the widget's public member list.
Requests and changes
To correct or remove a verification record, contact an administrator of the Discord server where you verified. Administrators use a reasoned, confirmed removal that deletes only that server's association and explicitly configured YouTube subscriber roles. You can also revoke YouTubers access from your Google account's third-party access settings.
Third parties
Google processes sign-in, analytics, and YouTube Data API requests under its own policies. Discord processes membership and role assignments under its own policies. This YouTubers community is not affiliated with YouTube.
Read the integration policy.