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