Transparency alternatives to Short.io
Other Marketing attribution vendors we measure, sorted by how much we found at them and not at Short.io. 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 7 gaps in what we could measure: Data processing agreement, Subprocessor list, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Short.io” is the one that closes them.
| Vendor | Score | Found there, not found at Short.io | Found at Short.io, not found there | |
|---|---|---|---|---|
| Cometlycometly.comSee also Transparency alternatives to Cometly | 65/100 | 5 Data processing agreement, Subprocessor list, Certifications named, +2 | 3 Status page with history, Public pricing, security.txt (RFC 9116) | Compare |
| Dubdub.coSee also Transparency alternatives to Dub | 52/100 | 4 Data processing agreement, Uptime SLA with a figure, Notice before subprocessors change, +1 | 2 Data location stated, Status page with history | Compare |
| Tealiumtealium.comSee also Transparency alternatives to Tealium | 39/100 | 4 Subprocessor list, Certifications named, Notice before subprocessors change, +1 | 4 Data location stated, Status page with history, Public pricing, +1 | Compare |
| Supermetricssupermetrics.comSee also Transparency alternatives to Supermetrics | 65/100 | 3 Subprocessor list, Certifications named, Named privacy contact | nothing | Compare |
| AppsFlyerappsflyer.comSee also Transparency alternatives to AppsFlyer | 50/100 | 3 Subprocessor list, Uptime SLA with a figure, Named privacy contact | 1 Data location stated | Compare |
| Clarisightsclarisights.comSee also Transparency alternatives to Clarisights | 43/100 | 3 Data processing agreement, Certifications named, Named privacy contact | 3 Status page with history, Public pricing, security.txt (RFC 9116) | Compare |
| Factors.aifactors.aiSee also Transparency alternatives to Factors.ai | 43/100 | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | 3 Data location stated, Status page with history, security.txt (RFC 9116) | Compare |
| Stapestape.ioSee also Transparency alternatives to Stape | 39/100 | 3 Data processing agreement, Uptime SLA with a figure, Named privacy contact | 3 Data location stated, Status page with history, security.txt (RFC 9116) | Compare |
| Analyzifyanalyzify.comSee also Transparency alternatives to Analyzify | 57/100 | 2 Data processing agreement, Notice before subprocessors change | 1 Status page with history | Compare |
| ReportGardenreportgarden.comSee also Transparency alternatives to ReportGarden | 50/100 | 2 Subprocessor list, Named privacy contact | 1 Status page with history | Compare |
| HockeyStackhockeystack.comSee also Transparency alternatives to HockeyStack | 43/100 | 2 Data processing agreement, Notice before subprocessors change | 3 Status page with history, Public pricing, security.txt (RFC 9116) | Compare |
| Northbeamnorthbeam.ioSee also Transparency alternatives to Northbeam | 43/100 | 2 Subprocessor list, Notice before subprocessors change | 3 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116) | 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.