Transparency alternatives to Featurebase
Other Product feedback and updates vendors we measure, sorted by how much we found at them and not at Featurebase. This is a comparison of disclosure, not of features or fitness.
12 shown of 12 that differ from Featurebase on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Featurebase has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Featurebase” is the one that closes them.
| Vendor | Score | Found there, not found at Featurebase | Found at Featurebase, not found there | |
|---|---|---|---|---|
| AnnounceKitannouncekit.appSee also Transparency alternatives to AnnounceKit | 61/100 | 4 Data processing agreement, Data location stated, Notice before subprocessors change, +1 | 1 security.txt (RFC 9116) | Compare |
| ProductLiftproductlift.devSee also Transparency alternatives to ProductLift | 61/100 | 4 Data processing agreement, Subprocessor list, Data location stated, +1 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Releasedreleased.soSee also Transparency alternatives to Released | 57/100 | 3 Data processing agreement, Data location stated, Status page with history | 1 Certifications named | Compare |
| Frillfrill.coSee also Transparency alternatives to Frill | 48/100 | 3 Subprocessor list, Data location stated, Named privacy contact | 2 Certifications named, security.txt (RFC 9116) | Compare |
| UserJotuserjot.comSee also Transparency alternatives to UserJot | 39/100 | 2 Data location stated, Status page with history | 2 Certifications named, security.txt (RFC 9116) | Compare |
| Roadmaproadmap.spaceSee also Transparency alternatives to Roadmap | 35/100 | 2 Data processing agreement, Data location stated | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Upvotyupvoty.comSee also Transparency alternatives to Upvoty | 30/100 | 1 Data location stated | 2 Certifications named, security.txt (RFC 9116) | Compare |
| Changelogfychangelogfy.comSee also Transparency alternatives to Changelogfy | 4/100 | 1 Named privacy contact | 4 Public pricing, Certifications named, HTTPS enforced with HSTS, +1 | Compare |
| Cannycanny.ioSee also Transparency alternatives to Canny | 23/100 | nothing we found there and not here | nothing | Compare |
| Beamergetbeamer.comSee also Transparency alternatives to Beamer | 22/100 | nothing we found there and not here | 1 security.txt (RFC 9116) | Compare |
| Noticeablenoticeable.ioSee also Transparency alternatives to Noticeable | 13/100 | nothing we found there and not here | 2 Public pricing, Certifications named | Compare |
| Feedback Fishfeedback.fishSee also Transparency alternatives to Feedback Fish | 9/100 | nothing we found there and not here | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | 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.