Safety

moned combines public standards, clear provider categories, reviewed capabilities, private reporting, and authorized review. Different concerns follow different routes because they involve different information and decision owners.

A report starts a review. It is not a public accusation, automatic proof, or a guarantee of a particular outcome.

Public review labels, provider categories, capability boundaries, and governed service records make expected scope visible before a session begins. The Marketplace standards and Expert standards state the conduct expected of participants.

People can privately report harassment, threats, discrimination, coercion, fraud, impersonation, misleading credentials, unsafe content, or pressure to bypass governed flows through the conduct reporting route.

A product defect belongs in product support. An owned booking or payment concern belongs in the transaction route. A vulnerability belongs in security disclosure.

Authorized reviewers assess the available information and may request more context. Reports, reporter identity, submitted evidence, and internal notes are not public profile or marketplace content. Access remains limited to people who need the information to review and act on the concern.

The appropriate owner can take a governed action, refer a transaction issue, or route a security or privacy concern to the team responsible for that domain. Eligible governed decisions can use the process described in Reporting and appeals.