Transparency alternatives to Cabin
Other Web analytics vendors we measure, sorted by how much we found at them and not at Cabin. This is a comparison of disclosure, not of features or fitness.
12 shown of 32 that differ from Cabin on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Cabin has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Cabin” is the one that closes them.
| Vendor | Score | Found there, not found at Cabin | Found at Cabin, not found there | |
|---|---|---|---|---|
| Mixpanelmixpanel.comSee also Transparency alternatives to Mixpanel | 78/100 | 5 Data processing agreement, Subprocessor list, Status page with history, +2 | 1 Certifications named | Compare |
| PostHogposthog.comSee also Transparency alternatives to PostHog | 78/100 | 5 Data processing agreement, Subprocessor list, HTTPS enforced with HSTS, +2 | nothing | Compare |
| Amplitudeamplitude.comSee also Transparency alternatives to Amplitude | 74/100 | 5 Data processing agreement, Status page with history, HTTPS enforced with HSTS, +2 | nothing | Compare |
| Contentsquarecontentsquare.comSee also Transparency alternatives to Contentsquare | 61/100 | 5 Subprocessor list, Status page with history, Uptime SLA with a figure, +2 | 1 Data location stated | Compare |
| Swetrixswetrix.comSee also Transparency alternatives to Swetrix | 61/100 | 4 Data processing agreement, HTTPS enforced with HSTS, No third-party tracking before consent, +1 | 2 Certifications named, security.txt (RFC 9116) | Compare |
| FullStoryfullstory.comSee also Transparency alternatives to FullStory | 57/100 | 4 Subprocessor list, Status page with history, HTTPS enforced with HSTS, +1 | 1 Public pricing | Compare |
| Umamiumami.isSee also Transparency alternatives to Umami | 57/100 | 4 Data processing agreement, Subprocessor list, HTTPS enforced with HSTS, +1 | 2 Data location stated, security.txt (RFC 9116) | Compare |
| Fathom Analyticsusefathom.comSee also Transparency alternatives to Fathom Analytics | 52/100 | 4 Data processing agreement, HTTPS enforced with HSTS, No third-party tracking before consent, +1 | 2 Data location stated, security.txt (RFC 9116) | Compare |
| Mouseflowmouseflow.comSee also Transparency alternatives to Mouseflow | 48/100 | 4 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change, +1 | 3 Public pricing, Certifications named, security.txt (RFC 9116) | Compare |
| Plausibleplausible.ioSee also Transparency alternatives to Plausible | 48/100 | 4 Data processing agreement, No third-party tracking before consent, Notice before subprocessors change, +1 | 3 Public pricing, Certifications named, security.txt (RFC 9116) | Compare |
| Rybbitrybbit.comSee also Transparency alternatives to Rybbit | 57/100 | 3 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change | 1 security.txt (RFC 9116) | Compare |
| Litlyxlitlyx.comSee also Transparency alternatives to Litlyx | 52/100 | 3 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change | 2 Certifications named, 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.