Named privacy contact in Product feedback and updates
"Contact us" is not a privacy contact. A named officer or a dedicated address is.
3 of 15 companies we measured here publish it, that is 20%. Last checked 2026-09-13.
20% here against 36% across every category we measure. Product feedback and updates sits below the overall share for this criterion.
This page counts companies, not product entries: a company with two products in this category is one company here and two rows below.
Back to Named privacy contact across all categories, or to Product feedback and updates.
Published
A data protection officer or a dedicated privacy address is named.
| Vendor | What we found |
|---|---|
| AnnounceKit | https://announcekit.app/privacy-policy |
| Changelogfy | https://changelogfy.com/privacy |
| Frill | https://frill.co/legal/privacy-policy |
No named privacy contact found.
We reached at least one address for each of these vendors and none of them carried it. That is what we found at the addresses we checked, on the date we checked them, and not a statement about what the vendor has.
| Vendor | What we found |
|---|---|
| Beamer | 7 addresses checked |
| Canny | 7 addresses checked |
| Changemap | 7 addresses checked |
| Featurebase | 7 addresses checked |
| Feedback Fish | 7 addresses checked |
| LoopedIn | 7 addresses checked |
| Noticeable | 7 addresses checked |
| ProductLift | 7 addresses checked |
| Released | 7 addresses checked |
| Roadmap | 7 addresses checked |
| Upvoty | 7 addresses checked |
| UserJot | 7 addresses checked |
Not measured
We could not look at these, or their robots.txt asks us not to. That says something about our measurement, not about them, and they are left out of the percentage above.
None. Every vendor here was measured for this criterion.
Found something we missed? Tell us. A correction moves that vendor into our next nightly run. That run reads the same fixed addresses we check for every vendor, not the address you send.