Last updated: June 15, 2026
ListenTogether lets people listen to YouTube Music together in real time through its website, browser extension, and Android app. The service is operated by its individual developer (referred to as "we", "us", or "our" in this document). You can reach us at the contact details listed at the end of this policy.
The table below describes the data ListenTogether handles, which product surfaces use it, why it is needed, where it is stored, and how long it is retained.
| Data | Domain | Purpose | Stored where | Retention |
|---|---|---|---|---|
| Required | ||||
|
Anonymous nickname e.g. "BoldFox" |
Extension, Mobile app | Identify you in a room without requiring an account. | Local app/extension storage + active room state | Until cleared locally; active room copy deleted when the room ends |
| Room code | Website, Extension, Mobile app | Join and route messages to the right room. | Backend active room state; local storage when needed for reconnect/join flow | Deleted when the room ends; local copy until cleared by app/browser storage |
|
Playback events play, pause, seek, track change |
Extension, Mobile app | Keep participants synchronized in real time. | Transient WebSocket relay / active room state | Not persisted beyond the active room |
|
Queue entries track title, artist, YouTube Music URL |
Extension, Mobile app | Show and synchronize the shared queue. | Backend active room state | Deleted when the room ends |
| Optional | ||||
|
Preferences theme, language, remote mode, notifications |
Extension, Mobile app | Remember settings such as theme, language, remote mode, notifications, analytics choice, and similar UI preferences. | Local app/extension storage; account-backed sync where enabled | Until changed, deleted, app/browser storage is cleared, or account is deleted |
| Email from Google account | Website, Mobile app | Create an account, operate login/session features, send required system emails, and send optional marketing/product emails when enabled. | Backend database; local app session cache | Until account deletion; local cache until sign-out/app data clear |
| Customized nickname | Website, Extension, Mobile app | Replace the anonymous nickname and synchronize it across signed-in surfaces. | Backend database; local app/extension cache | Until changed or account deletion; local cache until cleared |
| YouTube read access | Mobile app | Retrieve liked songs and playlists after explicit consent. | Google access token stored locally on device; fetched YouTube data may be cached briefly by backend | Token expires/refreshes; backend cache expires automatically |
| YouTube write access | Mobile app | Like a song or save one into a playlist, only after explicit consent for that action/capability. | Google access token stored locally on device; write request sent through backend when the feature is available | Token expires/refreshes; action persists in your YouTube account until changed there |
Optional Google and YouTube permissions are requested only when you choose to use the related feature. You can use ListenTogether rooms without connecting a Google or YouTube account. YouTube write access is not requested for future-proofing; it is requested only when a visible write feature is available and you choose to use it.
We do not collect your Google password or YouTube password; payment card details; device identifiers or hardware fingerprints; precise location data; or data from browser pages other than YouTube Music tabs where the extension is active. We do not collect your broader YouTube Music listening history beyond the room, playlist, liked-song, or write actions you explicitly choose to use.
The ListenTogether website uses Umami Analytics, a privacy-focused analytics platform. Umami does not use cookies, does not track users across sites, and records only aggregate page-view statistics. The extension also uses Umami Analytics for anonymous usage events (see section 11). The extension communicates with the ListenTogether backend server and the Umami cloud endpoint, and interacts with YouTube Music (music.youtube.com) to read playback state from the page. Google Sign-In and YouTube account access are optional features used only after you choose to connect them.
We do not sell, rent, or trade your data. The sharing that occurs between participants within the same room is limited to room functionality: your nickname, playback events, and queue entries are relayed to other people in the same room in real time. Optional account, email, and YouTube data are not shared with other room participants unless the feature itself requires visible room sharing, such as adding a track to the shared queue. We may share data if required by law, but we will notify you where legally permitted before doing so.
Communication between ListenTogether clients and the backend uses encrypted connections (TLS/HTTPS and WSS). Account data is stored in the backend database, and Google/YouTube access tokens used by the Android app are stored locally on your device. We limit access to Google user data to the features described in this policy.
You can clear local extension or app preferences through your browser or device settings, sign out to clear local session data, and delete your ListenTogether account where account features are available. If you are a resident of the European Economic Area (EEA), the United Kingdom, or California, you may have additional rights under GDPR, UK GDPR, or CCPA respectively, including rights to access, correct, or delete personal data.
ListenTogether is not directed at children under the age of 13. We do not knowingly collect any information from children. If you believe a child has used the service, please contact us and we will take appropriate steps.
We may update this policy when ListenTogether gains new features that affect data handling. The "Last updated" date at the top of the page will reflect any changes. Continued use of the service after a policy update constitutes acceptance of the revised terms.
Questions or concerns about this policy? Reach out via:
ListenTogether collects anonymous usage events to improve the product. By default, the extension records session-level signals such as room creation, playback sync quality, button interactions, and time spent using the extension. These events are not linked to any persistent identifier and cannot be used to track you across sessions. Optionally, you may consent to enhanced analytics during the onboarding flow or in the extension settings. This generates a random anonymous UUID stored locally on your device, allowing us to measure returning users, feature adoption over time, and community growth. This identifier is never linked to your identity, email, or browsing history. You can revoke this consent at any time in the extension settings, which stops the identifier from being used. All analytics data is processed by Umami, a privacy-focused analytics platform that does not use cookies and does not track users across websites. This data is never sold or shared with advertisers.