Transparency alternatives to Swetrix
Other Web analytics vendors we measure, sorted by how much we found at them and not at Swetrix. This is a comparison of disclosure, not of features or fitness.
12 shown of 32 that differ from Swetrix on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Swetrix has 6 gaps in what we could measure: Subprocessor list, Status page with history, Certifications named, Uptime SLA with a figure, security.txt (RFC 9116), Named privacy contact. The column “Found there, not found at Swetrix” is the one that closes them.
| Vendor | Score | Found there, not found at Swetrix | Found at Swetrix, not found there | |
|---|---|---|---|---|
| Contentsquarecontentsquare.comSee also Transparency alternatives to Contentsquare | 61/100 | 5 Subprocessor list, Status page with history, Certifications named, +2 | 3 Data processing agreement, Data location stated, No third-party tracking before consent | Compare |
| FullStoryfullstory.comSee also Transparency alternatives to FullStory | 57/100 | 5 Subprocessor list, Status page with history, Certifications named, +2 | 4 Data processing agreement, Public pricing, No third-party tracking before consent, +1 | Compare |
| PostHogposthog.comSee also Transparency alternatives to PostHog | 78/100 | 4 Subprocessor list, Certifications named, security.txt (RFC 9116), +1 | 1 No third-party tracking before consent | Compare |
| Amplitudeamplitude.comSee also Transparency alternatives to Amplitude | 74/100 | 4 Status page with history, Certifications named, security.txt (RFC 9116), +1 | 1 No third-party tracking before consent | Compare |
| Mixpanelmixpanel.comSee also Transparency alternatives to Mixpanel | 78/100 | 3 Subprocessor list, Status page with history, security.txt (RFC 9116) | 1 No third-party tracking before consent | Compare |
| Chartbeatchartbeat.comSee also Transparency alternatives to Chartbeat | 30/100 | 3 Status page with history, Certifications named, Named privacy contact | 5 Data processing agreement, Public pricing, HTTPS enforced with HSTS, +2 | Compare |
| Umamiumami.isSee also Transparency alternatives to Umami | 57/100 | 2 Subprocessor list, Certifications named | 2 Data location stated, No third-party tracking before consent | Compare |
| Matomomatomo.orgSee also Transparency alternatives to Matomo | 52/100 | 2 Certifications named, Named privacy contact | 2 No third-party tracking before consent, Notice before subprocessors change | Compare |
| TelemetryDecktelemetrydeck.comSee also Transparency alternatives to TelemetryDeck | 43/100 | 2 security.txt (RFC 9116), Named privacy contact | 3 Public pricing, No third-party tracking before consent, 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, No third-party tracking before consent, +1 | Compare |
| Cabinwithcabin.comSee also Transparency alternatives to Cabin | 30/100 | 2 Certifications named, security.txt (RFC 9116) | 4 Data processing agreement, HTTPS enforced with HSTS, No third-party tracking before consent, +1 | Compare |
| Heapheap.ioSee also Transparency alternatives to Heap | 30/100 | 2 Status page with history, Certifications named | 4 Data processing agreement, Data location stated, No third-party tracking before consent, +1 | 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.