In short: Music is played locally on each user's own device through their own YouTube Music. The Service does not collect, store, or transmit any audio data — it only syncs "playback state" (track identifier / playback position / play-pause flag + timestamp).
| Item | Description |
|---|---|
| Account email | Login identifier. |
| Password hash | We never store your plaintext password — only a one-way hash. |
| Nickname | The name shown in rooms, chat, and friend lists. |
| Friend / follow relationships | Friend (nickname-based) and one-way follow connections, used to deliver icon badge alerts. |
| Room / chat messages | Room data, shared queue, and in-room chat used for real-time synced listening. Chat and room state are ephemeral and are deleted when the session or room ends (they are not retained permanently). |
| Playback state | Current track identifier, playback position, play/pause flag, and sync timestamp — used for drift correction. The audio itself is not included. |
| UI language setting | Your selection among en / ko / ja. |
| Room hearts (likes) | Used for sorting and browsing public rooms. |
| Billing identifiers | For Pro subscriptions, a Stripe Customer ID / Subscription ID. We never store full card numbers. |
What we do not collect: audio / music data, browsing history, contacts, location data, or content from other sites.
Music playback happens entirely locally on the user's own device and through the user's own YouTube Music account. The Service does not stream or redistribute any audio; the server only exchanges the "playback state" metadata described in section 1 above. Therefore, audio content is never collected, stored, or transmitted in any form. This is a design principle intended to avoid copyright and bandwidth burdens.
Apart from the services above, we do not sell or share personal data for advertising purposes.
You may request access to, correction of, deletion of, or suspension of processing of your personal data. Deleting your account is the fastest way to erase your data; for any other request, contact us at the address in section 9.
We use HTTPS-only communication, one-way hashing of passwords, and session-token-based authentication. The security scope of payment card data is handled by Stripe.
This Service is not directed to users under the age of 16.
For privacy inquiries and data access or deletion requests: hello@hummo.app