Kagibeh Here's a good example from the front page of KagiFeedback.org today. The user wants to be helpful by posting a screenshot of a SERP with a bug, but as a result, the user publicly reveals interest in this specific book and the corresponding topic. For example, is he dissatisfied with his job, looking to "quiet quit", etc.
That said, I'm not sure what the best solution is: it's not clear that making kagifeedback.org would necessarily address the privacy concerns even as it makes it harder for users to participate. My best effort at offering constructive feedback is to suggest that there is an extremely low-friction way to send a private bug report rather than posting publicly on kagifeedback.org. And that feature requests and bug reports where users aren't concerned about privacy can still be posted and discussed on the public kagifeedback.org forum.
For example, when clicking "Report a Bug" on the front page of kagifeedback.org there could be a radio button or option that allows a user to opt in to making the bug report public, along with a line explaining the benefit of doing so (higher visibility, the potential for it to get prioritized sooner if other users have a similar issue, etc.). The default would be private.
"Suggest a Feature" could stay public, or it could also have an option but be public by default.