Transparency alternatives to UnitedMasters
Other Music rights and royalties vendors we measure, sorted by how much we found at them and not at UnitedMasters. This is a comparison of disclosure, not of features or fitness.
12 shown of 25 that differ from UnitedMasters on at least one criterion we measured for both. Public transparency score, not a product or security rating.
UnitedMasters has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change. The column “Found there, not found at UnitedMasters” is the one that closes them.
| Vendor | Score | Found there, not found at UnitedMasters | Found at UnitedMasters, not found there | |
|---|---|---|---|---|
| Reprtoirreprtoir.comSee also Transparency alternatives to Reprtoir | 43/100 | 2 Data location stated, Status page with history | 1 security.txt (RFC 9116) | Compare |
| Beatdappbeatdapp.comSee also Transparency alternatives to Beatdapp | 17/100 | 2 Certifications named, No third-party tracking before consent | 3 Public pricing, HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Amuseamuse.ioSee also Transparency alternatives to Amuse | 35/100 | 1 Data location stated | 1 security.txt (RFC 9116) | Compare |
| Tunecoretunecore.comSee also Transparency alternatives to Tunecore | 35/100 | 1 Data location stated | 1 security.txt (RFC 9116) | Compare |
| Chartmetricchartmetric.comSee also Transparency alternatives to Chartmetric | 26/100 | 1 Status page with history | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Soundchartssoundcharts.comSee also Transparency alternatives to Soundcharts | 26/100 | 1 Status page with history | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Symphonicsymphonicdistribution.comSee also Transparency alternatives to Symphonic | 26/100 | 1 Data location stated | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Jaxstajaxsta.comSee also Transparency alternatives to Jaxsta | 22/100 | 1 Data location stated | 3 Public pricing, security.txt (RFC 9116), Named privacy contact | Compare |
| Pexpex.comSee also Transparency alternatives to Pex | 22/100 | 1 Data location stated | 3 Public pricing, security.txt (RFC 9116), Named privacy contact | Compare |
| Royalty Exchangeroyaltyexchange.comSee also Transparency alternatives to Royalty Exchange | 22/100 | 1 Status page with history | 2 Public pricing, security.txt (RFC 9116) | Compare |
| FUGAfuga.comSee also Transparency alternatives to FUGA | 17/100 | 1 Data location stated | 3 Public pricing, HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| CD Babycdbaby.comSee also Transparency alternatives to CD Baby | 13/100 | 1 Data location stated | 4 Public pricing, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | Compare |
Only criteria we could measure for both are counted. Where we could measure one and not the other, the row is silent: that would be a statement about our measurement, not about either vendor. Every single result with its source is on the two profiles.