Privacy

What a list holds

The tracks you add, with the title, artist, cover, length and whatever else the source said. The stars, reactions and comments people give them. The list's title, date, venue and times. Who is on the list, with which role. All of it lives in one Postgres database at Neon, in Frankfurt.

The link is the list

A list's address is a long random key. Whoever has it gets what the owner set for the link: look, comment, edit, or nothing at all. Search engines are told to stay out, and the site sends no referrer from a list page, so the key doesn't travel on. Deleting a list deletes everything in it: tracks, stars, reactions and comments. No copy is kept.

Accounts

An account is an e-⁠mail address and whether it has been proven, by a sign-in link or by Google. A name is stored only when Google gives one or you type one on the account page. A session is a cookie and a row with its dates: no IP address, no browser details. Google learns that you signed in to setlist.DJ, and nothing about your lists. A passkey you add is kept as its public key and a counter, a name (the kind of device it was added on, such as Mac or iPhone), which password manager or security key holds it (the code its maker gives every copy of that product, shown as the passkey's name on Your lists; Apple sends none), how it talks to the browser (built in, USB, Bluetooth or NFC), whether it is synced or on one device, and when it was added. Touch ID, Face ID, Windows Hello or your phone check your fingerprint, face or PIN on the device itself: none of it reaches the site, which checks a signature. Remove a passkey on the account page and it is deleted here; delete it in your passwords settings too, or your device may still offer it. Right after you sign in by an e-⁠mail link, Google or an invitation, a cookie holding only "1" says so for ten minutes, so the site can offer a passkey once. Not now leaves a note in this browser's own storage (not a cookie, nothing about you, never sent to the site) so the offer doesn't come back here.

Guests

Press New list without signing in and this browser gets a guest account: a cookie and a placeholder address that is nobody's and is never mailed. It is what brings you back to your list from the same browser. Sign in, and the guest's lists move to your account. A guest account with nothing left on it is deleted 30 days later. One more cookie, holding only "1", says this browser has been here before, so the home page makes a list by itself only on a first visit; it lasts a year.

Mail

The site sends three kinds of mail: a sign-in link, to the address you typed; an invite, to the addresses someone who edits a list types on it, with its own link that holds 14 days; and a mention, to a person on the list whose name a comment names with @, with that comment in it. All go through Resend. An invited address stays with the list until the invite is taken up, withdrawn or the list is deleted; of the invitation's link only a hash is kept, and it goes once the invite is taken up. Accepting an invitation for an address without an account makes one, as a sign-in link does. Feedback you send goes, also through Resend, to the person who runs the site, and to nobody else. Nothing else is sent, and no address is passed on.

Feedback

The feedback form keeps what you write, the quick verdict if you chose one, the address you left for an answer, if any, and your account if you were signed in. It is there so the person who builds the site can read it and write back; a copy goes to them by mail. It is deleted after 24 months at the latest, sooner if you ask.

Spotify, YouTube, SoundCloud and rekordbox

Paste a link and the site asks Spotify, YouTube or SoundCloud for the track's details; the link is all they get from us. A track from a Spotify playlist keeps the name Spotify shows for whoever added it to the playlist, so the list can say who picked what; an editor may say who that is on the list, for that list only. For a track's energy, danceability, mood, tempo and key the site asks Soundcharts with the track's Spotify id or ISRC (or, for a track with neither, its title and artist), and FreqBlog, for what Soundcharts does not know, with its ISRC or its title and artist: a track identifier or its name, nothing about you. A player loads only after a tap on the track, and then it is the source's player, with the source's own cookies; YouTube's is told the site's name (setlist.dj, never the list's address), which it needs to play. A rekordbox export is read in your browser; only the tracks you pick are sent to the list, never the file.

Visits and bots

Vercel hosts the site, in Frankfurt, and keeps its server logs for a short while. Vercel's Web Analytics counts visits without cookies and without a profile: a page, a country, a browser family, nothing that follows you around. Its Speed Insights times how fast pages load in your browser, the same way: no cookies, no profile. BotID checks the forms, so a script can't ask for a thousand sign-in links; it looks at how a request is made, not at who makes it.

How long

A list stays until its owner deletes it, or until the owner's account is deleted, so a link keeps working for as long as you have it. The one exception is a list nobody did anything with: an empty one goes when you leave it, or after a day. A guest account goes 30 days after it has nothing left. Feedback goes after 24 months. A sign-in link works once and stops after 15 minutes.

Who else sees what

Vercel (hosting, visit counts, the bot check), Neon (the database), Resend (mail) and Google (sign-in, when you choose it) process data on our behalf, each under its own terms. The site and its database are in Frankfurt. Spotify, YouTube and SoundCloud see the links you paste; Soundcharts sees a track's Spotify id or ISRC (or its title and artist), FreqBlog a track's ISRC or its title and artist, and nothing else. That is the whole list. Nothing is sold, shared or swapped.

The person who runs the site

Whoever runs the site can see, on its admin pages, who is on which list, what each person did there (the same lines a list's history shows, and who gave which stars, reactions and comments), and the addresses of accounts and of open invites. It is there to run the site and to fix what goes wrong, and it goes no further: it is not mailed, exported or passed on, and the logs never hold an address. From there they can also open any list, one closed to its link too, and read what is on it, comments included; opening it that way leaves no name on it.

Your rights

What is stored about you is on your lists and on your account page, plus any feedback you sent; there is nothing behind them. You can delete a list you own, and leave one you don't. To have your account and every list it owns deleted, write to us: it is done by hand, within a few days, and it is final.

Questions about this, or a request to delete your account: hello@setlist.dj