Transparency alternatives to Sensi.AI
Other Senior living vendors we measure, sorted by how much they publish that Sensi.AI does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 23 that differ from Sensi.AI on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Sensi.AI has 9 gaps in what we could measure: 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). The column “publishes and Sensi.AI does not” is the one that closes them.
| Vendor | Score | Publishes, and Sensi.AI does not | Sensi.AI publishes, and they do not | |
|---|---|---|---|---|
| CarePredictcarepredict.com | 26/100 | 2 Data location stated, HTTPS enforced with HSTS | 2 Data processing agreement, Notice before subprocessors change | Compare |
| VirtuSensevirtusense.ai | 22/100 | 2 Data location stated, HTTPS enforced with HSTS | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | Compare |
| StoriiCarestorii.com | 17/100 | 2 Public pricing, HTTPS enforced with HSTS | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | Compare |
| WelcomeHomewelcomehomesoftware.com | 17/100 | 2 Public pricing, HTTPS enforced with HSTS | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | Compare |
| Serenityserenitysmart.com | 10/100 | 2 Certifications named, Uptime SLA with a figure | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | Compare |
| LifeLooplifeloop.com | 13/100 | 1 HTTPS enforced with HSTS | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Cubigocubigo.com | 9/100 | 1 HTTPS enforced with HSTS | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | Compare |
| ECPecp123.com | 9/100 | 1 HTTPS enforced with HSTS | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | Compare |
| Eldermarkeldermark.com | 9/100 | 1 HTTPS enforced with HSTS | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | Compare |
| icareicaremanager.com | 9/100 | 1 HTTPS enforced with HSTS | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | Compare |
| Vigil Healthvigil.com | 9/100 | 1 HTTPS enforced with HSTS | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | Compare |
| Viibrantviibrant.com | 9/100 | 1 HTTPS enforced with HSTS | 3 Data processing agreement, Notice before subprocessors change, 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.