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