Jukebox / Privacy policy
Privacy policy
Last updated 14 October 2026
In short: Jukebox keeps what it needs to give you the same music on every device: your account, your library, and your music-service sign-ins, the last stored encrypted with your password. There are no ads, no analytics and no trackers, and nothing is sold or shared for marketing.
Who we are
Jukebox is made and run by Marobotic (Maro), at marobotic.dev. "We" below means Marobotic. To ask anything about your data, or to have it deleted, use the contact form.
What we store and why
| What | Why | How long |
|---|---|---|
| Your email address and password. The password is never stored, only a one-way scrypt hash of it. | To sign you in, and to email you a reset link if you forget the password. | Until you delete your account. |
| Sign-in sessions: a random token for each device you sign in on. | To keep you signed in. | Until you sign out, or 90 days without use. |
| Your sign-ins to Spotify, YouTube Music (Google) and SoundCloud, when you connect them. | So every device can use your services after you connect them once. They are stored only in encrypted form, locked with a key made from your password, so the server cannot read them on its own. On your devices that key is kept in the system's own protected store (for example Windows' DPAPI). | Until you sign out of that service in Jukebox, or delete your account. |
| Your library: playlists, liked songs, recently played, your queue, and your devices' names. | So the same library and the same player are on every device. | Until you delete them or your account. Saved playlists stay after you sign out of a service, by design. |
| What is playing now and on which of your devices, and commands sent between your devices. | To let one device play, pause or skip on another. | Short-lived: replaced as you play. |
| Server logs: your IP address, the time, and the address requested. | To keep the service running and to stop abuse. | 14 days. |
The shared music cache
When a song is played, the server keeps a copy of its audio, its cover, its title and artist, and its lyrics, so that the next play of that song, by you or anyone else, starts instantly. The cache records when a song was last played, not who played it. Songs that are not played are removed after 30 days, and the oldest are removed when the cache is full.
Services we talk to
- Spotify, Google (YouTube Music) and SoundCloud, when you connect them or play from them. What they do with your data is covered by their own privacy policies.
- Cover and song lookups. To find a song's cover and its match on another service, the server asks YouTube Music, Spotify and SoundCloud about the song (its title, artist or id). These requests do not include who you are.
- Discord, only if you run the Windows app with Discord open: the app tells Discord, on your own computer, what you are listening to, so it shows on your profile.
- Email delivery: password-reset emails are sent through an email delivery service.
- Hosting: the server runs on DigitalOcean, behind Cloudflare.
What we never do
- No ads, no analytics, no tracking cookies, no fingerprinting.
- We do not sell your data or share it for marketing.
- We do not read your music-service sign-ins; they are stored encrypted.
In your browser
The web player keeps your sign-in token and a few settings (like the volume) in your browser's local storage, so you stay signed in. Signing out removes them. It sets no cookies.
Your choices
- Sign out of a music service in Jukebox's settings: its stored sign-in is deleted.
- Ask for a copy of your data, or for your account and everything in it to be deleted, through the contact form. We reply within a few days.
Children
Jukebox is not meant for children under 13, and we do not knowingly keep their data.
Changes
If this policy changes, the new version is posted here with a new date.