Channel Moderator Code of Conduct
This Code binds channel moderators and deputy moderators only. It does not bind ordinary users; their obligations are in the Terms of Use. It is published in full and readable by anyone, whether or not they hold the role.
Last updated: 2026-08-22 · Version: 2026-08-22-v2
Read these six first
- The role is a delegation, not a possession: the operator can withdraw it at any time, with or without a reason, and without notice (Section 3).
- There is no pay of any kind, and nothing you do in the role becomes a claim for payment (Section 4).
- You must give a reason for every action you take against a person's content or account, in words that person can understand; the screen asks for it and the person is sent what you wrote (Section 5).
- What you see in the role — reports, and the identifiers attached to them — stays with you, and that obligation continues after the role ends (Section 7).
- You are a person handling other people's personal data under Korean law while you hold the role, with the duties in Section 11.
- This Code has versions. When it changes you must accept the new one, your acceptance expires after twelve months in any case, and until you accept the moderator tools do not work (Sections 2, 10 and 11).
1. What this document is
This Code of Conduct sets out what a channel moderator and a deputy moderator agree to when they take the role. It sits below the Terms of Use and the Privacy Policy. Where this Code and the Terms differ, the Terms prevail. Accepting this Code does not replace, limit, or extend the Terms.
2. Who it binds
It binds every channel moderator and every deputy moderator, from the moment they accept it until the moment the role ends. A person who has not accepted the current version cannot use any moderator tool: every control the role carries is refused until they accept. Publishing a new version therefore stops a moderator acting until they accept that version. The obligations in sections 7 and 8 continue after the role ends.
3. The role is a delegation, not a property
The role is permission to use certain tools inside one channel. It is not ownership of the channel, not a title, and not a position. The operator may withdraw it at any time, with or without a reason, and without notice. Withdrawal is not a penalty and carries no finding of fault unless one is separately stated. Holding the role creates no employment, no service contract, no partnership, and no agency between the holder and the operator. It creates no right to hold the role, no right to keep it for any period, and no claim of any kind arising from its withdrawal.
4. There is no compensation
The role is unpaid. The operator does not owe money, goods, or any other thing of value for work done in the role, and nothing done in the role creates a debt. Where the service grants recognition to people in the role, that recognition is a feature of the service, not payment, and it may be changed or removed at any time.
5. What a moderator agrees to do
Apply the Terms of Use and the rules of the channel evenly, to every person. Act only within the channel the role covers, and only with the tools given for it. Give a reason for every action taken against a person's content or account, in words that person can understand. The screen asks for one before it will hide anything, and what you write is sent to that person with the notice telling them what was done. Step aside from a decision that concerns the moderator personally — their own post, their own dispute, or a person they are close to — and hand it to the operator. Pass on to the operator anything that looks like a threat to a person's safety, or anything that looks unlawful, rather than handling it alone.
6. What a moderator agrees not to do
Not to use the role for private benefit — their own, or that of anyone they are close to. Not to go easy on some people and hard on others. Friendship, dislike, a shared group, or a past dispute are not reasons to decide differently. Not to trade the role — not to sell it, rent it, lend it, share the account that holds it, or promise it to anyone. Not to use moderator tools to settle an argument they are part of. Not to punish a person for reporting the moderator, for evaluating the moderator, or for asking the operator to review a decision. Not to hold out as speaking for the operator or for the service.
7. What a moderator sees stays with the moderator
The role gives sight of things ordinary users cannot see, including reports and the identifiers attached to them. The moderator agrees to use what they see only to do the work of the role, and not to publish it, pass it on, or use it for anything else. This obligation continues after the role ends. If the moderator receives a demand from anyone claiming legal authority, they pass it to the operator instead of answering it.
8. Deputies, and what a moderator carries for them
The operator appoints and removes channel moderators and deputy moderators. A channel moderator cannot appoint a deputy; if that ever changes, this Code changes with it and everyone re-accepts. A channel moderator answers for their own use of the role. Where a deputy misuses the role, the channel moderator's role ends as well only where the channel moderator was at fault in supervising them — not automatically and not merely because the two worked in the same channel. This is a ground for withdrawing a delegation; it is not a transfer of liability, and it does not make either person liable to the other or to any third party.
9. How the role ends
The role ends when the operator withdraws it, when the holder resigns, when the account is suspended or closed, or when the channel is closed. When a channel moderator's role ends, deputies keep their roles until the operator decides otherwise. Ending the role does not delete anything the person posted, and does not delete the record of the appointment and its end. That record is not published: it is kept where the operator can see it, and the Service shows only who currently holds a role in a channel. The reason for an ending is not published either. If the account is deleted, the record goes with it, the same as everything else tied to the account.
10. Disagreeing, and changes to this Code
Anyone who believes a moderator has acted against this Code may report it to the operator through the channel the service provides for that purpose. A moderator whose role was withdrawn may ask the operator to look again; the operator is not obliged to restore the role. This Code has a version. When it changes, the operator publishes the new version and asks every current moderator to accept it again. Acceptance also expires on its own after twelve months, so a moderator accepts this Code at least once a year whether or not it has changed — Section 11 says why. A moderator who does not accept cannot continue in the role. Refusing has no other consequence.
11. Handling other people's personal data
While you hold the role you are, under the Republic of Korea Personal Information Protection Act, a person who handles personal data under the operator's direction. Article 28 of that Act puts two duties on the operator: to keep that group as small as possible and supervise it, and to give it the training it needs, regularly. This Section is that training, and accepting this Code is how it is recorded. Regularly means on a period, not on an event, so it is not enough to reissue it only when this Code changes: you accept it again whenever this Code changes and, in any case, at least once every twelve months. The Service enforces that — when your acceptance is twelve months old the moderator tools stop working until you accept again. What that means in practice, and each of these is an obligation, not advice. Use what you see only to do the work of the role. Nothing you see in a report — who made it, what it says, the identifier attached to it — is yours to use for anything else. Do not screenshot, copy out, or forward what you see, to anyone, inside or outside the Service. Do not put it on your own device or in your own notes. Read it where it lives. Never share the account that holds the role, and never let anyone else act through it. If you see something that looks like a leak — data showing where it should not, a screen showing you more than the role should reach — tell the operator immediately and do not investigate it yourself. When the role ends, you keep nothing. Anything you still hold, delete. Breaking any of this is a ground for withdrawing the role at once, and the duty in Section 7 continues after that.