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