Transparency alternatives to Cliniko
Other Medical practice software vendors we measure, sorted by how much we found at them and not at Cliniko. This is a comparison of disclosure, not of features or fitness.
12 shown of 85 that differ from Cliniko on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Cliniko has 7 gaps in what we could measure: Data processing agreement, Subprocessor list, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Cliniko” is the one that closes them.
| Vendor | Score | Found there, not found at Cliniko | Found at Cliniko, not found there | |
|---|---|---|---|---|
| Nookalnookal.comSee also Transparency alternatives to Nookal | 78/100 | 4 Data processing agreement, Subprocessor list, Uptime SLA with a figure, +1 | nothing | Compare |
| Heidi Healthheidihealth.comSee also Transparency alternatives to Heidi Health | 52/100 | 3 Data processing agreement, security.txt (RFC 9116), Notice before subprocessors change | 2 Data location stated, Certifications named | Compare |
| Semblesemble.ioSee also Transparency alternatives to Semble | 39/100 | 2 Subprocessor list, Named privacy contact | 2 Data location stated, Public pricing | Compare |
| Doctenadoctena.comSee also Transparency alternatives to Doctena | 35/100 | 2 security.txt (RFC 9116), Named privacy contact | 2 Status page with history, Public pricing | Compare |
| Mira Healthmirahealth.careSee also Transparency alternatives to Mira Health | 26/100 | 2 Subprocessor list, Notice before subprocessors change | 4 Data location stated, Status page with history, Public pricing, +1 | Compare |
| Duriaduria.deSee also Transparency alternatives to Duria | 22/100 | 2 No third-party tracking before consent, security.txt (RFC 9116) | 4 Data location stated, Status page with history, Public pricing, +1 | Compare |
| Quincyfrey.deSee also Transparency alternatives to Quincy | 22/100 | 2 No third-party tracking before consent, Named privacy contact | 4 Data location stated, Status page with history, Public pricing, +1 | Compare |
| DAMPSOFTdampsoft.deSee also Transparency alternatives to DAMPSOFT | 17/100 | 2 security.txt (RFC 9116), Named privacy contact | 4 Data location stated, Status page with history, Public pricing, +1 | Compare |
| medatixxmedatixx.deSee also Transparency alternatives to medatixx | 17/100 | 2 security.txt (RFC 9116), Named privacy contact | 4 Data location stated, Status page with history, Public pricing, +1 | Compare |
| Arzt Direktarzt-direkt.deSee also Transparency alternatives to Arzt Direkt | 13/100 | 2 No third-party tracking before consent, Named privacy contact | 5 Data location stated, Status page with history, Public pricing, +2 | Compare |
| Dr. Flexdr-flex.deSee also Transparency alternatives to Dr. Flex | 13/100 | 2 No third-party tracking before consent, Named privacy contact | 5 Data location stated, Status page with history, Public pricing, +2 | Compare |
| jamedajameda.deSee also Transparency alternatives to jameda | 9/100 | 2 security.txt (RFC 9116), Named privacy contact | 5 Data location stated, Status page with history, Public pricing, +2 | 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.