How we handle data

Last updated August 23, 2026. This notice describes the current Singroom product in clear, practical language.

Queue and room data

The main controller stores the queue, song history and current song in browser local storage. To synchronize phones with the controller, room state, video links, titles, thumbnails, playback state, control commands, a random room code and update times are stored in our server database.

A room does not require an account or real name. Anyone with the same room URL or code may be able to access and control it, so do not place private or sensitive information in song titles, links or room data.

Google Analytics

We use Google Analytics 4 to understand visits, page views, average engagement time, general device and browser categories, approximate region, and product events such as adding a song, opening the player, entering fullscreen and skipping. Google Analytics may use first-party cookies or similar identifiers to distinguish anonymous browser instances.

Analytics page addresses contain only the origin and path. Singroom deliberately removes URL query parameters, so room codes are not sent to Google Analytics as part of the page URL.

Third-party content

When you open or play YouTube or Bilibili content, your browser connects directly to those services. They may receive network, device, cookie or playback information under their own privacy policies.

Information we do not request

Singroom currently requires no account and does not ask for your name, email address or payment details. The application does not record your microphone or singing.

Managing local data

Use “Clear queue” and “Clear history,” or clear browser site data, to remove locally stored records. Closing a room does not automatically delete room state already synchronized to the server.

Changes

We will update this page and its date when product behavior or data handling changes materially. This notice describes the product and is not legal advice.