Privacy Policy

This Privacy Policy explains how OldManObserver ("we", "us", "our") collects, uses, and shares information when you use ViewerFrenzy (the game) and related services, including viewerfrenzy.com, streamer.viewerfrenzy.com, and manage.viewerfrenzy.com (collectively, the "Services").

If you do not agree with this Privacy Policy, please do not use the Services.

1. Information we collect

1.1 Account information (Twitch, Google/YouTube, or Kick sign-in)

When an approved sign-in option is enabled and you choose it, we verify your provider identity and associate it with a canonical ViewerFrenzy account. Available providers and features can differ during rollout; this notice is not a claim that all integrations are enabled or live-tested.

• Identifiers: your ViewerFrenzy account ID and the exact verified Twitch, Google, or Kick account identifier, together with a provider login where supplied. Google account identity, YouTube channel identity, and the sender of an actual chat message are distinct; a matching name, email address, or channel-management permission does not by itself link accounts.
• Profile information: provider display names and profile image URLs. Account Connections lets you save a public name/avatar snapshot from an active verified identity on your account. That snapshot persists across sign-ins and reloads; changing it does not change account IDs, transfer history, or automatically follow future provider profile changes.
• Access/entitlement checks: information needed for features you choose and are authorized to use, such as applicable channel-role or entitlement checks.
• OAuth and verification data: approved scopes, expiry, verification status, short-lived authorization attempts, and one-use proofs for sign-in, linking, or fresh owner actions. The new broker handles provider authorization server-side; successful website callbacks save only a ViewerFrenzy application session in browser storage, not provider access/refresh credentials.

Legacy Twitch compatibility login remains available when the broker is off. It receives a transient Twitch access token for exchange into a ViewerFrenzy session. Older browser/device versions may already hold Twitch tokens; they are not silently uploaded or converted into server-held channel grants, and this website update is not a claim that every older client or stored credential has been retired. The exact provider fields and permissions depend on the authorization you approve.

1.2 Game and gameplay information

When you play ViewerFrenzy (including participating via stream), we may collect and store gameplay data to operate the game and generate leaderboards/stats.

• Competition results: finishes, placements, points, races joined, wins, and other stats.
• Customization and preferences: default vehicle selection, cosmetic selections, and related preferences you save.
• In-game identifiers: canonical ViewerFrenzy IDs used to associate stats, inventory, and preferences with your account, separately from linked sign-in identities and channel permissions.

1.3 Community content (UGC) you create or upload

If you create or upload content (for example: community maps/tracks, map metadata like name/description, or other creations), we store that content and associated metadata.

• Map metadata: map name, description, creator, timestamps, versioning, and configuration data.
• Moderation status: flags such as removed/disabled or featured/official status.

1.4 Official promotional recordings

If you participate in a ViewerFrenzy session designated for official promotional recording, we may collect and create recordings, screenshots, clips, and related metadata. These materials can include in-game usernames, display names, profile images, maps, gameplay actions, results, and chat messages displayed by the Services.

If a streamer agrees to be featured in official promotional materials, we may also collect the information needed to document that agreement, such as their legal name, contact information, Twitch or channel identity, release version, signature timestamp, and agreed credit or compensation terms. We keep this information private except as described in this policy or in the applicable agreement.

1.5 Purchase and entitlement information

ViewerFrenzy may offer in-game purchases (such as skins) processed through third-party platforms (for example, Steam). We do not collect or store your full payment card details.

• Transaction/entitlement references: purchase receipts or entitlement IDs needed to grant you items.
• Inventory state: records indicating what digital items you own in ViewerFrenzy.

1.6 Technical information

Like most online services, we and our infrastructure providers may collect technical information when you access the Services.

• Device and browser data: user agent, language, and similar details.
• Log data: IP address, timestamps, error logs, and request metadata for security and troubleshooting.
• Local storage: the website stores its ViewerFrenzy session and preferences in localStorage. A broker authorization uses a fresh initiating secret in that tab's sessionStorage to resume and verify the attempt; it is not an account identity supplied in a return URL.
• Cookies: the broker uses a short-lived, host-only HttpOnly cookie to bind the provider callback to the initiating browser. Separate administrative sign-in and other required security functionality may use cookies. We do not knowingly use third-party advertising cookies for ViewerFrenzy.

1.7 Optional provider channel connections (separately controlled rollout)

Broker sign-in, identity linking, and server-held Twitch, Google/YouTube, and Kick connections default off and require separate approved activation. A sign-in or identity link does not consent to channel access. In Account Connections, connecting or reconnecting explicitly requests the supported features you select; YouTube connections require selection of a server-verified channel. The provider consent screen shows the actual permissions requested for identity/own-channel verification and those features.

When an enabled connection is authorized, its access/refresh grant is stored encrypted at rest on our servers, with the VF owner, verified provider account/channel identifiers, granted scopes, expiry, revision, and connection status. Grants are used for the approved connected features, such as supported chat receive/send, user lookup, or Twitch own-channel role checks. Only permissions needed for available, selected features are requested, not speculative future permissions or automatic paid-event access. Stored connection grants are not returned to website or Unity clients. Sign-in/link verification does not itself retain a provider grant as a channel connection.

Connection authorization, available capabilities, and actual live-chat/runtime readiness are separate. A connected grant is not proof that a collector is running or a live chat exists. Missing scopes, expiry, disconnection, unknown runtime status, or a provider outage do not by themselves sign you out of your independent ViewerFrenzy account. Existing browser/device credentials are not automatically migrated; connecting always requires separate explicit authorization.

1.8 Provider operations and support diagnostics

Enabled Twitch, YouTube, and Kick integrations can receive authorized channel events and publish the event messages you configure to the destinations you select. ViewerFrenzy uses YouTube API Services for enabled YouTube features. Sign-in, receiving channel events, and sending chat are separate permissions; a saved checkbox or linked identity does not grant access to an unbound channel. Provider access and refresh grants for these server integrations are encrypted server-side. Existing native Twitch credentials and optional Streamer.bot passwords remain local to the game; those passwords are not part of shared setup, administrative diagnostics, or support reports.

Authorized connection diagnostics can include your canonical VF account ID, provider/channel IDs, granted or missing permission names, selected live-chat status, session generations, queue counts, reconnect reasons, quota/rate state, configuration conflicts, and delivery outcome codes. They do not need token values, authorization codes, private keys, raw provider messages, or Streamer.bot passwords. Native Twitch observations and acknowledgments are host-reported; a server session or message receipt does not prove independent delivery, recipient consumption, or server-simulated gameplay.

Administration and support access is role-controlled. Changes to rollout controls and connection lifecycle actions are audited using bounded identifiers and action codes. A populated-account conflict can produce a proof-bound, read-only collision report; it does not authorize an account merge, balance sum, immutable-ledger rewrite, or transfer of another account's history.

2. How we use information

• Provide the Services (sign-in, saving preferences, showing stats, and operating competitions).
• Personalize your experience (remember your default vehicle/cosmetics).
• Moderate and enforce rules (prevent abuse, remove prohibited content, and protect the community).
• Improve and debug (monitor performance, fix bugs, and develop new features).
• Security (detect fraud, protect accounts, and protect our infrastructure).
• Official promotion and marketing (create, edit, publish, distribute, and advertise ViewerFrenzy trailers, clips, screenshots, store pages, social media, and press materials, subject to the Terms and any applicable separate creator release).

3. How information is shared

We do not sell your personal information.

3.1 Public visibility (leaderboards and stats)

ViewerFrenzy is designed to be stream-enabled. Your ViewerFrenzy public profile, including a selected name/avatar snapshot, any displayed provider login, and gameplay results may be visible in leaderboards, stats pages, and stream overlays. Choosing a different profile does not move or erase those results.

3.2 Official promotional distribution

For designated official promotional recordings, we may share the recorded materials with video, social media, storefront, advertising, press, editing, hosting, and content-delivery providers to publish and promote ViewerFrenzy. Materials made public through those services may be copied, embedded, or reshared according to the receiving service’s terms and controls.

3.3 Service providers and infrastructure

We use third-party providers to host and operate the Services (for example, hosting, databases, and content delivery). These providers process information on our behalf to deliver the Services.

3.4 Third-party platforms you choose to use

• Twitch, Google/YouTube, and Kick: when enabled and chosen, identity verification and separately authorized supported channel features. Information needed for the particular provider authorization or approved operation is exchanged with that provider; a linked identity alone does not grant authority to operate a channel.
• Steam (or other storefront/platforms): purchase processing and entitlement verification.

Google API data is used for the enabled, user-authorized identity and channel features described here, not for advertising profiles, sale of personal data or unrelated secondary purposes. The Google API Services User Data Policy, including its Limited Use requirements, governs this handling. Publication of this notice does not certify Google/YouTube verification, quota approval or any other provider review.

3.5 Legal and safety

We may disclose information if required to do so by law, or if we believe in good faith that disclosure is necessary to comply with legal obligations, protect the safety of users, investigate abuse, or protect our rights.

4. Data retention

We keep information only as long as needed to provide and operate the Services, comply with legal obligations, resolve disputes, and enforce agreements.

• Gameplay stats and leaderboards may be retained long-term to preserve competitive history.
• Removed community maps may be retained for moderation/audit purposes, but can be disabled from public access.
• Official promotional recordings and related release or consent records may be retained for the duration needed to run the campaign, meet legal obligations, resolve disputes, and enforce agreements. Published materials may remain available as permitted by the Terms, a separate creator release, and applicable law.
• We may retain backups for a limited time even after deletion requests are processed.

4.1 Connection credentials, verification records, and provider-derived data

Disconnect and revoke operations fence local use and delete the encrypted connection payload. Erasing our credential copy does not itself revoke permission at the provider or delete other provider-derived data. Provider revocation is separately attempted and may report that additional owner action is required. Pending downstream stop work is also reported separately; a local operation is not certification of a remote provider action or an independently running collector.

Authorization attempts and proofs are short-lived and one-use. Expiry prevents reuse; it is not a guarantee of immediate scheduled deletion. Minimal connection/account audit records contain owner identifiers, timestamps, and event codes, not token values or chat/profile payloads, and are separate from encrypted credentials and frozen gameplay history.

Connection-specific cleanup distinguishes encrypted grants, provider-derived profile/channel/live-chat metadata and pending technical work from first-party VF account ownership, authored content, competition outcomes, entitlements, wallets and append-only records. Disconnecting one provider must not reset your VF account or unrelated connections. Minimal ownership reservations and immutable histories are not permission to keep provider-derived presentation data indefinitely; mixed legacy records, backups and legally required retention need a separately reviewed deletion procedure.

For enabled YouTube features, you can request removal of stored YouTube API data through our privacy contact and revoke access in Google account permissions. Removing VF's copy does not remove content from YouTube. YouTube's policies require prompt handling: an in-app consent revocation or user deletion request has a seven-calendar-day deletion limit, while external revocations must be detected and associated data removed within the applicable thirty-day limit. Most cached YouTube API metadata must be refreshed or deleted within thirty days. These are provider requirements, not a claim that an undeployed integration or background cleanup has passed production verification. Relevant provider rules also apply to Twitch and Kick data.

New-provider production activation remains gated on verified cleanup/revocation behavior, a finite audit and backup schedule, review of current provider terms and required application verification. A local cleanup result is not confirmation of remote revocation, a completed downstream stop or erasure from backups. Unavailable or unsupported cleanup is reported as pending review rather than silently declared complete. The general history and backup statements create no exception to provider rules or deletion rights. Contact us for a verified privacy/deletion request.

5. Security

We use reasonable administrative, technical, and physical safeguards designed to protect information. However, no method of transmission or storage is 100% secure.

6. Children’s privacy

The Services are not intended for children under 13. We do not knowingly collect personal information from children under 13. If you believe a child under 13 has provided personal information to us, please contact us and we will take appropriate action.

7. Your rights and choices

Depending on where you live, you may have rights to access, correct, delete, or receive a copy of certain personal information we hold about you. You may also have the right to object to or restrict certain processing.

To request access or deletion, contact us using the contact method below. We may need to verify your identity, for example by confirming an active verified sign-in associated with the relevant ViewerFrenzy account; this is not limited to Twitch.

For a designated promotional recording session, the notice will identify how to opt out before participating. You may also contact us to ask that we do not use you in future promotional recordings. We will review requests to remove or limit published material in accordance with applicable law, the Terms, and any separate creator release; removal may not be possible where material has already been published, redistributed, or is retained for legal or archival purposes.

7.1 Provider connections, sign-out, and unlinking are different

• Disconnect a connection: fence ViewerFrenzy's authorization to use that connection and delete its encrypted token payload, without unlinking sign-in or ending unrelated connections. This alone does not confirm provider revocation or completion of downstream stop work.
• Revoke provider permission: withdraw authorization at the provider. You can review Twitch permissions in Twitch Connections and Google/YouTube permissions in Google account permissions. VF's revoke action separately requests supported provider revocation and reports when additional owner action is required; a failed or incomplete request is not reported as remote success. Kick's user-facing permission-settings route remains to be confirmed before activation. These links describe provider controls, not a claim that ViewerFrenzy has connected your account.
• Sign out of ViewerFrenzy: end your ViewerFrenzy session or clear local sign-in state; this does not by itself revoke provider permission or disconnect a server-held grant.
• Unlink a sign-in identity: deactivate that sign-in, fence affected server-held grants, and invalidate existing VF sessions after fresh owner verification. At least one usable sign-in must remain. Historical ownership stays reserved to the same canonical account to prevent takeover; unlinking is not account deletion, a history transfer, or proof of provider revocation.
• Link or review a conflict: verified linking keeps the same VF account. If an identity belongs to a separate account/history, controlled consolidation is preview-only: neither account is silently switched, merged, deleted, or stripped of history. Privacy/deletion requests remain separate and are handled subject to applicable provider rules and law.

Provider handling is also described in the Twitch Privacy Notice, Google Privacy Policy, Kick Privacy Policy, and YouTube Terms of Service. Privacy and deletion questions can be sent using section 9. Provider-specific consent notices, removal behavior, and retention obligations still require review before launch; this notice is not a compliance certification.

8. Changes to this policy

We may update this Privacy Policy from time to time. We will post the updated version on this page and update the “Last updated” date.

9. Contact

For privacy questions or requests, contact OldManObserver via the contact form on oldmanobserver.com.

This document is provided for general informational purposes and should be reviewed for your specific legal requirements.