TuneHive privacy policy

Last updated: August 2, 2026

TuneHive collects only the information needed to create shared listening rooms, synchronize playback, manage a shared queue, and moderate participants. This policy applies to the TuneHive Chrome extension, public room directory, and configured TuneHive service.

Information TuneHive processes

• a random anonymous TuneHive user identifier generated by the extension;
• the display name chosen by the user;
• room settings, membership, roles, moderation actions, bans, and queue state;
• track presentation metadata submitted to a room, including the YouTube video ID, title, artist, album, artwork URL, duration, and queue timestamps;
• operational metadata needed for security and reliability, such as connection presence, rate-limit counters, request or socket identifiers, safe error codes, and server timestamps.

Public-room names, descriptions, participant counts, playback mode, current-track title and artist, and creation time may be shown in the public directory when the room owner enables public listing. Display names and queue contents are visible to people in the same room.

Information TuneHive does not collect

TuneHive does not collect Google passwords, Google cookies, Google OAuth tokens, YouTube credentials, private Google account identity, audio, video, browsing history, payment data, or the contents of unrelated websites. It does not download media or bypass access controls. Each participant plays content through their own independently authenticated YouTube Music session.

How information is used

The information above is used only for anonymous session continuity, room membership, moderation, shared queues, synchronized playback, optional public-room discovery, abuse prevention, deletion requests, and service diagnosis. TuneHive does not sell user data or use it for advertising or credit decisions.

Storage and retention

• The extension stores the anonymous identity and signed TuneHive session locally.
• Signed room-session tokens expire after 30 days.
• Connection presence and rate-limit state expire after their short control window.
• Empty temporary rooms expire after the service's configured room lifetime.
• Ended-room, queue, moderation, and audit records remain until removed by the service's configured retention process or a valid deletion request.
• Server logs redact authorization, password, and session-token fields.

Deletion

An authenticated user may request deletion from the configured TuneHive service using DELETE /api/me/{anonymousUserId} with their TuneHive session token. This removes that user's participant records, queued tracks, bans, and linked audit actor data. Clearing Chrome extension storage removes local data but does not by itself delete server records. The service operator and support contact identified on the Chrome Web Store listing can assist with a deletion request.

Sharing and service providers

TuneHive sends room data to the configured TuneHive service, the participants in the same room, and the optional public directory as described above. The service operator may use infrastructure providers for hosting, databases, logging, backups, and monitoring and is responsible for identifying those providers in its public service information.

The optional “Buy me a coffee” link opens a payment page operated by Revolut. TuneHive does not collect, store, or transmit card numbers, bank credentials, or other payment credentials. Revolut processes the transaction under its own terms and privacy notice. The payment recipient may receive the transaction details that Revolut normally provides to a recipient, such as the sender name, amount, and payment reference.

Chrome Web Store Limited Use

TuneHive's use and transfer of information received from Chrome APIs and YouTube Music page content is limited to providing and improving its disclosed single purpose: shared listening rooms with synchronized playback and queues. TuneHive complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.

Security and independence

Production connections use HTTPS and secure WebSockets. Sensitive authorization fields are redacted from application logs. TuneHive is independent software and is not affiliated with, endorsed by, or sponsored by Google or YouTube.