← Back to EBBLESS

Privacy Policy

Last updated 2026-11-10. EBBLESS is in open beta, so this will change. Written from what the app's code actually does, not from a template.

The short version.

1. Who runs EBBLESS

EBBLESS is run by MAL GRIOT. To reach us about privacy, use Settings → Send feedback in the app, or open an issue at github.com/MalGriot/EBBLESS.

Needs a decision before public release: the legal name of the operator, a postal address or dedicated privacy email, and the country the operator is legally based in. None of these are stated here because they are not in the code.

2. What is stored on your device

EBBLESS keeps this in your browser or app storage (localStorage, plus a cache for the app files). It stays there until you clear it, clear site data, or uninstall.

3. Accounts and sign-in

Google sign-in is optional. When you use it, our server verifies your Google token and gets your Google account ID and email address. It creates an EBBLESS login session (stored on your device; the server keeps only a hash of it, for up to 90 days of inactivity). Your email is shown in Settings and stored with your cloud profile.

The beta community is optional: you don't need it to use EBBLESS. If you join, we collect your name or nickname, email, and your answers to the sign-up questions (such as a playlist link and music taste), plus your browser's user-agent string. These go to a Google Sheet that the operator uses to run feedback rounds and send tester links. Testers are identified by a tester token.

Feedback and bug reports you send include what you type and technical details (device, operating system, browser, screen size, and for wrong-song reports, the song and the match that played). They go to the same Sheet or to our server's report storage.

4. What is stored on our server

DataWhenNotes
Cloud profile: library, playlists and tracks, Liked Songs, pins, settings, thumbs-downs, listening recap log, and a short "now playing" summary per device (queue, position) for handoffOnly if you sign in with GoogleKeyed to your Google account ID, stored with your email. This includes the Personalized listening setting. Deleted removals are remembered for 180 days so they sync.
Login sessionOnly if you sign inHash of the session token. Expires after 90 days unused.
Beta tester record and analyticsIf you joined the betaIn the operator's Google Sheet. See section 6.
Wrong-song and link reports, feedbackOnly when you send oneSong details and what you wrote.
Shared tag poolUnless you turn off Personalized listeningAnonymous. See section 5.

Not synced and never stored by us: your taste data, genre-link table, play history, recent-plays list, device-local caches, and playback position. They exist only on the device that learned them.

5. Listening and personalization

EBBLESS learns from what you do: songs you play, finish, skip early, like, or thumbs-down. It uses this to rank Discover and CuRRentSSsss picks and to avoid repeating songs you just heard. Specifically it builds, on your device:

To look up genre tags, the title and artist of songs you play are sent to our server, which asks Last.fm and similar sources.

The shared tag pool. When you finish, like or skip a song, EBBLESS sends our server a short list of that song's genre tags (up to 8) and a small positive or negative weight. The server adds this to anonymous counters of which tags pair well. No account ID, device ID or song name is sent with it, and none is stored by us. The stored counters carry no identifier, so we cannot find or delete your individual contribution later. EBBLESS also reads the pool to give new listeners a starting point.

Your control: Personalized listening

In Settings → Privacy & data, the "Personalized listening" switch is on by default. When you turn it off:

The setting is saved on your device and, if you sign in, follows your account to your other devices.

Turning it off does not stop the play history list you can see in the app, the listening recap log, or per-playlist play counts. Those are your own records, not taste learning. See section 8 for how to clear them.

Your control: Reset listening profile

The same section has "Reset listening profile". It erases the taste data, genre links, thumbs-downs, genre tag cache and recent-plays seed list on that device. It does not delete playlists, Liked Songs or the library. Thumbs-downs are removed from your cloud profile at the next sync. Other devices keep their own taste data until you reset them too.

5a. Voice requests

You can speak to EBBLESS with the microphone button. What happens depends on what you say.

5b. Pictures as a vibe

On Home you can tap the camera button (or paste or drop a picture on a computer) to get songs that match a photo or movie still. Only the picture you choose is sent.

6. Analytics and tracking

7. Other services

EBBLESS plays music and fetches information from other companies. They receive requests (at least your IP address and the thing requested) and have their own privacy policies. Some requests go through our server, which then asks them; the rest go straight from your device.

ServiceWhat for
YouTube / GoogleSongs play through YouTube's embedded player and YouTube searches. YouTube and Google can see your IP address and may set their own cookies or identifiers, as with any YouTube embed. By using playback you are also using YouTube's service; see Google's Privacy Policy and the YouTube Terms of Service.
Google Sign-InOptional account sign-in.
Spotify, Apple Music / iTunes, SoundCloudReading the public playlists, albums and songs you paste, and track details and previews. Spotify login (optional) can read your library and playlists with your consent. SoundCloud playback uses its embedded widget.
Last.fm, MusicBrainz, ListenBrainz, Wikidata, Cover Art Archive, Deezer, ReccoBeats, GetSongBPMGenre tags, similar songs, artist info, art, and audio features. Song and artist names are sent. Last.fm usernames are sent if you import from Last.fm.
LRCLIBLyrics, by title and artist.
SponsorBlockSkip times. Sends only the first 4 characters of a hash of the video ID.
CloudflareRuns our server. Sees requests as described above.
GitHub Pages, jsDelivrHost the app files and a captions library.
Legal review needed: whether these services' terms (especially YouTube API Services and Spotify's developer terms) require specific consent text or placement for EBBLESS, and whether pasting a third-party playlist requires any notice to that playlist's owner.

8. Keeping, deleting and your rights

There is no automatic retention schedule beyond the 90-day session expiry and the 180-day removal memory.

9. Children

EBBLESS is not designed for children and has no age check.

Legal review needed: the minimum age and whether the app needs an age gate for the countries and app stores it targets.

10. Changes

If a data practice changes, this page and the "last updated" date change with it, and the in-app Settings description is updated at the same time.