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