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