Alternatives to Leena AI
Other Conversational AI vendors we measure, sorted by how much they publish that Leena AI does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 26 that differ from Leena AI on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Leena AI has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Public pricing, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change. The column “publishes and Leena AI does not” is the one that closes them.
| Vendor | Score | Publishes, and Leena AI does not | Leena AI publishes, and they do not | |
|---|---|---|---|---|
| Certainlycertainly.io | 65/100 | 5 Data processing agreement, Data location stated, Public pricing, +2 | 1 security.txt (RFC 9116) | Compare |
| Botpressbotpress.com | 52/100 | 5 Data processing agreement, Data location stated, Public pricing, +2 | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Forethoughtforethought.ai | 61/100 | 4 Data processing agreement, Data location stated, Status page with history, +1 | 1 security.txt (RFC 9116) | Compare |
| Voiceflowvoiceflow.com | 57/100 | 4 Data processing agreement, Data location stated, No third-party tracking before consent, +1 | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Netominetomi.com | 48/100 | 3 Data location stated, Status page with history, No third-party tracking before consent | 1 security.txt (RFC 9116) | Compare |
| Tiledesktiledesk.com | 43/100 | 3 Data processing agreement, Data location stated, Notice before subprocessors change | 3 Certifications named, security.txt (RFC 9116), Named privacy contact | Compare |
| Kore.aikore.ai | 39/100 | 2 Data location stated, Status page with history | 1 security.txt (RFC 9116) | Compare |
| Moveworksmoveworks.com | 35/100 | 2 Data location stated, Status page with history | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Landbotlandbot.io | 30/100 | 2 Status page with history, Public pricing | 2 Certifications named, security.txt (RFC 9116) | Compare |
| Chatfuelchatfuel.com | 26/100 | 2 Status page with history, Public pricing | 3 Certifications named, security.txt (RFC 9116), Named privacy contact | Compare |
| Kommunicatekommunicate.io | 26/100 | 2 Public pricing, Uptime SLA with a figure | 2 Certifications named, security.txt (RFC 9116) | Compare |
| Cognigycognigy.com | 26/100 | 1 Data location stated | 2 Certifications named, security.txt (RFC 9116) | 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.