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