A safer way to write about work
Your experience deserves to be heard. Describe what happened and what could change, while protecting your privacy and the privacy of others.
No writing style can guarantee anonymity or prevent a complaint or legal dispute. Even without a name, details in a story can identify someone. Share only what you are comfortable making visible to other members.
1. Make identifying details less specific
Think about what a coworker could recognize from your account, not just what strangers would know.
- Role and team: Use a broad description instead of an exact job title, small team or unique responsibility when it is not necessary to the story.
- Dates and events: Avoid exact meeting dates, unusual incidents, project names and combinations of facts that point to one person.
- Writing style: Review distinctive phrases or details you have already shared at work. Changing your wording can help, but it does not guarantee anonymity.
2. Focus on your experience, not accusations
Constructive, first-hand feedback is easier to understand and respond to. You can describe a serious issue clearly without personal attacks.
- Describe the effect: Explain what you observed, how it affected your work and what change you would like to see. Separate facts from your interpretation.
- Avoid targeting people: Do not name or identify managers, colleagues, customers or applicants. Avoid insults, threats and unsupported claims about anyone's motives.
- Company name is optional: If naming a company is not necessary, you can post without one. Removing its name alone may not make the story anonymous.
3. Protect personal and confidential information
GDPR and Türkiye's KVKK protect personal data. Your post should not expose someone else's private information.
- Remove personal data: Leave out names, contact details, photos, identifying job details and sensitive information about other people.
- Do not upload records: Do not paste confidential documents, internal messages, screenshots, customer information or trade secrets into a post.
- Check before publishing: Automatic checks can miss details. Read the whole post once more, including its title and company label.
4. Understand what is and is not private
Only signed-in members can read posts here, but another member could still share what they saw elsewhere.
- Your account: Work-email accounts keep their address privately for sign-in and recovery; it is not displayed with posts. Invitation accounts do not require a real email.
- Your words: Posts are separated from your account identity, but your role, timing, workplace and story may still reveal who you are.
- Get advice when needed: If your situation involves a legal dispute, whistleblowing or sensitive evidence, consider speaking with a qualified professional before posting.
A constructive example
Instead of
“This company is terrible and its managers don't care about anyone.”
Try
“In my experience, changes to team priorities were communicated late, which made planning difficult. Earlier updates and a clear point of contact would help.”
Before you share
- Is this my first-hand experience?
- Could my wording identify me or someone else?
- Have I removed personal and confidential information?
- Is the change I want to see clear?
This guide is general information, not legal advice or a promise of anonymity. For details about how Feedback Owed handles data and content, read the privacy notice and community terms.