SingSpree

Privacy Policy

Last updated: 19 October 2026

1. Controller

SingSpree is operated by Jan Beckschewe (see Contact). References to "we", "us", or "our" refer to the operator of this website.

2. What data we collect

SingSpree is designed to collect as little personal data as possible. Account registration is optional – you can sing without one – and we do not use analytics or tracking scripts.

  • Accounts (optional): If you create an account we store your e-mail address (verified with a one-time code and used only to sign you in – no newsletters), the display name you choose, the public key of each passkey you register and/or a salted hash of an optional password (never the password itself), the dates you created and last used the account, your sign-in sessions, and the profile picture you may add. A picture is cropped and shrunk in your browser and stored only as our own re-encoded 256 × 256 pixel copy, without the metadata of the original file (such as location or camera details); it is shown next to your display name on your profile, to your friends and to everyone in the parties you join, until you remove or replace it on your profile page. Administrators can remove a picture that breaks the rules. Sign-in codes are delivered by our e-mail provider Resend (Resend, Inc., USA), which processes your address and the message for that purpose only. Other signed-in users can find you by your exact e-mail address, which shows them your display name but never the address. You can delete your account at any time from your profile page, which removes everything listed here together with your saved scores and friendships.
  • Saved scores and friends: Every song you sing with the microphone on is saved with its score, stars, how long you were on the microphone, date, party code and the display name you sang under; a song stopped before its end is saved too, with how far it got, once you sang at least half a minute of it. While signed in it belongs to your account and is shown on your profile and to your friends, unless you make your statistics private (see below). As a guest it is stored under a random id that your browser keeps in localStorage, so that it becomes part of your account if you sign in later on the same browser; until then it is shown to nobody, and clearing your browser's site data severs the link for good. We also remember which signed-in users finished a song in the same party, to suggest them as friends to each other. Friend requests you send or accept are stored until either side removes the friendship. Achievements (milestones such as the number of songs sung) are worked out from these saved scores alone. Your profile shows your display name, picture and the date you joined to anyone who knows the display name. Its statistics, achievements, best songs and recent plays, the numbers next to your name in your friends' lists and your best score on a song in other people's song rankings are public by default as well. In the Privacy section of your profile page you can show them to your friends only, or make them private: then only you see them. Everyone who may not see them sees just your name, picture and joining date. In a party, everyone in it always sees the score of the song you are singing; with private or friends-only statistics your previous best on that song and the achievements you just earned appear on your own screen only. How close you are to the achievements you have not earned yet is shown to you only. Administrators can still see them when they look after the service.
  • Party sessions: When you create or join a party, we temporarily store your chosen display name, party code, and song queue in server memory. This data is not persisted after the party ends.
  • Listen history: We record which songs are played (artist, title, video ID, party code, the display name used, how long the song ran, the round-trip time of your connection during it, the page you arrived from and the country our CDN places your address in) to power the "Popular at Parties" feature and to see how the site is used. We likewise record what is typed into the song search and how a song was chosen (from a search, from browsing, from a pasted YouTube link or from a party queue), to see what people look for and do not find. A song played while you are signed in is linked to your account, and your profile shows how many songs you played, in how many parties, and the latest ones (to you only, like your statistics, if you make them private); as a guest the play is stored under the browser id described above, so that it becomes part of your account if you sign in later on the same browser. Deleting your account removes that link, and the plays stay as anonymous listen history. Searches and how songs were chosen are not linked to an account.
  • Recordings of your singing (“Save recordings”, on unless you turn it off): When you sing, real-time pitch detection runs in your browser. While “Save recordings” is on in the microphone panel, the microphone audio of each song you sing (compressed Opus audio) is uploaded to our server together with the pitch detection telemetry and timing metadata of that song. A recording holds whatever your microphone hears while the song plays, which can include the music and other people nearby. It is stored under your account, or as a guest under the random browser id described above, and becomes part of your account when you sign in on that browser. You can listen to your recordings, mixed with the song's backing track, on your own profile, and so can whoever you allow in your privacy settings (by default nobody else). For that, our server keeps the mixed version of a recording once it has been played, until it has not been played for 7 days. You can delete each recording on your profile or all of them at once; deleting removes the recording, its mixed version and any share videos made from it from our server. We also use recordings to evaluate, benchmark and improve our pitch detection and scoring. With “Save recordings” off, nothing you sing is recorded or uploaded; pitch detection and scoring still work. Recordings made before “Save recordings” existed (October 2026) were kept for that evaluation only and cannot be listened to.
  • Share videos: When you choose “Share video” after a song or on your profile, your browser sends us the pictures of your score card, and our server makes a short video from them and about 15 seconds of your recording of that song mixed with its backing track. The video is sent back to your browser; where it goes from there is up to you. Our server keeps a copy so the same video can be sent again at once, until it has not been asked for in 7 days, or until you delete the recording. “Share audio” on your profile gives your browser the mixed recording itself to share.
  • Share links: A score card, share video or recording you share from SingSpree carries a link to the song with a random code (such as singspree.com/sing/…?r=Ab12Cd34). With the code we store who shared it (your account, or as a guest the random browser id described above), what was shared (the song, and the score or recording) and when, and we count each time it goes out through your share sheet or is downloaded. The code itself says nothing about you, and the same thing shared again gets the same code. When someone opens the link, we note that their browser came by it (under their own random browser id, with the country our CDN places their address in, never the address itself) and whether that browser then starts a party, sings a song or creates an account within 30 days, so we can see how many people shares bring and whose. Opening your own link counts for nothing. The page the link opens shows your name and the shared score only to the people your profile's statistics setting lets see them (see above); as a guest it shows the name you sang under with the score, as the card itself does. If you sign in on the browser you shared from as a guest, its links become your account's. Deleting your account deletes the links you shared and what they counted.
  • Song recognition (the microphone button next to the song search): When you press it, your browser opens the microphone and sends what it hears to our server, a second at a time, for at most 12 seconds. The server compares it with the audio fingerprints of our songs and answers with the song and the place in it that was playing. The audio is held in the server's memory only while it looks and is dropped with the answer, or after 60 seconds at the latest; it is never stored. Like searches, we record that a recognition happened, how long it listened and which song it found, not linked to an account. The microphone closes when the answer comes, when you press Stop, or when you leave the page.
  • Your recent parties and “For you”: Your browser keeps a list of the last ten parties it hosted or joined in its localStorage: when they were, which songs played, the display names of those who sang and the songs still left in the queue. It stays in your browser and is used on the home page to offer the songs a party you hosted left unsung (the ✕ there stops that for the party) and for the “For you” row; clearing your browser's site data removes the whole list. To fill the “For you” row your browser sends the ids of those songs (as a guest also the random browser id described above) to our server, which adds the songs it has saved for you (your plays and scores), answers with songs that go with them and stores nothing about the request. The songs are picked from your own songs only: songs often sung at the same parties as yours (counted over all parties, without names), the same artists and the same languages. “Hide” takes the row off the home page of this browser. “Plan the next one” makes a calendar file in your browser with a link that holds the ids of the party's songs.
  • Language preference: Stored in your browser's localStorage.
  • Server logs: Our web server may log IP addresses and request metadata for operational purposes. These logs are not used for tracking.

3. Third-party services

SingSpree embeds content from the following third-party services, which may collect data independently:

  • YouTube (Google): Song videos are embedded with the YouTube IFrame Player API in YouTube's privacy-enhanced mode (served from youtube-nocookie.com), which does not set cookies on your device and does not use your viewing to personalise your YouTube experience. Song thumbnails are loaded from YouTube's image servers (i.ytimg.com), which also set no cookies. Loading the player or a thumbnail still transfers technical request data such as your IP address to Google, which processes it according to Google's Privacy Policy. By using SingSpree, you also agree to the YouTube Terms of Service.
  • SponsorBlock: We query the SponsorBlock API to skip non-music segments. This sends the video ID to their servers. See SponsorBlock's privacy info.

4. Cookies

SingSpree sets two strictly necessary cookies. singspree_sid is a random identifier for your browser, set on your first visit and kept for up to a year: it lets the server hand a song's lyrics and backing tracks only to the browsers taking part in a party that plays it. It is not linked to your name or account. singspree_session is set only after you sign in to an account; it keeps you signed in for up to 180 days and is removed when you sign out. No other cookies are set, and the embedded YouTube player runs in privacy-enhanced mode so that it does not set cookies either. Preferences such as your language, volume settings and which one-time hints you have already seen are kept in your browser's localStorage (not cookies). Your current party session is kept in sessionStorage and discarded when the tab is closed.

5. Your rights (GDPR)

If you are located in the European Economic Area, you have the right to:

  • Request access to any personal data we hold about you
  • Request correction or deletion of your data
  • Object to or restrict processing of your data
  • Lodge a complaint with your local data protection authority

If you have any concerns, please contact us.

6. Data retention

Party session data is held in server memory only and discarded when the party ends or the server restarts. Listen history records are retained to power song popularity. Recordings of your singing are kept until you delete them on your profile or delete your account, which deletes them too; a guest's recordings can be listened to and deleted after signing in on the same browser. Recordings made before “Save recordings” existed are retained for model evaluation benchmarks. Scores saved as a guest stay under their browser id so that an account created later can take them over. Share links and the visits they brought are kept until the account that shared them is deleted; a guest's stay under its browser id, like its scores.

7. Contact

For privacy-related inquiries, see our Contact page.