Transparency alternatives to Action1
Other Endpoint management and security vendors we measure, sorted by how much we found at them and not at Action1. This is a comparison of disclosure, not of features or fitness.
12 shown of 37 that differ from Action1 on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Action1 has 6 gaps in what we could measure: Subprocessor list, Data location stated, Status page with history, Uptime SLA with a figure, No third-party tracking before consent, Named privacy contact. The column “Found there, not found at Action1” is the one that closes them.
| Vendor | Score | Found there, not found at Action1 | Found at Action1, not found there | |
|---|---|---|---|---|
| Addigyaddigy.comSee also Transparency alternatives to Addigy | 87/100 | 5 Subprocessor list, Data location stated, Status page with history, +2 | 1 security.txt (RFC 9116) | Compare |
| Malwarebytesmalwarebytes.comSee also Transparency alternatives to Malwarebytes | 83/100 | 4 Subprocessor list, Data location stated, Status page with history, +1 | 1 Certifications named | Compare |
| NinjaOneninjaone.comSee also Transparency alternatives to NinjaOne | 52/100 | 3 Data location stated, Status page with history, Named privacy contact | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Hexnodehexnode.comSee also Transparency alternatives to Hexnode | 62/100 | 2 Subprocessor list, Named privacy contact | 2 Certifications named, security.txt (RFC 9116) | Compare |
| Levellevel.ioSee also Transparency alternatives to Level | 61/100 | 2 Subprocessor list, Data location stated | 1 Data processing agreement | Compare |
| Esperesper.ioSee also Transparency alternatives to Esper | 52/100 | 2 Data location stated, Named privacy contact | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| SentinelOnesentinelone.comSee also Transparency alternatives to SentinelOne | 48/100 | 2 Status page with history, Named privacy contact | 1 Data processing agreement | Compare |
| Automoxautomox.comSee also Transparency alternatives to Automox | 43/100 | 2 Uptime SLA with a figure, Named privacy contact | 2 security.txt (RFC 9116), Notice before subprocessors change | Compare |
| Scalefusionscalefusion.comSee also Transparency alternatives to Scalefusion | 43/100 | 2 Data location stated, Named privacy contact | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Fleetfleetdm.comSee also Transparency alternatives to Fleet | 39/100 | 2 Data location stated, Named privacy contact | 3 Data processing agreement, security.txt (RFC 9116), Notice before subprocessors change | Compare |
| Kaseyakaseya.comSee also Transparency alternatives to Kaseya | 39/100 | 2 Subprocessor list, Status page with history | 4 Data processing agreement, Public pricing, Certifications named, +1 | Compare |
| PDQ Connectpdq.comSee also Transparency alternatives to PDQ Connect | 30/100 | 2 Status page with history, Named privacy contact | 3 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change | 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.