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