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