Transparency alternatives to Botsense
Other Conversational AI vendors we measure, sorted by how much we found at them and not at Botsense. This is a comparison of disclosure, not of features or fitness.
12 shown of 35 that differ from Botsense on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Botsense has 12 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Botsense” is the one that closes them.
| Vendor | Score | Found there, not found at Botsense | Found at Botsense, not found there | |
|---|---|---|---|---|
| MessageBirdbird.comSee also Transparency alternatives to MessageBird | 65/100 | 8 Data processing agreement, Subprocessor list, Status page with history, +5 | nothing | Compare |
| Forethoughtforethought.aiSee also Transparency alternatives to Forethought | 61/100 | 7 Data processing agreement, Data location stated, Status page with history, +4 | nothing | Compare |
| Sinchsinch.comSee also Transparency alternatives to Sinch | 57/100 | 7 Data processing agreement, Status page with history, Public pricing, +4 | nothing | Compare |
| Yellow.aiyellow.aiSee also Transparency alternatives to Yellow.ai | 55/100 | 7 Data processing agreement, Public pricing, Certifications named, +4 | nothing | Compare |
| Sendbirdsendbird.comSee also Transparency alternatives to Sendbird | 52/100 | 7 Subprocessor list, Public pricing, Certifications named, +4 | nothing | Compare |
| Botpressbotpress.comSee also Transparency alternatives to Botpress | 52/100 | 6 Data processing agreement, Data location stated, Public pricing, +3 | nothing | Compare |
| Netominetomi.comSee also Transparency alternatives to Netomi | 48/100 | 6 Data location stated, Status page with history, Certifications named, +3 | nothing | Compare |
| Wotnotwotnot.ioSee also Transparency alternatives to Wotnot | 48/100 | 6 Data location stated, Public pricing, Certifications named, +3 | nothing | Compare |
| Rasarasa.comSee also Transparency alternatives to Rasa | 48/100 | 5 Data processing agreement, Data location stated, HTTPS enforced with HSTS, +2 | nothing | Compare |
| Tiledesktiledesk.comSee also Transparency alternatives to Tiledesk | 48/100 | 5 Data processing agreement, Data location stated, HTTPS enforced with HSTS, +2 | nothing | Compare |
| Infobipinfobip.comSee also Transparency alternatives to Infobip | 43/100 | 5 Data processing agreement, Status page with history, Public pricing, +2 | nothing | Compare |
| Typewisetypewise.appSee also Transparency alternatives to Typewise | 39/100 | 5 Data location stated, Public pricing, Certifications named, +2 | nothing | 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.