Transparency alternatives to Meltwater
Other Social listening vendors we measure, sorted by how much we found at them and not at Meltwater. This is a comparison of disclosure, not of features or fitness.
12 shown of 31 that differ from Meltwater on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Meltwater has 6 gaps in what we could measure: Data location stated, Public pricing, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change. The column “Found there, not found at Meltwater” is the one that closes them.
| Vendor | Score | Found there, not found at Meltwater | Found at Meltwater, not found there | |
|---|---|---|---|---|
| Determdeterm.comSee also Transparency alternatives to Determ | 39/100 | 2 Public pricing, Notice before subprocessors change | 4 Subprocessor list, Status page with history, security.txt (RFC 9116), +1 | Compare |
| Brand24brand24.comSee also Transparency alternatives to Brand24 | 36/100 | 2 Data location stated, Public pricing | 3 Data processing agreement, Subprocessor list, Status page with history | Compare |
| YouScanyouscan.ioSee also Transparency alternatives to YouScan | 35/100 | 2 Public pricing, Certifications named | 3 Data processing agreement, Subprocessor list, security.txt (RFC 9116) | Compare |
| Onclusiveonclusive.comSee also Transparency alternatives to Onclusive | 13/100 | 2 Certifications named, Uptime SLA with a figure | 5 Data processing agreement, Subprocessor list, Status page with history, +2 | Compare |
| Prezlyprezly.comSee also Transparency alternatives to Prezly | 43/100 | 1 Public pricing | 2 Subprocessor list, security.txt (RFC 9116) | Compare |
| Quintlyquintly.comSee also Transparency alternatives to Quintly | 39/100 | 1 Notice before subprocessors change | 3 Data processing agreement, security.txt (RFC 9116), Named privacy contact | Compare |
| Presspagepresspage.comSee also Transparency alternatives to Presspage | 26/100 | 1 Public pricing | 4 Data processing agreement, Subprocessor list, security.txt (RFC 9116), +1 | Compare |
| Socialinsidersocialinsider.ioSee also Transparency alternatives to Socialinsider | 22/100 | 1 Public pricing | 4 Data processing agreement, Subprocessor list, Status page with history, +1 | Compare |
| Awarioawario.comSee also Transparency alternatives to Awario | 17/100 | 1 Public pricing | 5 Data processing agreement, Subprocessor list, Status page with history, +2 | Compare |
| Buzzsumobuzzsumo.comSee also Transparency alternatives to Buzzsumo | 17/100 | 1 Public pricing | 5 Data processing agreement, Subprocessor list, Status page with history, +2 | Compare |
| Exploding Topicsexplodingtopics.comSee also Transparency alternatives to Exploding Topics | 9/100 | 1 Public pricing | 6 Data processing agreement, Subprocessor list, Status page with history, +3 | Compare |
| GummySearchgummysearch.comSee also Transparency alternatives to GummySearch | 9/100 | 1 Public pricing | 6 Data processing agreement, Subprocessor list, Status page with history, +3 | 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.