Privacy Policy

Information OverlayHub accesses

When you authorize a YouTube connection, OverlayHub requests the Google OAuth permission https://www.googleapis.com/auth/youtube.readonly. It receives an access token and, when Google issues one for offline access, a refresh token. It uses the permission to identify the connected YouTube channel and obtain relevant live broadcast, live chat, subscriber, and related stream activity. This may include channel identifiers and names; broadcast identifiers and status; chat messages, author names and identifiers, timestamps, subscription identifiers and dates, and platform-provided event details. Viewers' public live chat content may appear in your OBS overlay and local moderation view.

If you also connect other supported services, OverlayHub processes comparable account and live chat information needed for their respective integrations. Google access is optional until you connect YouTube.

How the information is used

OverlayHub uses connected account data to authenticate the integration, find the relevant live broadcast and chat, display activity in the overlay and local control page, and support local moderation actions. The refresh token lets the app request a new access token when the old one expires, so you can reconnect without repeating the browser authorization on every launch. The app does not use Google user data for advertising or sell it. The YouTube integration requests read-only access; it does not post to YouTube or change your channel settings.

Storage and sharing

OverlayHub stores the YouTube access token, refresh token, and token expiration time in a local configuration file on the streamer's Windows computer: %LOCALAPPDATA%\OverlayHub\Plugins\YouTube\Config\youtube-config.json. These credentials are stored as application data so the account can reconnect. A hosted authorization service processes the authorization code and token refresh requests, using the app's client credentials to exchange data with Google's OAuth service and return tokens to the desktop app. The desktop app calls YouTube APIs to provide the integration.

OverlayHub also saves a local subscriber state file at %LOCALAPPDATA%\OverlayHub\Plugins\YouTube\Data\subscribers.json. It records known subscriber identifiers, channel names, subscription dates, and when they were first observed so the app can recognize new subscriber activity. During a session, OverlayHub processes live messages and keeps recent entries available in the local moderation view. When you show an OBS overlay or broadcast it, visible chat content may be seen by your audience and by the streaming platforms you use. OverlayHub does not share Google user data with data brokers or advertisers.

The website is hosted by a third-party hosting provider, which may process standard web requests and technical logs needed to serve these pages. The website itself does not ask for Google account authorization.

Retention and your choices

Live chat entries displayed in the overlay are temporary; the local moderation view keeps a recent in-session history. Local YouTube tokens and subscriber state remain on your computer until their files are removed. To delete them, close OverlayHub and delete %LOCALAPPDATA%\OverlayHub\Plugins\YouTube\Config\youtube-config.json and %LOCALAPPDATA%\OverlayHub\Plugins\YouTube\Data\subscribers.json. You can separately revoke OverlayHub's Google access at Google Account connections. Revoking access stops future authorized API requests but does not erase local subscriber state or chat content already included in a recorded or live broadcast. Platform operators may retain data under their own policies.

Community forum

Anyone can read approved community topics and replies. To post, you sign in with ChatGPT. The site receives a stable account identifier, email address, and an optional display name from that sign-in. It stores the identifier and your submitted text to attribute and review posts; it does not publish your email address. Approved posts are public. Submissions remain pending until reviewed, and rejected submissions are not shown publicly. We use this information to run and moderate discussions about OverlayHub. We keep posts until removed by moderation or upon a reasonable deletion request sent to OverlayHubSupport@gmail.com. ChatGPT sign-in is governed by OpenAI’s own terms and privacy practices.

Security

OverlayHub uses OAuth to request access rather than asking for your Google password. The local configuration file contains usable credentials; protect the computer and Windows account running the app. Access tokens expire, while refresh tokens may continue to work until revoked or invalidated. No system can guarantee absolute security.

Google and YouTube

By using the YouTube integration, you are also subject to the YouTube Terms of Service and Google Privacy Policy. Google permissions are requested through its consent screen and can be reviewed or revoked in your Google Account.

Updates and contact

We may update this policy when OverlayHub's features or data practices change. The effective date above will change when a revised version is published. For privacy questions or requests concerning your own OverlayHub installation, email OverlayHubSupport@gmail.com.