Transparency alternatives to Teladoc Health
Other Telehealth platforms vendors we measure, sorted by how much we found at them and not at Teladoc Health. This is a comparison of disclosure, not of features or fitness.
12 shown of 25 that differ from Teladoc Health on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Teladoc Health has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Teladoc Health” is the one that closes them.
| Vendor | Score | Found there, not found at Teladoc Health | Found at Teladoc Health, not found there | |
|---|---|---|---|---|
| Janejane.appSee also Transparency alternatives to Jane | 57/100 | 5 Data processing agreement, Certifications named, Uptime SLA with a figure, +2 | 1 security.txt (RFC 9116) | Compare |
| Halaxyhalaxy.comSee also Transparency alternatives to Halaxy | 52/100 | 3 Subprocessor list, HTTPS enforced with HSTS, Named privacy contact | nothing | Compare |
| Zandazandahealth.comSee also Transparency alternatives to Zanda | 39/100 | 3 Certifications named, HTTPS enforced with HSTS, Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| Dermanosticdermanostic.comSee also Transparency alternatives to Dermanostic | 22/100 | 3 HTTPS enforced with HSTS, No third-party tracking before consent, Named privacy contact | 3 Data location stated, Public pricing, security.txt (RFC 9116) | Compare |
| smart medicationsmart-medication.euSee also Transparency alternatives to smart medication | 22/100 | 3 HTTPS enforced with HSTS, No third-party tracking before consent, Named privacy contact | 3 Data location stated, Public pricing, security.txt (RFC 9116) | Compare |
| Vseevsee.comSee also Transparency alternatives to Vsee | 35/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| Luma Healthlumahealth.ioSee also Transparency alternatives to Luma Health | 30/100 | 2 Status page with history, HTTPS enforced with HSTS | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Doxy.medoxy.meSee also Transparency alternatives to Doxy.me | 26/100 | 2 Status page with history, HTTPS enforced with HSTS | 2 Data location stated, security.txt (RFC 9116) | Compare |
| Sprucesprucehealth.comSee also Transparency alternatives to Spruce | 26/100 | 2 Status page with history, HTTPS enforced with HSTS | 2 Data location stated, security.txt (RFC 9116) | Compare |
| Corepluscorepluspm.comSee also Transparency alternatives to Coreplus | 22/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 2 Data location stated, security.txt (RFC 9116) | Compare |
| Medgatemedgate.chSee also Transparency alternatives to Medgate | 18/100 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | 2 Data location stated, Public pricing | Compare |
| Sanvartissanvartis.deSee also Transparency alternatives to Sanvartis | 17/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 2 Data location stated, Public pricing | 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.