This privacy policy describes how One Happy Jukebox (“the Service,” “we,” “us”) handles information when you use the website at happyjukebox.com, related branded domains, the phone connector client, and the One Happy Jukebox Host Chrome extension.
This does not apply to guests. People who join a jukebox by scanning a QR code on their phone use the jukebox client only. They are not asked to sign in with OAuth, and we do not collect their email addresses at all. Google Account sign-in and YouTube playlist access apply only to the person operating the host computer with the Chrome extension.
Google user data we access
When a host signs in with Google, we request only the Google permissions needed to run the Service. From Google, we access and may process:
Email address
Google Account unique user identifier (the OpenID “subject” / OAuth user ID returned by Google sign-in)
Display name from the Google profile (shown in the extension account UI on the host)
YouTube playlist metadata (playlist IDs and titles) for the signed-in Google Account, requested only on demand when the idle-playlist dropdown is opened in the admin settings
Video items inside a selected idle playlist (video IDs and related titles/thumbnails needed for playback), requested only for the playlist the host chooses as the idle playlist—not for any other playlist
We do not request or use other Google user data that Google could share under broader permissions (for example Gmail, Drive, Calendar, Contacts, Photos, or write access to YouTube). We do not sell Google user data, use it for advertising, credit, lending, or AI model training, or transfer it for those purposes.
How we use Google user data
Sign-in and subscription status
We use your email address and Google Account unique user identifier solely to identify your host account and look up your subscription status (for example paid unlimited plan or free tier) so the extension can apply the correct plan limits and features. This lookup happens when you sign in and may refresh while you remain signed in.
Your display name and email may be shown in the extension’s account menu on the host computer while you are signed in.
YouTube idle playlists
With your permission (youtube.readonly), the host extension can read YouTube playlist information for the Google Account you used to sign in, for one purpose: choosing and playing an idle playlist when no guest has a video queued.
Playlist list (IDs and names): Requested from YouTube only when someone opens the idle-playlist dropdown in admin settings. That list is held temporarily in the host extension’s memory for that session so you can pick a playlist. We do not save the IDs or names of playlists you have not selected on the host or on any guest/client device, and we do not upload that list to our servers.
Selected playlist only: If you choose a playlist as the idle playlist, that playlist’s ID and title are stored locally on the host computer (in the Chrome extension’s storage) as a jukebox setting so idle playback can resume after restart.
Videos in the selected playlist: We access the list of videos in a playlist only if that playlist is selected as the idle playlist. We use those video IDs (and related display metadata such as title/thumbnail) on the host computer to play filler tracks when the guest queue is empty—either on the host’s YouTube playback tab or via Cast to a TV/display. A short-lived local cache of those video items may be kept on the host (on the order of about one hour) to avoid re-fetching while idle playback is active. We do not access video lists for playlists that are not selected as the idle playlist.
Admin visibility on the data channel: The selected idle playlist’s ID and title (as part of host settings) can be transmitted over the direct peer-to-peer data channel between the host and any guest who is signed into that jukebox session as an administrator, so admins can view or change settings. That information is not saved on guest/client devices as a lasting copy of your YouTube library, and unselected playlists are not sent.
Sharing, transfer, and disclosure of Google user data
The Service's use and transfer to any other app of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
We share or disclose Google user data only as follows:
Subscription status service / cloud infrastructure provider: Your email address and Google Account unique user identifier are sent to our subscription status service, which runs on our cloud infrastructure provider, solely to look up and maintain your subscription tier and related host identifiers needed for the Service (such as a short join key for QR links). We do not share this data with that provider for advertising, analytics products unrelated to running the Service, or resale.
Host computer: Sign-in state, OAuth access tokens used to call YouTube on your behalf, selected idle playlist ID/title, and temporary playlist/video caches are stored or processed locally in the Chrome extension on the host PC.
Jukebox administrators (peer-to-peer): As described above, the selected idle playlist ID and title may be shared with admins of that jukebox session over the direct data channel. We do not send your Google email, Google Account ID, or OAuth access token to guests.
Google: Sign-in and YouTube API requests are made to Google under your authorization; Google’s handling of those requests is governed by Google’s policies.
We do not sell Google user data. We do not transfer or disclose Google user data to third parties for advertising, data brokerage, credit-worthiness, lending, or other purposes unrelated to providing or improving the Service’s user-facing features.
Except for the limited subscription records described above, guest song queues and display names are transmitted peer-to-peer to the host for the current session. That information is not uploaded to a separate cloud service operated by us for the purpose of building user profiles.
Data protection
We take reasonable and appropriate steps to protect Google user data against unauthorized access, use, alteration, or disclosure, including:
Encryption in transit: Sign-in, subscription lookups, and YouTube API calls use HTTPS/TLS.
Limited scope: We request only the Google OAuth scopes needed (identity/email/profile and YouTube read-only for idle playlists).
Access control: OAuth access tokens and host sign-in state are kept in the Chrome extension’s local storage on the host computer and are not sent to guest clients. Subscription lookups require our server-side credentials and are limited to status checks for the signed-in host.
Minimization: Full playlist catalogs are fetched on demand and not persisted server-side; only the selected idle playlist ID/title is kept as a host setting. Playlist video lists for idle playback are cached briefly on the host only.
Sign-out: Signing out of the extension clears locally stored Google access tokens and signed-in account state on that host.
Retention and deletion of Google user data
We retain Google user data only as long as needed for the purposes in this policy, unless a longer period is required or permitted by law:
On the host computer: Google sign-in profile fields, OAuth access tokens, and related local settings remain while you stay signed in (or until tokens expire and are refreshed). Signing out or uninstalling the extension removes local sign-in data and Google access tokens from that browser profile. Selected idle playlist ID/title remain in host settings until you change or clear them, sign out/reset settings, or remove the extension data. Temporary idle-playlist video caches expire on the order of about one hour or when replaced.
Subscription status service: We retain the minimal host account record needed to look up subscription status (Google Account unique user identifier, email, plan tier, and related Service identifiers such as a join key). We keep that record while your account may use the Service, or until you ask us to delete it.
Unselected playlists: Playlist IDs/names that you never select are not retained on our servers and are not kept as lasting host settings.
How to request deletion: Email info@happyjukebox.com from the Google account email you used to sign in (or include that email in the message) and ask us to delete your Google-related account data. We will delete or destroy subscription-service records associated with that account that we no longer need to provide the Service, and we will confirm when the request is completed. You should also sign out of the extension on any host PC you control and, if desired, revoke the app’s access in your Google Account permissions. When a retention period ends for a given type of data, we delete or destroy it.
Other information (non-Google guests and general operation)
What guests store locally
Preferences such as display name, language, UI cache, and connection details for the phone connector are kept on the guest’s own device (for example in browser storage) unless they clear them.
What is transmitted in a session
When you join a jukebox session, song choices, queue updates, display name, and related session messages are sent directly to the host over peer-to-peer networking between your device and the host. That traffic is for running the current session. It is not uploaded to a separate cloud service operated by us for the purpose of building user profiles.
Favorites
If you choose to save videos as Favorites in the jukebox client, those favorites (such as video IDs and titles you star for quick access later) are stored only on your own device—for example in your browser’s local storage. We do not upload your favorites list to our servers, and favorites are not required to use the Service. You can remove favorites in the client or clear them by clearing that browser storage.
Search queries on the jukebox host
When guests search for songs, the text of a search query may be saved for up to one week in the host’s browser storage to speed repeat searches and reduce API usage. Those cached terms are not associated with the guest’s display name.
YouTube pages on the host (extension)
Separately from the YouTube Data API playlist calls described above, the host extension may read data from YouTube pages open in the host browser—for example, to support queue management or playback. That processing happens on the host computer. We do not store that page data on our servers or transmit it to our servers; it is processed locally by the extension and discarded when no longer needed for operation.
Cookies and similar technologies
The Service or the site that serves the client may use cookies or similar browser storage technologies where needed for basic operation, security, or preferences. You can control cookies through your browser settings.
Third-party services
Searching for and playing videos involves Google/YouTube and may involve other third-party services. Those services have their own privacy policies. We do not control third-party data practices beyond the disclosures in this policy about how we use Google APIs and OAuth.
Children
The Service is intended for personal / home / private gathering use under the supervision of the jukebox operator. We do not knowingly collect personal information from children through a dedicated registration process for guests, because guests are not required to register with us.
Changes
We may update this policy from time to time. The “Last updated” date at the top of this page will change when we do. If we change how we use Google user data in a material way, we will update this policy and, where required, obtain appropriate consent before using Google user data in a new way.
Contact
Questions about this policy, or requests to delete Google-related account data, may be sent to info@happyjukebox.com.