Transparency alternatives to F24
Other Mass notification and critical events vendors we measure, sorted by how much we found at them and not at F24. This is a comparison of disclosure, not of features or fitness.
12 shown of 38 that differ from F24 on at least one criterion we measured for both. Public transparency score, not a product or security rating.
F24 has 7 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Public pricing, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change. The column “Found there, not found at F24” is the one that closes them.
| Vendor | Score | Found there, not found at F24 | Found at F24, not found there | |
|---|---|---|---|---|
| AlertMediaalertmedia.comSee also Transparency alternatives to AlertMedia | 52/100 | 4 Subprocessor list, Status page with history, Public pricing, +1 | 3 Data location stated, security.txt (RFC 9116), Named privacy contact | Compare |
| Singlewiresinglewire.comSee also Transparency alternatives to Singlewire | 43/100 | 4 Subprocessor list, Status page with history, Uptime SLA with a figure, +1 | 4 Data location stated, Certifications named, security.txt (RFC 9116), +1 | Compare |
| Zellozello.comSee also Transparency alternatives to Zello | 39/100 | 2 Data processing agreement, Public pricing | 2 Data location stated, Named privacy contact | Compare |
| GroupAlarmgroupalarm.comSee also Transparency alternatives to GroupAlarm | 22/100 | 2 Status page with history, Public pricing | 4 Data location stated, Certifications named, HTTPS enforced with HSTS, +1 | Compare |
| Juvarejuvare.comSee also Transparency alternatives to Juvare | 35/100 | 1 Subprocessor list | 3 Certifications named, security.txt (RFC 9116), Named privacy contact | Compare |
| Divera 247divera247.comSee also Transparency alternatives to Divera 247 | 26/100 | 1 No third-party tracking before consent | 2 Data location stated, Certifications named | Compare |
| IamRespondingiamresponding.comSee also Transparency alternatives to IamResponding | 23/100 | 1 Public pricing | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Active911active911.comSee also Transparency alternatives to Active911 | 22/100 | 1 Public pricing | 4 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | Compare |
| Mobile Text Alertsmobile-text-alerts.comSee also Transparency alternatives to Mobile Text Alerts | 22/100 | 1 Public pricing | 3 Data location stated, Certifications named, security.txt (RFC 9116) | Compare |
| Rapid Recallrapidrecall.comSee also Transparency alternatives to Rapid Recall | 22/100 | 1 Public pricing | 3 Data location stated, security.txt (RFC 9116), Named privacy contact | Compare |
| Bryxbryx.comSee also Transparency alternatives to Bryx | 17/100 | 1 Status page with history | 4 Data location stated, Certifications named, security.txt (RFC 9116), +1 | Compare |
| CallingPostcallingpost.comSee also Transparency alternatives to CallingPost | 17/100 | 1 Public pricing | 4 Data location stated, Certifications named, security.txt (RFC 9116), +1 | 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.