Privacy Policy

1. Who this covers

This policy applies to people using the current StreamPixels preview, including viewers who claim or link a persistent StreamPixels profile and creators who authorize provider connections so StreamPixels can react to live events from Twitch or YouTube.

2. Data we collect for viewer sign-in and linked accounts

When an audience member signs in or links Twitch or YouTube, StreamPixels may collect and store the data needed to identify the linked account and keep the profile usable across sessions.

• Provider user IDs, login names, display names, avatar URLs, and email addresses when the provider supplies them.
• Linked identity records that associate a Twitch or YouTube account with a StreamPixels viewer profile.
• Viewer profile data such as display name, avatar/loadout state, owned items, creator memberships, and last-seen timestamps.
• Remembered session data used by the web app to keep the signed-in viewer attached to the correct profile and creator context.

3. Data we collect for creator connectors and live ingest

When a creator connects Twitch or YouTube, StreamPixels stores the connector state needed to keep that channel's ingest path alive and to show diagnostics in the creator console.

• OAuth access tokens, refresh tokens, granted scopes, and token expiry times.
• Connected account and channel metadata such as account IDs, login names, display names, and avatar URLs.
• Runtime connector state such as active broadcast IDs, YouTube live chat IDs, polling timestamps, webhook status, last errors, and event counters.
• Ingested Twitch or YouTube event data needed to drive overlay behavior, diagnostics, dedupe, and recent-event views.

4. How we use the data

• To authenticate viewers, claim or link viewer profiles, and remember signed-in sessions.
• To let viewers keep one persistent profile across supported streamer communities.
• To let creators connect Twitch or YouTube and run provider-native ingest for their own channels.
• To discover active broadcasts, read live chat or other authorized provider events, and trigger overlay scenes and related runtime behavior.
• To show account status, connector diagnostics, recent events, and other operational information in the web app.
• To secure the service, investigate failures, and prevent misuse.

5. Google and YouTube data

StreamPixels currently uses Google and YouTube data in two ways:

• For audience members who sign in or link a YouTube identity to a StreamPixels viewer profile.
• For creators who connect YouTube so StreamPixels can discover active broadcasts and poll live chat for that creator's stream.

Google and YouTube data is used only to provide or improve StreamPixels features the user explicitly asked us to run.

• We do not sell Google user data.
• We do not use Google user data for targeted advertising.
• We do not use Google user data to train generalized AI or machine learning models.
• We do not use Google or YouTube data to fabricate unrelated progression, audience profiling, or off-platform behavior that the connected provider did not actually send.

6. Sharing and access

We do not sell personal data. Access is limited to the people and systems needed to run the service.

• Authorized GameCult operators may access service data when needed to run, secure, debug, or recover StreamPixels.
• Authorized creator admins can access creator-scoped settings and diagnostics for their own creator context.
• Hosting and infrastructure providers may process data only as needed to host, secure, or back up the service.
• We may disclose data when required by law, legal process, or to protect the service and its users.

7. Retention, disconnect, and deletion

• Creator connector tokens and related connector metadata are retained while the connector is active.
• Disconnecting a creator-side Twitch or YouTube connector clears the stored access token, refresh token, granted scopes, connected account details, and runtime state for that connector.
• Ingested event records are kept in a bounded operational log. The current preview deployment defaults to a 14-day retention window for ingested events.
• Viewer profile data, linked identities, and creator membership state may remain until the account is no longer needed for service operation or a deletion request is processed.
• Viewer self-service unlink and deletion tooling is not fully built out yet, so privacy, unlink, or deletion requests should be sent to meta@gamecult.org.

8. Security and updates

StreamPixels uses signed session and OAuth state data, role-based access checks, and a public HTTPS deployment model for the hosted preview. No internet system is perfect, but access is intended to stay limited to the components and operators that actually need it.

We may update this policy as the product changes. When that happens, we will publish the revised version here and update the effective date at the top of the page.