Transparency alternatives to Mastodon
Other Customer communities vendors we measure, sorted by how much we found at them and not at Mastodon. This is a comparison of disclosure, not of features or fitness.
12 shown of 29 that differ from Mastodon on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Mastodon has 10 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Mastodon” is the one that closes them.
| Vendor | Score | Found there, not found at Mastodon | Found at Mastodon, not found there | |
|---|---|---|---|---|
| Bettermodebettermode.comSee also Transparency alternatives to Bettermode | 83/100 | 8 Data processing agreement, Subprocessor list, Data location stated, +5 | 1 No third-party tracking before consent | Compare |
| Discoursediscourse.orgSee also Transparency alternatives to Discourse | 61/100 | 6 Subprocessor list, Data location stated, Status page with history, +3 | 1 No third-party tracking before consent | Compare |
| Hivebritehivebrite.comSee also Transparency alternatives to Hivebrite | 52/100 | 6 Data processing agreement, Subprocessor list, Status page with history, +3 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | Compare |
| Mattermostmattermost.comSee also Transparency alternatives to Mattermost | 52/100 | 6 Subprocessor list, Data location stated, Status page with history, +3 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | Compare |
| Higher Logichigherlogic.comSee also Transparency alternatives to Higher Logic | 65/100 | 5 Data processing agreement, Subprocessor list, Data location stated, +2 | 1 No third-party tracking before consent | Compare |
| Circlecircle.soSee also Transparency alternatives to Circle | 61/100 | 5 Data processing agreement, Data location stated, Status page with history, +2 | 1 No third-party tracking before consent | Compare |
| Heartbeatheartbeat.chatSee also Transparency alternatives to Heartbeat | 52/100 | 5 Data processing agreement, Status page with history, Public pricing, +2 | 1 No third-party tracking before consent | Compare |
| Zapnitozapnito.comSee also Transparency alternatives to Zapnito | 43/100 | 4 Subprocessor list, Status page with history, Public pricing, +1 | 1 No third-party tracking before consent | Compare |
| Zulipzulip.comSee also Transparency alternatives to Zulip | 43/100 | 4 Data location stated, Status page with history, Public pricing, +1 | 1 No third-party tracking before consent | Compare |
| Flockflock.comSee also Transparency alternatives to Flock | 32/100 | 3 Status page with history, Public pricing, Certifications named | 1 No third-party tracking before consent | Compare |
| Rocket.Chatrocket.chatSee also Transparency alternatives to Rocket.Chat | 26/100 | 3 Status page with history, Certifications named, Named privacy contact | 1 No third-party tracking before consent | Compare |
| Twisttwist.comSee also Transparency alternatives to Twist | 26/100 | 3 Public pricing, security.txt (RFC 9116), Named privacy contact | 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.