Transparency alternatives to eSchedule
Other Emergency medical services vendors we measure, sorted by how much we found at them and not at eSchedule. This is a comparison of disclosure, not of features or fitness.
12 shown of 22 that differ from eSchedule on at least one criterion we measured for both. Public transparency score, not a product or security rating.
eSchedule 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, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “Found there, not found at eSchedule” is the one that closes them.
| Vendor | Score | Found there, not found at eSchedule | Found at eSchedule, not found there | |
|---|---|---|---|---|
| AngelTrackangeltrack.comSee also Transparency alternatives to AngelTrack | 30/100 | 3 Data location stated, Public pricing, HTTPS enforced with HSTS | 1 No third-party tracking before consent | Compare |
| Julotajulota.comSee also Transparency alternatives to Julota | 30/100 | 3 Data location stated, Status page with history, HTTPS enforced with HSTS | 1 No third-party tracking before consent | Compare |
| Pulsarapulsara.comSee also Transparency alternatives to Pulsara | 22/100 | 3 Status page with history, HTTPS enforced with HSTS, Named privacy contact | 1 No third-party tracking before consent | Compare |
| Tablet Commandtabletcommand.comSee also Transparency alternatives to Tablet Command | 17/100 | 2 Status page with history, HTTPS enforced with HSTS | 1 No third-party tracking before consent | Compare |
| ImageTrendimagetrend.comSee also Transparency alternatives to ImageTrend | 13/100 | 2 Uptime SLA with a figure, HTTPS enforced with HSTS | 1 No third-party tracking before consent | Compare |
| Priority Dispatchprioritydispatch.netSee also Transparency alternatives to Priority Dispatch | 13/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 1 No third-party tracking before consent | Compare |
| Zoll Datazolldata.comSee also Transparency alternatives to Zoll Data | 13/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 1 No third-party tracking before consent | Compare |
| AIM EMS Softwareaim-system.comSee also Transparency alternatives to AIM EMS Software | 9/100 | 1 HTTPS enforced with HSTS | 1 No third-party tracking before consent | Compare |
| Beyond Lucidbeyondlucid.comSee also Transparency alternatives to Beyond Lucid | 9/100 | 1 HTTPS enforced with HSTS | 1 No third-party tracking before consent | Compare |
| Emergency Reportingemergencyreporting.comSee also Transparency alternatives to Emergency Reporting | 9/100 | 1 HTTPS enforced with HSTS | 1 No third-party tracking before consent | Compare |
| ESOeso.comSee also Transparency alternatives to ESO | 9/100 | 1 HTTPS enforced with HSTS | 1 No third-party tracking before consent | Compare |
| First Duefirstdue.comSee also Transparency alternatives to First Due | 9/100 | 1 HTTPS enforced with HSTS | 1 No third-party tracking before consent | 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.