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