Transparency alternatives to LogRx
Other Emergency medical services vendors we measure, sorted by how much they publish that LogRx does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 13 that differ from LogRx on at least one criterion we measured for both. Public transparency score, not a product or security rating.
LogRx 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, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and LogRx does not” is the one that closes them.
| Vendor | Score | Publishes, and LogRx does not | LogRx publishes, and they do not | |
|---|---|---|---|---|
| AngelTrackangeltrack.com | 30/100 | 2 Data location stated, Public pricing | nothing | Compare |
| Julotajulota.com | 30/100 | 2 Data location stated, Status page with history | nothing | Compare |
| Pulsarapulsara.com | 22/100 | 2 Status page with history, Named privacy contact | nothing | Compare |
| Tablet Commandtabletcommand.com | 17/100 | 1 Status page with history | nothing | Compare |
| ImageTrendimagetrend.com | 13/100 | 1 Uptime SLA with a figure | nothing | Compare |
| Priority Dispatchprioritydispatch.net | 13/100 | 1 Named privacy contact | nothing | Compare |
| Zoll Datazolldata.com | 13/100 | 1 Named privacy contact | nothing | Compare |
| eScheduleeschedule.com | 9/100 | 1 No third-party tracking before consent | 1 HTTPS enforced with HSTS | Compare |
| Carbynecarbyne.com | 4/100 | 1 Named privacy contact | 1 HTTPS enforced with HSTS | Compare |
| Traumasofttraumasoft.com | 4/100 | 1 Named privacy contact | 1 HTTPS enforced with HSTS | Compare |
| Zetronzetron.com | 4/100 | 1 Named privacy contact | 1 HTTPS enforced with HSTS | Compare |
| AIM EMS Softwareaim-system.com | 9/100 | nothing we found there and not here | 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.