Transparency alternatives to Rybbit
Other Web analytics vendors we measure, sorted by how much we found at them and not at Rybbit. This is a comparison of disclosure, not of features or fitness.
12 shown of 32 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 “Found there, not found at Rybbit” is the one that closes them.
| Vendor | Score | Found there, not found at Rybbit | Found at Rybbit, not found there | |
|---|---|---|---|---|
| Contentsquarecontentsquare.comSee also Transparency alternatives to Contentsquare | 61/100 | 4 Subprocessor list, Status page with history, Uptime SLA with a figure, +1 | 2 Data processing agreement, Data location stated | Compare |
| FullStoryfullstory.comSee also Transparency alternatives to FullStory | 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 |
| Mixpanelmixpanel.comSee also Transparency alternatives to Mixpanel | 78/100 | 3 Subprocessor list, Status page with history, security.txt (RFC 9116) | 1 Certifications named | Compare |
| PostHogposthog.comSee also Transparency alternatives to PostHog | 78/100 | 3 Subprocessor list, security.txt (RFC 9116), Named privacy contact | nothing | Compare |
| Amplitudeamplitude.comSee also Transparency alternatives to Amplitude | 74/100 | 3 Status page with history, security.txt (RFC 9116), Named privacy contact | nothing | Compare |
| Plausibleplausible.ioSee also Transparency alternatives to Plausible | 48/100 | 2 No third-party tracking before consent, Named privacy contact | 3 Public pricing, Certifications named, HTTPS enforced with HSTS | Compare |
| TelemetryDecktelemetrydeck.comSee also Transparency alternatives to TelemetryDeck | 43/100 | 2 security.txt (RFC 9116), Named privacy contact | 3 Public pricing, Certifications named, Notice before subprocessors change | Compare |
| Parse.lyparse.lySee also Transparency alternatives to Parse.ly | 39/100 | 2 Subprocessor list, Named privacy contact | 4 Data processing agreement, Public pricing, Certifications named, +1 | Compare |
| Pirschpirsch.ioSee also Transparency alternatives to Pirsch | 35/100 | 2 No third-party tracking before consent, Named privacy contact | 4 Data processing agreement, Certifications named, HTTPS enforced with HSTS, +1 | Compare |
| Chartbeatchartbeat.comSee also Transparency alternatives to Chartbeat | 30/100 | 2 Status page with history, Named privacy contact | 4 Data processing agreement, Public pricing, HTTPS enforced with HSTS, +1 | Compare |
| Quantcastquantcast.comSee also Transparency alternatives to Quantcast | 26/100 | 2 Status page with history, Named privacy contact | 5 Data processing agreement, Public pricing, Certifications named, +2 | 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 |
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.