Alternatives to Kinderheldin
Other Telehealth platforms vendors we measure, sorted by how much they publish that Kinderheldin does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 17 that differ from Kinderheldin on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Kinderheldin has 11 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. The column “publishes and Kinderheldin does not” is the one that closes them.
| Vendor | Score | Publishes, and Kinderheldin does not | Kinderheldin publishes, and they do not | |
|---|---|---|---|---|
| Janejane.app | 57/100 | 6 Data processing agreement, Data location stated, Public pricing, +3 | nothing | Compare |
| Halaxyhalaxy.com | 52/100 | 5 Subprocessor list, Data location stated, Public pricing, +2 | nothing | Compare |
| Zandazandahealth.com | 30/100 | 3 Data location stated, Public pricing, Certifications named | nothing | Compare |
| Doxy.medoxy.me | 26/100 | 3 Status page with history, Public pricing, HTTPS enforced with HSTS | 1 Named privacy contact | Compare |
| Healthiegethealthie.com | 26/100 | 3 Data location stated, Public pricing, Certifications named | 1 Named privacy contact | Compare |
| Corepluscorepluspm.com | 22/100 | 2 Public pricing, HTTPS enforced with HSTS | nothing | Compare |
| Dermanosticdermanostic.com | 22/100 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | nothing | Compare |
| Owl Practiceowlpractice.ca | 22/100 | 2 Data location stated, Public pricing | 1 Named privacy contact | Compare |
| Updoxupdox.com | 22/100 | 2 Data location stated, Status page with history | 1 Named privacy contact | Compare |
| Arztkonsultationarztkonsultation.de | 17/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | nothing | Compare |
| Sanvartissanvartis.de | 17/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | nothing | Compare |
| Livilivi.co.uk | 13/100 | 1 HTTPS enforced with HSTS | 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.