Privacy

Tempo Match has no accounts and stores no personal data. It sets no cookies of its own and uses no analytics.

What happens when you search

Your browser sends the chosen BPM to the Tempo Match server. The server then asks GetSongBPM and Deezer for songs at that tempo and searches Spotify for the matching tracks. These requests are made by the server, so GetSongBPM and Deezer receive the tempo and Spotify receives song names and recording codes (ISRCs), not your IP address or browser details. To skip songs listed at the wrong tempo, the server then asks ReccoBeats for the tempo of the Spotify track it found, so ReccoBeats receives Spotify track IDs from the server only. The dice button works the same way: the server searches Spotify for a random common word and asks ReccoBeats for the popularity and tempo of the tracks found.

To show songs that play where you are, the Spotify search uses your country. Cloudflare, which delivers the site, derives a country code from your IP address and supplies it to the server. Tempo Match sends that code to Spotify with the search and keeps it in the keys of its in-memory lookup cache, which is lost when the server restarts. It does not write the code to persistent storage or tie it to a visitor profile.

Tempo Match does not log your searches. Whoever hosts a copy of the app may keep standard server access logs, such as IP addresses, under their own policy.

Spotify player

When a song is found, the page shows Spotify's embedded player. It loads directly from Spotify in your browser, so Spotify receives your IP address and browser details and may set its own cookies, including recognising you if you are logged in to Spotify. The "Play on Spotify" button opens the Spotify app. Spotify's handling of that data is covered by the Spotify Privacy Policy.

Contact

Questions about privacy: open an issue at github.com/hadalin/tempo-match/issues.