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