Transparency alternatives to Trackpac
Other IoT platforms and connectivity vendors we measure, sorted by how much they publish that Trackpac does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 44 that differ from Trackpac on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Trackpac has 10 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, 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 “publishes and Trackpac does not” is the one that closes them.
| Vendor | Score | Publishes, and Trackpac does not | Trackpac publishes, and they do not | |
|---|---|---|---|---|
| Balenabalena.io | 65/100 | 6 Data processing agreement, Subprocessor list, Status page with history, +3 | 1 Named privacy contact | Compare |
| Memfaultmemfault.com | 57/100 | 5 Data location stated, Status page with history, Certifications named, +2 | nothing | Compare |
| Particleparticle.io | 48/100 | 4 Data location stated, Status page with history, HTTPS enforced with HSTS, +1 | nothing | Compare |
| Datacakedatacake.co | 39/100 | 3 Data location stated, HTTPS enforced with HSTS, No third-party tracking before consent | 1 Named privacy contact | Compare |
| EMnifyemnify.com | 35/100 | 3 Data location stated, Status page with history, HTTPS enforced with HSTS | 1 Public pricing | Compare |
| TagoIOtago.io | 35/100 | 3 Data processing agreement, Certifications named, Notice before subprocessors change | 1 Named privacy contact | Compare |
| Litmuslitmus.io | 32/100 | 3 Status page with history, Certifications named, HTTPS enforced with HSTS | 1 Named privacy contact | Compare |
| Mendermender.io | 30/100 | 3 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116) | 1 Named privacy contact | Compare |
| Qbeeqbee.io | 30/100 | 3 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116) | 1 Named privacy contact | Compare |
| Emteriaemteria.com | 30/100 | 2 Data location stated, HTTPS enforced with HSTS | 1 Named privacy contact | Compare |
| Onomondoonomondo.com | 30/100 | 2 Status page with history, HTTPS enforced with HSTS | nothing | Compare |
| Aerisaeris.com | 26/100 | 2 Data processing agreement, Notice before subprocessors change | 1 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.