Transparency alternatives to IamResponding
Other Mass notification and critical events vendors we measure, sorted by how much we found at them and not at IamResponding. This is a comparison of disclosure, not of features or fitness.
12 shown of 37 that differ from IamResponding on at least one criterion we measured for both. Public transparency score, not a product or security rating.
IamResponding 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, security.txt (RFC 9116), Notice before subprocessors change. The column “Found there, not found at IamResponding” is the one that closes them.
| Vendor | Score | Found there, not found at IamResponding | Found at IamResponding, not found there | |
|---|---|---|---|---|
| AlertMediaalertmedia.comSee also Transparency alternatives to AlertMedia | 52/100 | 5 Subprocessor list, Status page with history, Certifications named, +2 | 1 Data location stated | Compare |
| Singlewiresinglewire.comSee also Transparency alternatives to Singlewire | 43/100 | 5 Subprocessor list, Status page with history, Uptime SLA with a figure, +2 | 2 Data location stated, Public pricing | Compare |
| Zellozello.comSee also Transparency alternatives to Zello | 39/100 | 4 Data processing agreement, Certifications named, HTTPS enforced with HSTS, +1 | 1 Data location stated | Compare |
| F24f24.comSee also Transparency alternatives to F24 | 35/100 | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | 1 Public pricing | Compare |
| Divera 247divera247.comSee also Transparency alternatives to Divera 247 | 26/100 | 3 HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116) | 2 Data location stated, Public pricing | Compare |
| Raptor Technologiesraptortech.comSee also Transparency alternatives to Raptor Technologies | 17/100 | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Data location stated, Public pricing | Compare |
| Juvarejuvare.comSee also Transparency alternatives to Juvare | 35/100 | 2 Subprocessor list, HTTPS enforced with HSTS | 1 Public pricing | Compare |
| D4Hd4h.comSee also Transparency alternatives to D4H | 26/100 | 2 Certifications named, HTTPS enforced with HSTS | 1 Public pricing | Compare |
| Rapid Recallrapidrecall.comSee also Transparency alternatives to Rapid Recall | 22/100 | 2 Certifications named, HTTPS enforced with HSTS | 1 Data location stated | Compare |
| Bryxbryx.comSee also Transparency alternatives to Bryx | 17/100 | 2 Status page with history, HTTPS enforced with HSTS | 2 Data location stated, Public pricing | Compare |
| Klaxonklaxon.ioSee also Transparency alternatives to Klaxon | 17/100 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | 2 Data location stated, Public pricing | Compare |
| Intradointrado.comSee also Transparency alternatives to Intrado | 13/100 | 2 Certifications named, HTTPS enforced with HSTS | 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.