Transparency alternatives to Short.io
Other Marketing attribution vendors we measure, sorted by how much they publish that Short.io does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 43 that differ from Short.io on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Short.io has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, Notice before subprocessors change, Named privacy contact. The column “publishes and Short.io does not” is the one that closes them.
| Vendor | Score | Publishes, and Short.io does not | Short.io publishes, and they do not | |
|---|---|---|---|---|
| Cometlycometly.com | 65/100 | 6 Data processing agreement, Subprocessor list, Certifications named, +3 | 3 Status page with history, Public pricing, security.txt (RFC 9116) | Compare |
| Dubdub.co | 52/100 | 5 Data processing agreement, Uptime SLA with a figure, HTTPS enforced with HSTS, +2 | 2 Data location stated, Status page with history | Compare |
| Tealiumtealium.com | 48/100 | 5 Subprocessor list, Certifications named, HTTPS enforced with HSTS, +2 | 3 Data location stated, Public pricing, security.txt (RFC 9116) | Compare |
| Supermetricssupermetrics.com | 65/100 | 4 Subprocessor list, Certifications named, HTTPS enforced with HSTS, +1 | nothing | Compare |
| AppsFlyerappsflyer.com | 50/100 | 4 Subprocessor list, Uptime SLA with a figure, HTTPS enforced with HSTS, +1 | 1 Data location stated | Compare |
| HockeyStackhockeystack.com | 48/100 | 4 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change, +1 | 3 Status page with history, Public pricing, security.txt (RFC 9116) | Compare |
| Clarisightsclarisights.com | 43/100 | 4 Data processing agreement, Certifications named, HTTPS enforced with HSTS, +1 | 3 Status page with history, Public pricing, security.txt (RFC 9116) | Compare |
| Factors.aifactors.ai | 43/100 | 4 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change, +1 | 3 Data location stated, Status page with history, security.txt (RFC 9116) | Compare |
| Stapestape.io | 30/100 | 4 Data processing agreement, Uptime SLA with a figure, HTTPS enforced with HSTS, +1 | 4 Data location stated, Status page with history, Public pricing, +1 | Compare |
| Analyzifyanalyzify.com | 57/100 | 3 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change | 1 Status page with history | Compare |
| Northbeamnorthbeam.io | 52/100 | 3 Subprocessor list, HTTPS enforced with HSTS, Notice before subprocessors change | 2 Status page with history, security.txt (RFC 9116) | Compare |
| ReportGardenreportgarden.com | 50/100 | 3 Subprocessor list, HTTPS enforced with HSTS, Named privacy contact | 1 Status page with history | 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.