Moderation and safety, designed in from the start

Quiet by default helps moderators

Many moderation problems start as attention problems: too many rooms, too many pings, too little time. A For you inbox that surfaces mentions and reports first lets a moderator spot what needs action without monitoring every channel.

Roles and permissions

Servers will have roles, so owners can decide who may do what.

• Who can create rooms, post in announcement channels or share a screen.
• Who can mute, remove or ban a member.
• Which channels are private and to whom.
• Who can edit the server homepage.

Reports and records

Members will be able to report a message or a person, and reports reach the moderators of that server. A log of moderation actions will let teams see what was done and by whom, which keeps decisions accountable.

Voice transcripts are text and can be reported like any message. Reporting a spoken moment in a live room is more difficult, and the design for it is still being worked out.

Privacy in screen sharing

The screen share studio includes blur boxes so people can keep private regions off the stream. This protects the person sharing as well as anyone whose details might otherwise appear.

Looking after the people who look after it

Moderators are often volunteers, and the work is tiring when the tools are blunt. The design aim is to make the routine parts light: clear roles, a record of what was done and why, and quiet defaults that mean fewer things go wrong in the first place. A calm app should not need constant firefighting to stay calm.

Reports are meant to reach the right people with the right context, and to leave a trail so that decisions can be reviewed. A member who is removed should be able to understand why, and a moderator who made a mistake should be able to fix it.

What the website already commits to

Even before the app exists, there are rules for this site. The acceptable use page sets out what is not allowed here and how to report a problem, and the copyright page describes how takedown requests are handled. Both are drafts pending legal review.

The harder questions, such as how to handle illegal content in private spaces and how appeals work, are open. We list them on this page so that nobody mistakes silence for an answer. They will be answered, in public, before the app opens.

Honesty about what software can do

No set of tools makes a community safe by itself. Software can make good moderation easier and bad behaviour harder, but it cannot replace judgement, and it will sometimes make mistakes. We would rather tell you that than present a feature list as if it solved the problem. The moderation work in Yappio is meant to support people, not to automate them away.

Open questions we will answer before launch

Age requirements, data retention for transcripts, how reports are handled across servers and what the platform itself will and will not moderate are all decisions still to be written down. They will be published as plain-language policies, not hidden in a terms page.