Transparency alternatives to Feedback Fish
Other Product feedback and updates vendors we measure, sorted by how much they publish that Feedback Fish does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 14 that differ from Feedback Fish on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Feedback Fish has 11 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and Feedback Fish does not” is the one that closes them.
| Vendor | Score | Publishes, and Feedback Fish does not | Feedback Fish publishes, and they do not | |
|---|---|---|---|---|
| AnnounceKitannouncekit.app | 61/100 | 6 Data processing agreement, Data location stated, Certifications named, +3 | nothing | Compare |
| ProductLiftproductlift.dev | 61/100 | 5 Data processing agreement, Subprocessor list, Data location stated, +2 | nothing | Compare |
| Releasedreleased.so | 57/100 | 5 Data processing agreement, Data location stated, Status page with history, +2 | nothing | Compare |
| Frillfrill.co | 48/100 | 4 Subprocessor list, Data location stated, HTTPS enforced with HSTS, +1 | nothing | Compare |
| Featurebasefeaturebase.app | 26/100 | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | nothing | Compare |
| Roadmaproadmap.space | 35/100 | 2 Data processing agreement, Data location stated | nothing | Compare |
| Upvotyupvoty.com | 30/100 | 2 Data location stated, HTTPS enforced with HSTS | nothing | Compare |
| Cannycanny.io | 23/100 | 2 Certifications named, HTTPS enforced with HSTS | nothing | Compare |
| Beamergetbeamer.com | 22/100 | 2 Certifications named, HTTPS enforced with HSTS | nothing | Compare |
| UserJotuserjot.com | 17/100 | 2 Status page with history, HTTPS enforced with HSTS | 1 Public pricing | Compare |
| Noticeablenoticeable.io | 13/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 1 Public pricing | Compare |
| Changelogfychangelogfy.com | 13/100 | 1 Named privacy contact | nothing | 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.