Privacy Policy (Datenschutzerklärung)
1. Controller
The controller within the meaning of the General Data Protection Regulation (GDPR, in German: DSGVO) is the person named in the Imprint. Contact for privacy requests: contact@stopthesong.com.
2. Overview
Stop the Song is a free music guessing game. Every game mode works without a user account. If you like, you can create a user account (section 6); it gives you a unique name marked as verified and a history of your games that only you can see, but nothing depends on it. No advertising services and no third-party analytics services are used; how many people visit and play the game is counted by a program on our own server, without cookies (section 16). A cookie is set only if you sign in with an account (section 9).
Games in progress live only in the server’s memory. Only the following are stored permanently in a database on the server: the public leaderboard for completed Ranked games and the results of the daily challenge (section 5) and, if you create one, your user account with the history of your games and your private groups (section 6).
3. Hosting, server log files and overload protection
The application runs on a virtual server of Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, Germany (server location: Falkenstein, Germany). A data processing agreement under Art. 28 GDPR is in place with Hetzner.
When you open the page, your browser must, for technical reasons, tell the server its IP address so that the page can be delivered. The web server in front of the application (Caddy) keeps no access logs. Its error log contains no IP addresses, no request headers and no browser identifiers. The containers’ logs are limited to about 2 MB per service and are discarded whenever the service is redeployed. The game application itself writes no IP addresses and no email addresses to log files.
To prevent overload and abuse, the game application limits how often a single IP address can create rooms, check room codes or join rooms, request title suggestions, and use the user account functions (registration, sign-in, recovery, “forgot password”, confirmation links, account settings, invite codes of private groups) and the feedback form. (When joining, the application first checks whether a room exists for the code entered; this check counts as a join.) To do so, it keeps the IP address together with the times of the most recent requests exclusively in memory, and only for as long as the respective time window lasts: one second to one minute for the game, 15 minutes for recovery with the recovery code and for invite codes of private groups, and at most one hour for registration, “forgot password” and the feedback form. It is deleted a few seconds after the window ends at the latest.
In addition, the application counts failed sign-in attempts in memory for each username or email address entered, both together with the IP address they came from (after five failed attempts from there, the waiting time before the next attempt from there grows) and without it (after five failed attempts in total, signing in with that name requires the security check, section 8). It likewise counts wrong password entries used to confirm a change in the account settings, and invite codes of private groups entered, per account. It also limits how often an address is emailed via “forgot password”; for this it keeps only a hash value of the address, not the address itself. All of this is deleted one hour after the last attempt at the latest.
Legal basis: Art. 6(1)(f) GDPR (legitimate interest in secure and functioning operation and in protecting user accounts). The IP address is not stored beyond this.
4. Playing the game
To play, you enter a name (player name); if you are signed in with an account, it is your username. You decide which name you choose. The following is processed: player name, room code, role (host/player), game events (buzzer, answers, right or wrong), score, the technical connection identifier and, if you are signed in, which seat belongs to your account. Name, score and game events are visible to all participants in the same room; for signed-in players there is also a mark showing that the name belongs to an account. In “One device” mode only the host’s seat can belong to an account; names the host enters for others are not linked to any account.
Legal basis: Art. 6(1)(b) GDPR (providing the game you use), alternatively point (f). Retention: This data lives exclusively in memory. A room is deleted automatically after three hours of inactivity, at the latest when the server restarts. Exceptions are the leaderboard entry after a completed Ranked game, the result of a daily challenge run (section 5) and, for an account, the number of your finished games and your game history (section 6).
Sharing: If you tap “Share invite” or “Share result”, Stop the Song hands the invite link with the room code, or the result of the game (a text with the names and points of the top three places and a picture of it), to your device’s share menu. The picture is created only on your device; Stop the Song sends nothing to the server or to third parties in the process. Only when you choose an app in the share menu (for example WhatsApp or Instagram) does the content go to that app, and its privacy terms apply. Whether and with whom you share is up to you. If your device has no share menu, the text is copied to your clipboard instead.
5. Public leaderboards (Ranked games and daily challenge)
Besides free games (“Custom”), there are Ranked games in Solo mode and in “Everyone joins” mode. Only when a Ranked game reaches its goal (100 points in Race, 20 points in Sprint, or the 90 seconds running out in Score Attack) is an entry stored permanently on the server and shown publicly. Custom games and Ranked games ended early never make it into the leaderboard.
- Content of an entry: for Solo games, the player name, the score reached or the time needed, and the date. For Ranked games in “Everyone joins” mode, the whole room counts as a team: the entry contains the player names of all participants in the room with their points, the shared score or time, and the date. Anyone who joins a Ranked room therefore appears with their player name in its entry. If someone plays with an account, the entry, or their place in the team, is linked to that account: the current username (also after a rename) and a mark for “signed-in account” are shown; entries without an account are marked “guest”. In addition there is a random internal identifier for the entry. IP addresses, device identifiers or other details are not stored.
- Name prompt: If the host’s seat is still called “Player” or “Host” when saving, the host is asked under which name the entry should appear. They can also leave the name unchanged, or create an account or sign in; the entry is then saved under that account.
- Who sees the entry: The leaderboard can be viewed without signing in by all visitors to Stop the Song, on the “Leaderboard” page and through the corresponding interface (
/api/leaderboard). The entries are therefore visible worldwide and can be retrieved and copied by third parties. Members of private groups can also view the leaderboard limited to the entries of their group (section 6). - Storage location: the database on the server at Hetzner in Germany (section 3), including its backups (section 10).
- Retention: Each of the six leaderboards shows only the 100 best entries publicly. An entry that drops out of the best 100 is deleted, unless it is the best entry of an account on that leaderboard (for team entries: of one of the accounts involved). It then stays stored until the account achieves a better entry, but is no longer public; it is shown only in that account’s private groups (section 6), for team entries with the names of all team members. An entry is also deleted when you request its deletion (section 13), when you delete your account (section 6), or when the leaderboards are reset, for example because the rules of a Ranked game change. There is no other time limit.
Legal basis: Art. 6(1)(b) GDPR: a Ranked game consists precisely in measuring yourself against others with your result in the public leaderboard. Alternatively Art. 6(1)(f) GDPR applies (legitimate interest in offering a fair, lasting ranking). I delete an entry on request.
Daily challenge (“Daily challenge”)
Every day there are five songs that are the same for everyone; new songs appear at midnight German time. As soon as the first song of a run starts, an entry is stored: the day, for an account the link to the account, otherwise the name you give as a guest, the start and end of the run, and your result (songs solved, how many seconds of music you heard, your time, the number of wrong answers, and these values per song). The server measures the time. With an account, only one run per day is possible.
- Who sees the entry: Completed runs appear publicly on the page for the day in question and through the corresponding interface (
/api/daily), retrievable without signing in: runs with an account in the day’s ranking (with the current username, the mark for “signed-in account” and the result), runs as a guest separately in an unranked list with the name given and the result. Earlier days remain available. Members of private groups can also view only the runs of their group, ranked among themselves (section 6). - Retention: Entries with an account are stored until you delete your account (they also make up the streaks and charts in your profile). Guest entries are deleted after 30 days. The selection of a day’s songs is kept for 60 days so that songs do not repeat too quickly; it contains no personal data.
- One guest run per device: For this, your browser remembers in local storage on which day a guest last played on this device (section 9).
Legal basis: Art. 6(1)(b) GDPR: the daily challenge consists in comparing your result with others. I delete an entry on request.
6. User account (optional)
An account is optional; the game works fully without one. You can create it in two ways: with just a username and password, or additionally with an email address. A security check (ALTCHA, section 8) is carried out at registration.
What is stored
- Account data: username (and a normalised spelling of it, so that similar-looking names cannot be taken twice), your password only as a hash value (Argon2id; the password itself is never stored), where applicable your recovery code only as a hash value, your email address only after you have confirmed it and the time of confirmation, the date of registration and of the last rename, the number of your finished games, and when and how often you last dismissed the “Add email” notice.
- Sign-ins (sessions): For each device on which you are signed in, a random session token (only as a hash value), a rough device label from browser and operating system (for example “Firefox on Android”; the full browser identifier is not stored), when you signed in and when the session was last used (updated at most once a day). No IP address.
- Confirmation and reset links: An email address that has not yet been confirmed is stored together with a random token (only as a hash value) until you confirm it, for at most 24 hours (after that it is deleted at the latest one further day later). Links for resetting the password are valid for 30 minutes and only once; they too are stored only as a hash value and deleted at the latest one day after they expire.
- Game history: For every game you play while signed in and in which at least one song was resolved, the following is stored when the game ends: start and end, game mode, whether it was a Ranked game (and for which leaderboard), how it ended (goal reached, ended, or room expired), the game settings (for example music selection including a pasted playlist link, playback and goal), your score, your rank, the number of participants and, where applicable, the time or score with which the goal was reached. In addition, for each song you heard in this game: title, artist, the address of the album cover, genre, decade and difficulty level, whether you guessed artist and title, how many wrong answers you gave, your points, how long the song played until your first “STOP!” and until your first correct answer and, with progressive reveal, at which snippet you got it right. Only your own result is stored: names and results of other participants do not appear in your history. Players that the host adds in “One device” mode have no account; no history is stored for them. Songs that were skipped or no longer resolved because the game ended early are not stored. From the game history the application calculates, on request, the charts under “Progress” (for example Ranked times, hit rates); nothing additional is stored for this.
- Leaderboard entries and results of the daily challenge that are linked to your account (section 5).
- Private groups: for every group you create or join, its name, when it was created, your membership (when you joined and whether you manage the group) and a hash value of its invite code. The invite code itself is not stored; the server calculates it when needed from its secret key and a random value of the group.
Who sees what
Your username is public: in rooms where you play, and in the leaderboard, each with a mark for “signed-in account”. Your email address, your devices, your game history and all other account data are visible only to you when you are signed in; they are not shown to anyone else. The exception is your private groups: their members see that you belong to them (see below).
Private groups
With an account you can create and join private groups (at most 10 groups, at most 50 members per group) to compare yourself with friends. A group is a filtered view of the leaderboards and the daily challenge: it shows only the entries of its members, ranked among themselves; your results continue to be kept publicly as described in section 5. Anyone who belongs to a group sees its name, its invite code, the current usernames of all members and their results in the group view, including entries that are no longer among the public best 100 (section 5). The group views can be retrieved only by signed-in members. Anyone with an account who knows the invite code can join; members can pass it on. Whoever manages the group can rename it, renew the code (the old one then no longer works), remove members and delete the group. In invite links the code comes after the # character; this part is not transmitted to the server when the link is opened and is not recorded by the visit counting (section 16). Retention: Your membership ends when you leave the group, are removed from it, the group is deleted or you delete your account. If the person managing the group leaves it, management passes to the longest-standing member; if the last member leaves, the group is deleted. Legal basis: Art. 6(1)(b) GDPR (the group function you use).
Forgot password and recovery
With a confirmed email address you can reset your password by an email link. Without an email address you receive a recovery code at registration, which is shown only once; with it you set a new password. Without a confirmed email address and without a recovery code, an account cannot be recovered, not even on request to the operator. There is no manual recovery.
Retention, access, export and deletion
Your account data is stored until you delete your account. A sign-in on a device ends when you sign out, end it in the device list, change or reset your password (then all other sessions, or all sessions, end), or when it has not been used for a year.
In the account settings you can at any time download all data stored about your account as a file (Art. 15 and 20 GDPR) and delete your account yourself (Art. 17 GDPR). Deletion requires your password or your recovery code and takes effect immediately: the account is deleted with all the data named above, including your game history and your daily challenge results, all sign-ins and open links, and your solo entries in the leaderboard. You leave your private groups; management of a group passes to its longest-standing member, and a group without other members is deleted. In team entries (“Everyone joins”), your seat is replaced by “Deleted player”, without your name; the results of the other team members remain. The data disappears from the backups after 14 days at the latest (section 10).
Legal basis: Art. 6(1)(b) GDPR (providing the account you created). Where data serves security (sessions, device labels, lockouts after failed attempts), additionally Art. 6(1)(f) GDPR (legitimate interest in protecting your account).
7. Emails
We never email you unprompted. An email goes out only as the direct result of your own action: to confirm an email address (at registration, when adding or changing it) and to reset the password when you use “Forgot password”. There are no newsletters, no notifications, no reminders, no advertising and no notices such as “Your password was changed”; instead you can see which devices are signed in in your account settings. If an address has already been confirmed for another account, nothing is sent to it. When you change the address, the previous address receives no message.
The emails contain no tracking pixels and no redirected links. To send them we use the email delivery service Brevo: Brevo GmbH, Köpenicker Str. 126, 10179 Berlin, Germany (privacy notice). In doing so, Brevo processes your email address, the content of the email and technical delivery information (for example delivery status, bounces) on our behalf and on our instructions; a data processing agreement under Art. 28 GDPR is in place with Brevo. According to Brevo, the data is stored on servers in the EU. Brevo does, however, also use sub-processors based in the USA or belonging to a group based outside the EU (such as Google Cloud or Cloudflare), so a transfer to third countries cannot be ruled out. It takes place only on the basis of the European Commission's adequacy decision on the EU-US Data Privacy Framework (Art. 45 GDPR) or the EU standard contractual clauses (Art. 46(2)(c) GDPR).
Legal basis: Art. 6(1)(b) GDPR (the confirmation or password reset you requested).
Feedback form
Through “Feedback” (at the bottom of the page and in the settings) you can send us problems, ideas for improvement and other comments. What is transmitted is your text, optionally your email address, and a rough device label from browser and operating system (for example “Firefox on Android”; the full browser identifier is not transmitted). Your player name, your username or account, and your games are not sent along, even if you are signed in. The security check (ALTCHA, section 8) is required before sending. Stop the Song does not store the message: the server sends it directly through our mailbox at mailbox.org (see below), not through Brevo, as an email to our address feedback@stopthesong.com and discards it afterwards. An email address you give is entered only as the reply address; nothing is sent to it automatically, and we use it only to reply to your message. We delete the email with your feedback as soon as your matter is settled and we no longer need it to follow it up. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in fixing errors, improving the game and answering enquiries).
We receive emails to our contact address, and send and receive the feedback, through the email service mailbox.org of Heinlein Hosting GmbH, Schwedter Straße 8/9A, 10119 Berlin, Germany (servers in Germany); a data processing agreement under Art. 28 GDPR is also in place with this provider. We use your message and your address only to reply to you. The legal basis is our legitimate interest in answering enquiries (Art. 6(1)(f) GDPR).
8. Protection against automated sign-ups (ALTCHA)
To protect registration, “forgot password”, the feedback form and, after repeated failed sign-in attempts for a username, signing in against automated mass requests, we use the security technology ALTCHA. Unlike reCAPTCHA, hCaptcha or Cloudflare Turnstile, ALTCHA runs entirely on our own server: your browser solves a small computing task in the background (proof-of-work method) before the form can be submitted. No data is sent to a third-party provider, no cookies are set, and your behaviour or your device is not analysed. For each task issued, the server stores only a random identifier and the time, so that a solved task can be used only once, and deletes both after 20 minutes at the latest. The task is solved in the browser; without JavaScript enabled, registering and sending feedback are therefore not possible. You can find information about ALTCHA at altcha.org.
Legal basis: Art. 6(1)(f) GDPR (legitimate interest in protection against abuse).
9. Cookie and local storage in the browser
Sign-in cookie: Only when you sign in with an account does Stop the Song set a cookie named __Host-sts_session. It contains a random session token with which the server recognises you, cannot be read by scripts (HttpOnly), is sent only over HTTPS and only to Stop the Song itself (other websites can neither set nor overwrite it because of the __Host- prefix) and expires after a year without use. It is deleted when you sign out. Without signing in, no cookie is set.
Local storage: Stop the Song stores in your browser’s local storage (localStorage) the code of your current room with a random session token. For every room you join with your name, the room code, player name and a random token are added. With this you return to your seat after reloading the page or after a connection drop. This data is not passed to third parties and is not used to recognise you beyond the game or for advertising. It stays in your browser until you delete it through the browser settings. The session token is also deleted when you leave a room.
When you start a game as host, Stop the Song also stores its settings there: game mode, music selection (for example genre, decade, artist or a pasted playlist link) and game rules. With these you can restart that game from the start page with “Play again”. Player names are not part of it. The settings are replaced when the next game is started and likewise stay only in your browser until you delete them through the browser settings.
If you change something in the settings (gear icon at the top right), Stop the Song likewise stores your choice there: the colour theme (Automatic, Night set or Vinyl pop), whether the next song starts automatically after the reveal and after how many seconds, and whether your device should vibrate. This information does not leave your device and stays stored until you delete it through the browser settings.
If you play the daily challenge as a guest, Stop the Song also stores there the day of that run, so that only one guest run per day is offered on this device. This information does not leave your device and is overwritten at the next guest run.
If you switch off visit counting (section 16), your browser remembers that there under umami.disabled until you switch it back on. Nothing is stored for the counting itself, and none of the information named here is read for it.
Legal basis: Section 25(2) no. 2 of the German Telecommunications Digital Services Data Protection Act (TDDDG) (strictly necessary to provide the service you expressly requested, that is the game and, if you sign in, your account; consent is therefore not required) and Art. 6(1)(b) GDPR.
10. Backups
So that accounts and the leaderboard are not lost in the event of a technical fault, the database is backed up daily. The backups are on the same server at Hetzner in Germany (section 3) and are deleted automatically after 14 days. Deleted accounts and entries therefore also disappear from the backups at most 14 days after their deletion. A backup is used only to restore the database after a fault.
Legal basis: Art. 6(1)(f) GDPR (legitimate interest in reliable operation) and Art. 32 GDPR.
11. Music services: Deezer, Apple and Spotify
Songs, titles, artists, genres and album covers come from Deezer and, where no preview is available there, from Apple (iTunes Search API). In addition, playlists can be imported as a link from Deezer, Spotify or Apple Music. The following applies:
- Server side: Our server retrieves the catalogues of Deezer or Apple (for example charts, search, playlists, autocomplete). If you paste the link to a playlist, our server loads the public playlist page at Deezer, Spotify or Apple Music. The playlist identifier is sent to the respective provider, together with the IP address of our server, not yours. What you type into the answer fields is processed on our server for suggestions and not stored.
- Directly from your browser: The host device loads the audio preview directly from the servers (CDN) of Deezer or Apple. For songs from a Spotify playlist for which there is no preview there, it loads the preview directly from Spotify. All devices in the room also load the album covers directly from Deezer or Apple when a round is revealed. In doing so, these providers necessarily receive the IP address and browser information of the device concerned. No referrer (which page the request comes from) is sent.
Legal basis: Art. 6(1)(f) GDPR (legitimate interest in offering the game with music content; without this connection, playback is not possible). You can object to the processing (see section 13), but then you cannot use the game.
Recipients: Deezer S.A., 12 rue d'Athènes, 75009 Paris, France (privacy notice); Apple Distribution International Ltd., Hollyhill Industrial Estate, Hollyhill, Cork, Ireland (privacy notice); Spotify AB, Regeringsgatan 19, 111 53 Stockholm, Sweden (privacy notice). Apple and Spotify may also transfer data to the USA; there, the adequacy decision on the EU-US Data Privacy Framework applies where relevant, or standard contractual clauses are used. I have no influence on the processing by these providers.
12. Fonts and recipients
The fonts used (Plus Jakarta Sans, Bricolage Grotesque, DM Mono) are hosted locally on the server. No connection is made to Google or other font providers.
Apart from the parties named in sections 3, 7 and 11, your data is not passed on to third parties. Leaderboard entries and usernames are, however, public (sections 5 and 6) and therefore retrievable by anyone. A transfer to third countries takes place only as described in sections 7 and 11.
13. Your rights
Under the GDPR you have the following rights:
- access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18) and data portability (Art. 20),
- objection to processing based on Art. 6(1)(f) GDPR on grounds relating to your particular situation (Art. 21),
- lodging a complaint with a data protection supervisory authority (Art. 77). The authority responsible is, for example, the one where you live or where the controller is based: Landesbeauftragte für Datenschutz und Informationsfreiheit Nordrhein-Westfalen, Kavalleriestraße 2–4, 40213 Düsseldorf, Germany, www.ldi.nrw.de.
With an account, you can exercise access (export), rectification (username, email) and deletion yourself in your account settings. Otherwise an email to the address given above is enough. To have an entry in the leaderboard deleted or changed without an account, please give the player name, the leaderboard (for example “Solo · Race”) and roughly the date. Because games in progress exist only transiently in memory and cannot be assigned to any person, access or deletion there is possible in individual cases only if you give the room code and player name.
14. Obligation to provide data, automated decisions
Giving a player name is necessary for playing; which name you give is up to you. A user account and an email address are optional. There is no automated decision-making, including profiling.
15. Security
Transmission between your browser and the server is encrypted (HTTPS/TLS). Passwords are hashed with Argon2id; session tokens, recovery codes and links are stored only as hash values. The application runs without administrator privileges in an isolated container.
16. Visit counting (Umami)
To understand how many people visit Stop the Song, how they find their way to the game, and which ways of playing are used how often and for how long, I use the open-source software Umami. Umami runs on my own server at Hetzner (section 3). The counting script is loaded by Stop the Song itself, and your browser sends the counting data only to Stop the Song; no data is passed to third parties. No cookies are set.
On every page view, your browser sends the page opened, the page you came from (referrer), the page title, the browser’s language setting and the screen size. Of the page’s address, only a campaign tag remains if the link has one (such as “?via=…”); if you arrive through an invite link, only “invite” is counted, not the room code. Your browser removes all other parts of the address, including the confirmation and password links from our emails and the invite codes of private groups, before sending.
In addition, these events are counted: a room is created or joined (by code or invite link), a game starts or ends (separately for Custom, Ranked and daily challenge), an invite or a result is shared, a leaderboard is opened, an account is created. For a game, only categories and numbers are sent: how it is played (alone, several people on one device, or everyone on their own device), game style, music selection as a category (for example “Hits” or “Playlist”), goal, and number of players as a range; at the end also the duration of the game, the number of songs and how the game ended; for the daily challenge the points and whether it was played with or without an account. The events never contain names, room codes, usernames, answers, songs or playlist links. Only the host’s device reports the start and end of a game.
From your IP address and your browser’s identifier, the server determines country, region and city as well as browser, operating system and device type, and from these forms a pseudonymous visit identifier using a secret key that changes daily. The IP address itself is not stored; a visit on another day cannot be linked to earlier ones. Nothing is stored on your device for the counting.
Legal basis: Art. 6(1)(f) GDPR (legitimate interest in improving the game). The counting data is deleted automatically after 13 months. If your browser sends “Do Not Track” or “Global Privacy Control”, your visits are not counted. You can object to the counting at any time and switch it off for this browser here:
17. Changes
I will adapt this policy when the service or the legal situation changes. The version published here at the time applies.