OhItsDaneee

OhItsDaneee Soundboard

Community games and stream interactions

Privacy Policy

Last updated:

This policy covers OhItsDaneee Soundboard at officialgamershub.com/soundboard, its related Twitch extensions and connected community features. The controller/operator is Dane Beckman, operating as OhItsDaneee Soundboard. Use our private contact form for questions or to exercise your rights. The form works without signing in.

Google user data: access, use, storage, sharing and deletion

This section explains how OhItsDaneee Soundboard handles information received through Google OAuth and YouTube API Services. The detailed sections below also cover Twitch, Kick and information created on this website.

Data we access and collect

When you choose YouTube sign-in, we request openid, profile and https://www.googleapis.com/auth/youtube.readonly. We use the YouTube Data API to obtain your channel identifier, channel name and profile-image URL. We do not collect your Google password or use this permission to upload, edit or delete YouTube content. We separately retrieve public broadcast information to display the stream and its title. Stream chat is display-only; this website does not request the broader YouTube permission for sending chat messages.

How and why we use Google user data

Your channel identifier connects your YouTube identity to your Soundboard account, local points balance and community-game participation. Your channel name and profile picture can identify you in account controls, public rankings, game rosters and results. We also use the identity to recognise the configured site owner, maintain account permissions, prevent duplicate accounts and verify continued authorization. Soundboard points and game results are records created by this service, not YouTube channel-performance metrics.

Storage and data protection

Our server database stores the linked channel identifier, name, profile-image URL and the account records needed for these features. We store a Google refresh token encrypted with authenticated encryption so we can recheck authorization and refresh your profile. Short-lived Google access tokens are used temporarily in server memory and are not saved in the Soundboard database. Browser-to-site connections use HTTPS; sign-in sessions use secure, HTTP-only cookies. Administrative access is restricted. We do not expose viewer OAuth tokens to other users or to local stream/game plugins.

Sharing and public visibility

Your displayed channel name and picture, together with your site participation, can be visible to other visitors and on stream. Necessary hosting, database and security providers process information to operate the service; authorised staff may access records for support you request, security or abuse investigations, or legal obligations. Connected streamer tools receive only the display and interaction information needed to perform enabled features. We do not sell Google user data, share it with advertising platforms or data brokers, use it for targeted advertising, or use it to train general-purpose artificial-intelligence or machine-learning models.

Retention, refresh and deletion

We check YouTube authorization and refresh stored channel profiles approximately daily. Data that cannot be verified or refreshed is removed at a 29-day cutoff, before it becomes 30 days old; invalid or revoked authorization detected by these checks triggers removal of the associated stored YouTube connection data. Our automated deletion controls remove the selected provider identity, stored token, profile data and copied provider references from the active service. Database backup dumps expire within seven days, and deletion records are reapplied if a backup is restored. The separate retention rules for website transactions, moderation records and chat appear below.

To remove your stored YouTube data, sign in to the Soundboard account owning that connection, open Privacy controls, select Remove YouTube data and complete the confirmation. You can also use the provider-data deletion controls below. Other linked services and the website’s independent points ledger are retained; this does not delete your YouTube channel. To revoke Google authorization separately, use Google Account third-party connections. For access, correction, full Soundboard account deletion or help when sign-in is unavailable, use our privacy contact form; no login is required to send an enquiry.

Google API Services User Data Policy and Limited Use

OhItsDaneee Soundboard’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Google user data is used only for the disclosed, visible account and community features and their necessary operation and protection.

1. Information we process and where it comes from

Information may come directly from you, the selected platform/API, connected streamer tools, technical requests or other people reporting a concern. Do not include someone else’s private information unless necessary and lawful.

2. Google and YouTube

This service uses YouTube API Services. Google processes information under the Google Privacy Policy; YouTube use is subject to the YouTube Terms of Service.

Viewer sign-in uses Google OAuth and the read-only YouTube permission to identify the channel belonging to the signing-in user, retrieve its basic profile, recognise the configured owner where applicable and link it to a Soundboard account. Separately, public broadcast metadata is retrieved to identify the live video, show its title and provide an embedded player and links. This service does not upload, edit or delete YouTube videos, comments or playlists.

The short-lived Google access token is used in memory and is not saved in the Soundboard database. With your read-only consent, we store an encrypted Google refresh token on the server to check continued authorization and refresh your channel profile approximately daily. Tokens are never sent to other viewers or local stream tools. Sign-in credentials are not sold, used for advertising or passed to data brokers. Required deletion and Google revocation controls are explained below.

Read-only stream chat: the website displays messages from connected stream chats together. Website visitors cannot send messages to YouTube, Twitch or Kick through this feed. Normal YouTube sign-in requests read-only channel access; the site no longer offers the additional chat-send authorization. Earlier short-lived chat-send grants are removed from active site sessions when this change is applied. This does not revoke a grant in your Google Account; provider-wide revocation remains available through Google Connections. Historical duplicate-send fingerprints and delivery records expire within 24 hours under hourly cleanup.

3. Twitch

Twitch OAuth and API lookups supply the signing-in user’s basic identifier, display/login name and profile image. We use them to find or create your Soundboard account, link identities when requested, display participation, maintain points and apply permissions and anti-abuse checks. The viewer login does not request permission to manage your broadcasts, subscriptions, follows, channel or moderation settings, or to post chat as you. Its access token is used for lookup and is not saved in the Soundboard database.

Twitch’s own Twitch Privacy Notice and Twitch Terms of Service apply to Twitch. Manage the platform grant in Twitch Connections; remove data held here using our separate controls below.

Read-only stream chat: Twitch messages may appear in the combined feed. The website does not offer Twitch message sending or request its chat-send permission. Normal Twitch sign-in remains profile-only. Any earlier site-session chat-send grants have been removed; platform-wide authorization can be managed through Twitch Connections.

4. Kick

Kick login requests only user:read. We use the account identifier, name and profile image to recognise you and optionally link your Soundboard balance. If the response includes an email address, that sign-in email is not used or stored. Kick access and refresh tokens are not saved in the Soundboard database. Viewer sign-in does not request stream keys, chat posting, moderation or channel-management permissions.

Kick’s own Kick Privacy Policy and Kick Terms of Service apply to Kick. Manage its grant through Kick Connections; remove data held here using our controls below.

5. Why we use information and the legal bases

Where UK data-protection law applies, we rely on contractual necessity to provide the account, requested features and transactions you use; legitimate interests to operate a fair community, prevent abuse, secure the site, maintain proportionate records, moderate content and answer enquiries; and legal obligations where processing is required by law. Our legitimate interests are operating this community service and protecting its users and integrity, balanced against your rights.

Where a feature requires consent, you can decline or withdraw it; withdrawal does not affect earlier lawful processing. Platform OAuth permission is permission granted through the platform and is not a blanket consent to unrelated uses. We do not use viewer profiles for targeted advertising or make solely automated decisions with legal or similarly significant effects. Game settlement, limits and automated filters assist ordinary site operation; you can ask for review of a moderation or account decision.

Without the identity information needed for authentication and account features, you may browse public pages but cannot use functions requiring a linked account. A reply email and message are needed to handle a contact-form enquiry.

6. What others can see

Names, profile images, platform labels and participation may appear in public rankings, game rosters, results, winner announcements and stream interactions. Some game announcements and effect redemptions may also appear in stream chat or a broadcast. Do not post information you want to keep private in a public message or submission.

Private account controls show your own balance and connected identities. Other people may see transaction/transfer information needed for their own participation. Bingo cards are account-specific, and investigation choices may be hidden until the game’s reveal. Private reviewer notes and reports are limited to authorised users where the feature provides that restriction. Approved challenges and their titles may be public.

We cannot erase recordings or copies independently held by viewers or platforms. Contact the relevant provider for its own records; we can address material still under our control.

7. Twitch extensions and connected stream tools

The Soundboard and leaderboard Twitch extensions use the same accounts, points and participation records. Twitch supplies signed, short-lived extension authorization information such as channel, role, expiry and an opaque identifier. We verify it rather than storing the token in our database. If you choose to share your Twitch identity, the numeric identifier is used to find your points account, authenticate actions or highlight your ranking. Browsing public sounds/rankings does not require identity sharing; point-spending actions do. Manage sharing through Twitch’s extension controls.

The streamer’s local tools and game/overlay connections receive the commands, target names, request references and execution information needed to perform an enabled interaction, not your viewer sign-in tokens. Supported-game, readiness, monitor/capture, timing and execution/refund information may be reported back. The animation renderer does not collect the content of your keyboard input.

8. Hosting, email, sharing and international processing

Hosting, database, security and mail providers process information needed to operate the service. Selected platforms process their own sign-in, embed and chat requests under their policies. Contact submissions are sent from our server through authenticated Google Mail delivery to the operator’s private inbox. Authorised moderators see information needed for their role. Information may also be disclosed where required by law, to address infringement or to protect users and the service.

We do not sell personal data or share it for targeted advertising. Providers such as Twitch, Google/YouTube and Kick may process information internationally. Where we arrange an international transfer subject to applicable data-protection rules, the required transfer safeguards must apply. You can request information about the providers and applicable safeguards through the contact form; we do not claim that third-party processing remains solely in the UK.

9. Cookies, local storage and embedded players

The Soundboard uses an essential secure, HTTP-only session cookie for sign-in and request security, with a rolling expiry of up to 30 days. In the installed Studio app, successful owner verification can remember this Windows device for up to 90 days, renewed while used. Its session credential is protected for the current Windows user and is not sent to game plugins. Signing out, removing provider data or server-side revocation ends that session; expiry or revocation can require sign-in again. Your browser may retain preferences such as game sound settings, wager drafts, player position, favourites-related preferences and investigation notes. Investigation notes saved locally are not normally sent to the server unless you copy them into a message or another submitted feature. Clear browser site data to remove local copies; doing so does not delete server-side records.

When automatic YouTube expiry or revocation removes a connection, a keyed, non-public channel reference is kept solely to reconnect your existing local points account after you deliberately complete YouTube authorization again. This preserves your Soundboard balance without retaining the removed channel name, avatar or token. Manual provider-data deletion removes this recovery reference and does not automatically restore the deleted connection. Older YouTube connections whose grants were not stored must reconnect before continued authorized use.

Our own application does not use advertising trackers. Embedded Twitch/YouTube players or native chat may contact those providers, transmit technical information and use their own cookies or account sessions. Their controls and privacy policies apply. YouTube video embeds use its privacy-enhanced domain. External tips/payment pages are separate services; the Soundboard does not collect full payment-card details.

10. Retention and security

Linked profile information is stored to recognise the account until it is updated or the connection is removed. Participation and point-ledger records are retained while needed to operate balances, resolve disputes, investigate abuse and meet legal obligations. Provider-data deletion is separate from full Soundboard account deletion. We do not claim that removing a provider erases the site’s independent transaction ledger.

Ordinary arena/relayed-chat messages are shown for a recent five-minute window and cleaned from the active chat table after approximately 24 hours. Chat moderation-audit records are cleaned after approximately 30 days. A message copied into a report, transaction or broadcast may follow that record’s separate retention criteria. Security and correspondence records are kept as needed for the issue, dispute or legal obligation rather than indefinitely for unrelated purposes. Backup dumps expire within seven days, subject to the deletion safeguards below.

We use access controls, protected sessions and appropriate encryption/hashing for secrets. No system is completely secure. Please report a suspected security issue privately through the contact form and do not exploit it or access another person’s data.

11. Delete stored Twitch, YouTube or Kick data

Sign in to the soundboard account that owns the connection and open Privacy controls beside your account buttons, or choose a service below. Select the connection you want to remove, review the explanation and type DELETE TWITCH, DELETE YOUTUBE or DELETE KICK as shown. The server automatically removes that connection and copied profile data from the active service; this is not an email request waiting for manual processing.

Deletion removes the selected provider's identifier and profile image, copied profile references and relevant chat records. It also removes your active round participation and signs out the account’s sessions. Other provider links and the soundboard’s own points ledger are retained. If this is your only sign-in, you lose access to the remaining account and balance; link another service first if you want to keep access.

A keyed opt-out marker prevents automatic re-import from that service’s chat. Deliberately signing in with that service again creates a new connection and resumes collection; it does not automatically restore the deleted link. Deleting information here does not delete your Twitch, YouTube or Kick channel or content, or revoke the provider’s separate authorization grant.

Remove provider authorization separately through Twitch Connections, Google Account third-party connections, or Kick Connections. For complete soundboard account deletion, a failed deletion, access/correction requests or privacy questions, use the private contact form; never send passwords, access tokens or recovery codes.

The automated flow covers active-service data. Database backup dumps expire within seven days. A separate keyed deletion journal reapplies deletions before a restored database can serve the website. The journal does not store your profile name, image or readable provider identifier. Code-only backups are retained separately.

12. Revoking platform authorization

Google/YouTube users can open Google Account third-party connections, select this application and remove its connection/access. Twitch and Kick provide their own Connections settings linked above. Signing out, deleting data here and revoking a platform grant are different actions. For YouTube, the daily authorization check detects invalid or revoked grants and automatically removes the associated stored YouTube profile data and token, copied references, relevant chat records and sessions. Temporary Google errors are retried rather than treated as revocation. A 29-day expiry cutoff removes data that cannot be verified/refreshed, before it reaches 30 days; startup checks also apply after downtime or database restoration. Public YouTube chat profiles that have no OAuth grant are refreshed using the public Data API and the same age limit; a public lookup is never treated as proof of OAuth authorization. You can request immediate removal using our deletion controls. Twitch and Kick revocation does not currently trigger this Google-specific authorization checker; use our deletion controls or contact us for their stored data. A later platform sign-in may ask you to authorize a new connection.

13. Contact messages

The contact form asks for your reply email, an optional name/username, an enquiry category and message. It sends these privately to the operator’s inbox, with a reference and timestamp, to respond, investigate and keep a proportionate record. It does not publish the operator’s delivery address or your submission, does not accept attachments and does not subscribe you to marketing.

Our server and Google Mail process this correspondence. Messages and replies may remain in correspondence records while needed to resolve the enquiry, evidence our handling, deal with complaints or meet legal duties. The form does not create a public ticket or automatically delete mailbox correspondence after a fixed number of days. Please avoid passwords, security codes, full payment details and unnecessary sensitive information. Rate limits and a spam trap protect delivery.

14. Your rights, objections and complaints

Depending on applicable law and the processing involved, you may request access, correction, erasure, restriction or portability of your personal information. You may object to processing based on our legitimate interests. You may withdraw consent where we rely on it. Some rights have exceptions; we will explain any applicable reason for declining or limiting a request. You can make a request through Privacy and data rights without being signed in.

We may ask for proportionate information to verify ownership and protect other people, but never your password or two-factor codes. Requests are handled under applicable statutory timescales. You can complain to the UK Information Commissioner’s Office or another competent authority where you live. You do not have to contact us first to exercise a legal right to complain.

Cards, wallets and Fastlane

Our tip page can load PayPal’s secure checkout and hosted card fields, Google Pay and Apple Pay. These providers receive the technical information needed to assess eligibility, authenticate your chosen wallet/card and process the payment, including device/browser details, network address and payment data that you provide directly to them. Hosted card fields keep full card numbers and security codes outside our application. Wallet billing details are passed from the wallet to PayPal in your browser; we do not save them to the Soundboard database.

If you choose Fastlane, your email is sent directly from your browser to PayPal to look up your Fastlane profile. PayPal handles identity verification, hosted payment fields and any consent to save details. We do not use that email for marketing or store your Fastlane email, billing address, saved profile or one-time card token in the Soundboard. Any one-time payment token passes temporarily through our server solely to create your requested checkout. Availability depends on the provider, country and device. See PayPal’s Privacy Statement, Google Payments Privacy Notice and Apple Pay privacy information.

Tips and PayPal payments

Our optional tip page collects the amount you choose, an optional display name and message, your consent confirmation, and a checkout reference tied to your browser session. Display names and messages may appear in public stream alerts and chat. We use them to process your requested tip, confirm its status, prevent duplicate alerts, and answer payment enquiries. PayPal handles payment approval and financial details under its Privacy Statement. We do not store your PayPal password, full card details, payer email address or billing address in the Soundboard.

We retain transaction references, amounts, currency, payment status and dates for up to six years for payment reconciliation, accounting and dispute handling. We remove the display name, tip message, approval link and browser-session association from our active payment records after 30 days. Copies in the integration event log are also redacted after 30 days; independent platform chat and broadcast recordings follow their own retention. Expiring database backups may retain removed data for up to seven days. A tip does not itself create or link a platform account, award points, or affect game odds. Use the contact form for data enquiries.

15. Children and updates

The service is not directed at children under 13 or people below a higher applicable platform minimum age. Tell us if you believe a child’s information has been collected inappropriately so we can investigate and take the required action.

The latest policy and date appear here. Material processing changes may need additional notice or consent; publishing an update is not a substitute for legally required consent. Contact the operator through the contact page.