Is Chorus - Spotify Enhancer safe?
Chorus - Spotify Enhancer captures your Spotify Authorization header and reuses it for Spotify API and playback requests.
When Spotify pages make API requests, the extension's background worker reads the Authorization header and stores it in extension storage as chorus_auth_token. It then attaches that token to later fetches to Spotify API, partner, and spclient endpoints to check library state, new releases, liked tracks, and playback commands.
Who publishes itCharles Drani - no other listings under this identity, 1 shared hostname
Charles Drani - no other listings under this identity, 1 shared hostname
What this publisher told the store about itself, and the other listings that told it the same thing.
Shared hosts - 1 hostname
Hostnames hardcoded in this extension that few other listings call. That can mean one operator behind both, and it can equally mean a small shared vendor, so it is context rather than a conclusion. Hosts that many listings call are left out: they are services, not connections.
AI-generated. Findings may contain errors. Those marked Verified have been manually reviewed.
Publishers can request a review.
Where it sends data
Destinations our analysis observed Chorus - Spotify Enhancer contacting. Sending data somewhere is not a finding on its own - an extension that syncs your settings has to talk to its own server - but it is where your data can go, and who else it goes to.
- api-partner.spotify.com
Chorus - Spotify Enhancer sends data to api-partner.spotify.com. One other extension we have analysed sends data here.
- api.spotify.com
Chorus - Spotify Enhancer sends data to api.spotify.com. One other extension we have analysed sends data here.
- guc3-spclient.spotify.com
Chorus - Spotify Enhancer sends data to guc3-spclient.spotify.com. No other extension we have analysed sends data here.