Transparency alternatives to Sensi.AI
Other Senior living vendors we measure, sorted by how much we found at them and not at Sensi.AI. 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 “Found there, not found at Sensi.AI” is the one that closes them.
| Vendor | Score | Found there, not found at Sensi.AI | Found at Sensi.AI, not found there | |
|---|---|---|---|---|
| CarePredictcarepredict.comSee also Transparency alternatives to CarePredict | 26/100 | 2 Data location stated, HTTPS enforced with HSTS | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Viibrantviibrant.comSee also Transparency alternatives to Viibrant | 22/100 | 2 Data location stated, HTTPS enforced with HSTS | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | Compare |
| VirtuSensevirtusense.aiSee also Transparency alternatives to VirtuSense | 22/100 | 2 Data location stated, HTTPS enforced with HSTS | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | Compare |
| Eldermarkeldermark.comSee also Transparency alternatives to Eldermark | 17/100 | 2 Status page with history, HTTPS enforced with HSTS | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | Compare |
| StoriiCarestorii.comSee also Transparency alternatives to StoriiCare | 17/100 | 2 Public pricing, HTTPS enforced with HSTS | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | Compare |
| WelcomeHomewelcomehomesoftware.comSee also Transparency alternatives to WelcomeHome | 17/100 | 2 Public pricing, HTTPS enforced with HSTS | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | Compare |
| Serenityserenitysmart.comSee also Transparency alternatives to Serenity | 10/100 | 2 Certifications named, Uptime SLA with a figure | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | Compare |
| Caremergecaremerge.comSee also Transparency alternatives to Caremerge | 17/100 | 1 Data location stated | 2 Data processing agreement, Notice before subprocessors change | Compare |
| LifeLooplifeloop.comSee also Transparency alternatives to LifeLoop | 13/100 | 1 HTTPS enforced with HSTS | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Cubigocubigo.comSee also Transparency alternatives to Cubigo | 9/100 | 1 HTTPS enforced with HSTS | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | Compare |
| ECPecp123.comSee also Transparency alternatives to ECP | 9/100 | 1 HTTPS enforced with HSTS | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | Compare |
| icareicaremanager.comSee also Transparency alternatives to icare | 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.