Privacy Policy

1. What we collect

Account details. Your email address, a display name, and how you sign in — a password hash, a passkey, or a link to your Google account if you chose that. We never see your Google password.

Which terms you accepted. The version of the terms you agreed to and when. Keeping this is the point of asking.

What you listen to and save. This is the part worth being explicit about, because it is easy to think of it as product behaviour rather than data collection. It is personal data:

• Play history — which tracks you played and when.
• Your library — the tracks, albums, artists, and playlists you save, and playlists you create.

These are tied to your account, not anonymous. They exist to make the player work — history, resuming, and your saved music.

If you are an artist here. Your artist profile, bio, images, links, and the music you provide.

Technical basics. Ordinary server logs — IP address, timestamps, and what was requested — kept for security and debugging. We do not run third-party advertising or analytics trackers.

2. Why we can hold it

Account details and terms acceptance: to provide the service you asked for, and to keep a record of an agreement. Play history and library: to provide features you are actively using. Server logs: our legitimate interest in keeping the platform secure and working.

We do not sell your personal information, and we do not share it with advertisers.

3. Who else can see it

The platform runs on infrastructure we operate, using service providers for hosting, file storage, and sending email. They process data on our instructions in order to run the service.

Some things are public by design: an artist profile, and playlists you choose to make public. Your play history and your saved library are not public.

4. How long we keep it

Account data lasts as long as your account. Play history accumulates while you use the player. Logs are short-lived.

When you ask us to delete your account, we remove your personal data: your sign-in details, your saved library, and the playlists you created.

Three things behave differently, and it is fairer to say so than to leave you to discover them:

• Records that an invite code was used survive with your identity removed, so the invite is not silently handed back out.
• Your play history is kept but detached from you — the rows remain, with no link to your account.
• Music published under an artist stays up. Deleting your account removes your access to that artist, not the music itself; taking a release down is a separate request.

One consequence worth knowing before you ask: deleting your account also deletes playlists you created, including for anyone else who had saved them. If you have shared a playlist, tell us and we will talk about it first.

5. Your rights

You can ask us to show you what we hold, correct it, delete it, or send you a copy. If you are in the UK or EEA you have these rights under the GDPR; if you are in California, under the CCPA. Either way, ask and we will do it — during the alpha this is handled by a human reading email rather than a self-service button, and we will confirm when it is done.

Email [email protected].

6. Cookies

We set a cookie to keep you signed in, and store some preferences (theme, volume, your queue) in your browser. No advertising or cross-site tracking cookies.

7. Changes

If this changes substantively we will publish a new version and ask you to accept it, the same way as the terms.