Transparency alternatives to LogSnag
Other Web analytics vendors we measure, sorted by how much they publish that LogSnag does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 31 that differ from LogSnag on at least one criterion we measured for both. Public transparency score, not a product or security rating.
LogSnag has 11 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, Named privacy contact. The column “publishes and LogSnag does not” is the one that closes them.
| Vendor | Score | Publishes, and LogSnag does not | LogSnag publishes, and they do not | |
|---|---|---|---|---|
| PostHogposthog.com | 78/100 | 8 Data processing agreement, Subprocessor list, Data location stated, +5 | nothing | Compare |
| Amplitudeamplitude.com | 74/100 | 8 Data processing agreement, Data location stated, Status page with history, +5 | nothing | Compare |
| Mixpanelmixpanel.com | 78/100 | 7 Data processing agreement, Subprocessor list, Data location stated, +4 | nothing | Compare |
| Contentsquarecontentsquare.com | 61/100 | 7 Subprocessor list, Status page with history, Certifications named, +4 | nothing | Compare |
| FullStoryfullstory.com | 57/100 | 7 Subprocessor list, Data location stated, Status page with history, +4 | 1 Public pricing | Compare |
| Swetrixswetrix.com | 61/100 | 5 Data processing agreement, Data location stated, HTTPS enforced with HSTS, +2 | nothing | Compare |
| Rybbitrybbit.com | 57/100 | 5 Data processing agreement, Data location stated, Certifications named, +2 | nothing | Compare |
| Fathom Analyticsusefathom.com | 52/100 | 5 Data processing agreement, Certifications named, HTTPS enforced with HSTS, +2 | nothing | Compare |
| Matomomatomo.org | 52/100 | 5 Data processing agreement, Data location stated, Certifications named, +2 | nothing | Compare |
| Mouseflowmouseflow.com | 48/100 | 5 Data processing agreement, Data location stated, HTTPS enforced with HSTS, +2 | 1 Public pricing | Compare |
| Plausibleplausible.io | 48/100 | 5 Data processing agreement, Data location stated, No third-party tracking before consent, +2 | 1 Public pricing | Compare |
| TelemetryDecktelemetrydeck.com | 43/100 | 5 Data processing agreement, Data location stated, HTTPS enforced with HSTS, +2 | 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.