---
title: "Code of Conduct - Discord Server | DonQuaan"
description: "Rules binding on every Member: conduct permitted and prohibited in all channels of the Server."
image: "https://donquaan.com/og-hero.png"
url: "https://donquaan.com/en/discord/rules"
lang: "en"
---

[DonQuaan Community Legal Framework](https://donquaan.com/en/discord)

CoC Code of Conduct

# Code of Conduct

Version 4.0 · Issued 11/08/2026 · Effective 18/08/2026 · Legacy ref: VK-02

# Code of Conduct

This English text is a courtesy translation. The Vietnamese version is the sole authoritative text (Article on Language).

The Code of Conduct (cite code CoC) is the internal normative instrument of the Discord Server "DonQuaan", identifier 1342729473245577267, and forms part of the [Community Legal Framework](https://donquaan.com/discord). This instrument lays down the standards of conduct, the scale of violation tiers and the enforcement principles applicable to every person participating in the Server. This instrument shall be binding by way of an accession contract: joining and taking part in the Server constitutes acceptance of the entire Legal Framework as published. This Code is published in the [official rules channel](https://discord.com/channels/1342729473245577267/1342766172000616490) and on the [Legal Framework publication page](https://donquaan.com/discord); a Member shall confirm having read and agreed to it through Discord Rules Screening before taking part.

---

### Article 0. Scope and rules of construction

0.1. This Code governs the activity of a community concerned with technology, artificial intelligence and personal development. This Code shall apply equally to every participating person, irrespective of role: new Members, long-standing Members, persons of influence, Staff and the Owner.

0.2. Three foundational principles govern the construction and application of this instrument as a whole: (a) no person shall be sanctioned in the absence of a rule written in advance, of traceable evidence and of an avenue of appeal; (b) no person shall be exempt - reputation, follower count, level of contribution, and relations with Staff or with the Owner shall not be a variable in any sanction, whether by way of aggravation or of mitigation; (c) the safety of persons shall take precedence over the reputation of the Server, over harmony, and over the convenience of any person whatsoever.

0.3. Relationship with the other instruments of the Legal Framework: overlapping areas shall be construed in accordance with the canonical instrument - discipline and evidentiary standards under ENF; the appeals procedure under APL; personal data and the logging regime under PRV; Official Channels and conditions of use under TOS; personnel arrangements under STF and OWN. In those areas this instrument merely cross-refers and shall not create detail departing from the canonical instrument.

0.4. The reference tables and the appendices annexed hereto have the value of finding aids. Where an appendix differs from the body of the instrument, the body shall prevail.

---

## CHAPTER I - GENERAL PROVISIONS

### Article 1. Scope of application, effect and hierarchy of norms

1.1. This Code shall apply to every individual participating in the Server (a Member), including ordinary Members, Members holding special roles, Staff and the Owner. Staff shall at the same time be governed by the Staff Policy (STF) at a standard higher than that applicable to ordinary Members.

1.2. The hierarchy of norms, in descending order of precedence: (a) the law of the Socialist Republic of Vietnam; (b) the [Discord Terms of Service](https://discord.com/terms) and the [Discord Community Guidelines](https://discord.com/guidelines); (c) this Code and the instruments annexed to it within the Legal Framework. No provision of this Code shall be construed so as to permit, condone or require conduct in breach of point (a) or point (b).

1.3. Safety-valve clause: any conduct prohibited by Vietnamese law or by Discord is prohibited on the Server, even where this Code does not restate it. The fact that this Code does not name a particular form of conduct shall not mean that such conduct is permitted.

1.4. No retroactivity: no person shall be sanctioned for conduct occurring before the corresponding provision entered into force, save for conduct already prohibited by Discord or by law at the time it was carried out. A gap in this Code shall be closed for the future; an abnormal advantage obtained through a gap may be annulled under Article 34.4, but the person who exploited it shall not be sanctioned where no prohibition existed at that time.

1.5. This Code may be amended only in accordance with Article 45. The version published in the Official Channels is the sole version in force.

### Article 2. Definitions

For the purposes of this Code:

2.1. Server: the sole official Discord server of the community - Server "DonQuaan", identifier 1342729473245577267 - together with its channels, events and subordinate spaces.

2.2. Official Channel: a closed list comprising the following points of contact (the full canon is contained in TOS): (a) the Discord Server "DonQuaan" (identifier 1342729473245577267); (b) the website donquaan.com - the place where the Legal Framework and authenticated announcements are published, at the [Legal Framework publication page](https://donquaan.com/discord); (c) the Single-Window Channel - the ticket channel for support, reports and appeals, which shall take precedence: [Single-Window Channel](https://discord.com/channels/1342729473245577267/1343099398720065559); (d) the official receiving e-mail addresses: [support@donquaan.com](mailto:support@donquaan.com) (support - ordinary response time 24 hours; matters requiring review: 1 to 3 days; complex cases: 3 to 7 days) · [private@donquaan.com](mailto:private@donquaan.com) (anonymous or sensitive intake) · [contact@donquaan.com](mailto:contact@donquaan.com) (general contact); (e) the sole official sending e-mail address: [notify@donquaan.com](mailto:notify@donquaan.com) (a proprietary domain, send-only, not receiving); that address is authenticated by SPF, DKIM and DMARC, the authentication standard being published in the [identity authentication annex](https://donquaan.com/discord/verify). Any e-mail purporting to act in the name of the Server sent from a free-mail address or from any other variant constitutes impersonation. The community has no secondary Server, no publicly announced backup Server and no channel of communication other than those in this list; Zalo, Messenger and every other platform are not Official Channels, and any place holding itself out as such constitutes impersonation. Direct messages are not an official support channel: a direct message shall be valid only where Staff have scheduled it in advance within a ticket; a Staff member who initiates a direct message to a Member outside the procedure commits a breach of the Staff Policy. Where the Server or Discord is disrupted (down, suspended or seized), an announcement in the name of the community shall have effect only where it is posted on the official website within this list; any "backup link" or "Server relocation" appearing elsewhere shall be presumed false.

2.3. Staff: a person granted an administrative or operational role through the official appointment procedure and publicly displayed by role. There are no undisclosed Staff. Transitional period: during the period in which there are no Staff, the Owner shall provisionally discharge the operational roles; mechanisms requiring several persons (two-person approval, panels and the like) shall be activated progressively in accordance with the recruitment roadmap and shall be announced in the [official announcements channel](https://discord.com/channels/1342729473245577267/1529782982016110642).

2.4. Direct message: a private message between accounts, lying outside the technical visibility of the Server.

2.5. Minor: a person under 18 years of age. Child: a person under 16 years of age under Vietnamese law. The Server shall at all times be presumed to have Minors present; all Content standards are set on that assumption.

2.6. Content: everything posted or transmitted within the Server - text, images, video, audio, files, emoji, stickers, display names, avatars, statuses, voice content, and content generated by a bot or by artificial intelligence at the instruction of a Member.

2.7. Context: the entirety of the circumstances surrounding a piece of Content - the conversational thread before and after, the relationship between the parties, the history of interaction, and the channel of posting. The assessment of a violation shall always rest on Context, in accordance with the standard laid down in Article 3.5.

2.8. Coordinated conduct: conduct by two or more accounts acting pursuant to a common script, agreement or call to action, identified in accordance with the criteria laid down in Article 27.2.

### Article 3. Violation tiers and principles of classification

3.1. Every violation under this Code shall be assigned one of four tiers:

| Tier | Default sanction range |
| --- | --- |
| LIGHT | Formal reminder entered in the record; removal or correction of Content; may be accompanied by a timeout of up to 1 hour |
| MEDIUM | Formal warning, removal of Content and a timeout or mute of 1 hour to 7 days; may include a temporary withdrawal of access to the channel concerned |
| HEAVY | Long-term mute; temporary ban of 7 days up to a permanent ban, according to the range set by the individual Article |
| RED | Immediate permanent ban (or a protective interim ban under the SOP), a report to Discord Trust and Safety, retention of the legal case record, and referral to or recommendation of referral to the competent authorities where the indicia are sufficient. No amnesty, no negotiation, no community consultation |

3.2. Repetition: three LIGHT violations within the same group in 30 days shall be treated as one MEDIUM violation. Five LIGHT violations across different groups within the same period shall likewise be treated as one MEDIUM violation. Two MEDIUM violations in 90 days shall be dealt with at the upper end of the MEDIUM range or reclassified as HEAVY. Repetition at HEAVY level following a temporary ban shall lead to a permanent ban.

3.3. Aggravating circumstances (a closed list, which may not be supplemented at the time of adjudication): (a) repetition of conduct within the same group; (b) targeting of a Minor or of a person in a vulnerable condition; (c) conduct that is coordinated, organised or carried out pursuant to a prepared script; (d) abuse of a position of trust (Staff, event organiser, holder of a special role); (e) wide dissemination or measurable actual harm; (f) continuation of the conduct after Staff have required it to stop.

3.4. Mitigating circumstances (a closed list): (a) a first violation accompanied by full cooperation; (b) voluntary removal or remedy before any sanction; (c) systematic provocation within the meaning of Article 10 - a substantial reduction, but not a complete exemption, since the circumstances reduce the sanction without erasing the conduct; (d) a violation committed in manifest good faith and not intended to cause harm (for example, posting an accident-warning image with good intent): dealt with at the bottom of the range, with priority given to educational measures; (e) a linguistic or translation misunderstanding verified in accordance with Article 7.6; (f) self-reporting before detection or immediately upon being warned, accompanied by an undertaking and by actual non-repetition: eligible for exemption or reduction; not applicable to the RED tier.

3.5. Standard for assessing Context - the understanding of an ordinary reader: for verbal conduct (disguised profanity, teen-code, spoonerisms, innuendo, sarcasm), a violation shall be established according to how an ordinary, good-faith Vietnamese reader would understand the matter in that Context; that determination shall not depend on whether a keyword appears in a filter list, and shall not permit Staff to infer malice without foundation. A sanction based on inference from Context shall be concluded by two independent Staff before it is carried out. Where only one Staff member is on duty, that Staff member may immediately apply interim measures (removal of Content, a short timeout, locking the topic); the finding and the formal sanction shall await confirmation by a second Staff member within 24 hours.

3.6. Factors prohibited from being treated as circumstances, whether in aggravation or in mitigation: the level of contribution to the Server, seniority, follower count, reputation online or offline, the level of financial support, personal relations with Staff or the Owner, and crowd pressure. The recognition of contributions belongs to a separate honours system, severed from the disciplinary system in every case; all information concerning roles, including contribution roles, is explained in the Server's role-introduction channel.

3.7. Good intent does not erase conduct. Intent shall be considered only within the framework of Article 3.4(d) and shall not in any circumstances reduce RED-tier conduct to a lower tier.

3.8. Limitation period for repetition: a LIGHT violation shall cease to be usable for the purposes of repetition or aggravation after 90 days without repetition; a MEDIUM violation after 6 months; a HEAVY violation after 12 months. A RED violation is not subject to any limitation period. Logs shall continue to be retained under the data policy (Article 43) in order to serve investigations into behavioural patterns and legal obligations, but a person whose limitation period has expired shall be treated as a person who has never offended when a new sanction is classified.

3.9. Default sanction ladder: for everyday violations, sanctions shall escalate along the ladder of warning (public or private, up to 3 occasions) → mute or timeout → heavy timeout → temporary ban → permanent ban. A person who self-reports and does not repeat the conduct shall be eligible for exemption or reduction under Article 3.4(f). Particularly serious violations (the RED tier) do not pass through this ladder: an immediate permanent ban together with monitoring for alternate accounts; an alternate account of a permanently banned person shall, upon detection or upon report and verification to the standard in Article 32.3, likewise be permanently banned (Article 32.2). The amnesty mechanism applies in accordance with Article 44; a RED sanction falling within the non-amnestiable group shall not be considered. Everyday sanctions shall by default be handled by Staff along this ladder. Special cases - matters within the special-log list in Article 43.1 or of a particularly serious or sensitive nature - shall be handled by the Owner or by senior Staff; Staff may not deal with a case of this kind unilaterally and alone.

### Article 4. Principles of enforcement

4.1. Only Staff may enforce this Code. A Member who discovers a violation has one obligation only: to report it through the [Single-Window Channel](https://discord.com/channels/1342729473245577267/1343099398720065559) (Article 2.2) or through Discord's report function. A single polite, good-faith reminder between Members does not constitute a violation. The conduct that is sanctioned is self-enforcement: publicly citing provisions in order to accuse, demanding in a domineering manner that another person delete a post, threatening that a report has been made in order to humiliate, or continuing to deal with another person after Staff have taken the matter in hand - a LIGHT violation; upon recurrence: MEDIUM. Confidential, good-faith reports are protected under Article 26.5.

4.2. No record, no sanction. Every sanction shall have a case record (the provision relied upon, the evidence, the person imposing it, the time) entered into the logging system before, or within 15 minutes after, it is carried out; for RED violations and emergencies: to be completed within 1 hour. Where a sanction is appealed and the record is incomplete, Staff shall have 24 hours to complete it from the system logs; if the core elements (the provision relied upon and Tier A or Tier B evidence) cannot be supplied, the sanction shall be annulled. Annulment for procedural error does not erase the conduct: the conduct may be re-adjudicated under the correct procedure on one occasion only; where a procedural error recurs in the same matter, the conduct may no longer be re-adjudicated.

4.3. The three-tier evidentiary standard (the detailed canon is contained in ENF): (a) Tier A - data exported by the system itself (the Discord audit log, bot logs bearing a message ID and a timestamp, Content still present on the Server): sufficient to found a sanction at any tier; (b) Tier B - a screenshot or recording supplied by one party together with at least one independent element of verification (a message ID capable of cross-reference, a witness outside the same relational group, matching metadata): sufficient to open an investigation and to apply interim measures; sufficient to found a sanction where several independent Tier B sources genuinely cross-corroborate; (c) Tier C - a single screenshot incapable of cross-reference, or an uncorroborated statement: sufficient only to record the matter and open an investigation, and never sufficient to found a sanction or to publish a name. The number of reports is not evidence: ten reports of identical content from accounts connected to one another shall count as a single source.

4.4. An interim measure is not a final determination. During an investigation Staff may apply interim measures (timeout, channel restriction, protective interim ban) and shall state expressly, in the words "INTERIM - not a final determination". An interim measure implies no finding of guilt and shall be deleted from the record where the conclusion is that no violation occurred.

4.5. Discreet handling is the default for every person. A sanction shall be notified privately to the person sanctioned; a serious sanction shall be announced to the community in a neutral template (conduct, provision, tier), without naming the person where this is not necessary, without humiliation and without sensational detail. This standard applies uniformly to Members, Staff and the Owner.

4.6. Every proceeding concerning a sanction shall take place in writing in a channel that leaves a trace. Staff shall not invite a Member into voice to discuss a sanction; Staff shall not initiate a direct message to a Member concerning a sanction outside the procedure (Articles 2.2 and 42.1). A Member who records or live-streams a disciplinary proceeding or the content of a restricted channel to the outside without consent commits a MEDIUM violation; where accompanied by harmful editing: HEAVY, under Article 37.

4.7. Crowd pressure is not procedure. Collective demands that a ban be imposed that day, countdowns and threats of mass departure shall not shorten the procedure by so much as an hour. Staff shall apply interim measures where necessary to de-escalate and shall reach a conclusion within the published time limits. Conversely, mobilising a crowd to exert pressure in order to overturn a particular sanction may constitute coordinated conduct under Article 27.

4.8. The power to freeze carries no finding of guilt: Staff on duty may lock a topic, enable slow mode and temporarily close a channel in order to de-escalate a conflict without accusing anyone. Having a topic locked is not a sanction and shall not be entered in a personal record.

4.9. Three instruments guaranteeing procedural fairness: (a) the informal reminder - the mildest instrument, used for minor first-time lapses (wrong channel, a slip of the tongue): not a sanction, not entered in the record, requiring no procedure. Staff are encouraged to use this instrument before applying any sanction at LIGHT tier; (b) the right to be heard before a heavy sanction: where the contemplated sanction is a long-term mute, or a HEAVY or RED sanction not falling within an emergency SOP (Articles 13, 23, 25 and 27), the person under consideration shall be notified and invited to make written representations before a conclusion is reached, within 24 hours in the case of a long-term mute and 48 hours in the case of a non-urgent HEAVY or RED sanction; interim measures may still be applied while that period runs. Silence or a refusal to make representations shall not be treated as an admission; (c) the heightened-defence mode: where there are indications of an attack or of abnormal growth, Staff may raise the verification level, enable server-wide slow mode and restrict the posting of links in accordance with predetermined defence levels governed by objective criteria published internally; this is a general safety measure, is not directed at any individual and requires no accusation.

### Article 5. Foundational declarations (confirmed by the Member upon joining)

5.1. The Server is not an exchange, a financial institution, a brokerage, a charitable organisation, a certifying training body, an employer, or the legal representative of any Member.

5.2. No person belonging to the Server - including the Owner - asks for money, charges fees, proposes bank transfers or requests the scanning of a QR code through direct messages or through any channel other than the officially published point, for any reason whatsoever; this rule is in force in perpetuity and admits of no exception. Any such message - including one accompanied by voice, video or images resembling the Owner or Staff - is a forgery or a fraud and shall be reported immediately.

5.3. Participation in the Server is a conditional and revocable licence. No person has any proprietary right in Member status, roles, levels, reward points or any virtual item; every contribution shall be recognised by way of honours but shall give rise to no right of ownership, co-ownership or indebtedness in relation to the Server.

5.4. Content that a Member voluntarily discloses within the Server (self-introduction, photographs, place of work) is a matter for the Member's own considered judgment and responsibility; the Server advises against posting a telephone number, an address, or a specific school or place of work. The aggregation of such information by another person in order to cause harm remains doxxing and shall be dealt with under Article 20.

5.5. Direct messages lie outside the technical visibility of the Server. The Server deals with conduct within the Server, issues proactive warnings and assists victims in reaching the competent authorities; the Server cannot read, cannot control and shall not compensate for content occurring in direct messages.

5.6. The Server does not organise, and does not permit the organisation of, charitable fundraising within the space of the Server. Personal fundraising appeals in Vietnam are governed by Nghị định 93/2021 (Decree on the mobilisation and use of voluntary contributions); every fundraising appeal within the Server - including one for charitable purposes - shall be removed together with an explanation, and the person appealing shall be directed to organisations having legal capacity to conduct such appeals. A Member wishing to engage in charitable work shall do so in a personal capacity, outside the name and the space of the Server.

---

## CHAPTER II - RULES OF RESPECT

### Article 6. Prohibition of personal attacks and toxic conduct

6.1. Insult, abuse, humiliation and derision directed at a person - the dignity, intelligence, appearance, living circumstances, occupation or family of another Member or of any identifiable individual, whether within or outside the Server - are prohibited. Tier: MEDIUM; where an aggravating circumstance is present or where several persons are targeted: HEAVY.

6.2. The prohibition in Article 6.1 applies to every form of expression: direct wording, teen-code, abbreviation, inserted characters, spoonerisms, metaphor, memes, emoji, reactions and mocking quotation - in accordance with the standard in Article 3.5. A defence that the statement was directed at some other object shall carry no weight where the Context shows the contrary.

6.3. Vigorous debate is permitted; personal attack is prohibited. The boundary: criticism of an argument, of source code, of a product or of an opinion is debate; moving to judgment of the person (personal ability, private life, employment status) is attack. In a two-sided conflict, both sides shall be dealt with symmetrically according to the conduct of each, and not according to the level of contribution of either.

6.4. Trash talk and coarse jokes between acquaintances in a shared channel: a Member bears responsibility for the fact that their content is read by everyone, including Minors. Coarse joking in a public part of the Server: LIGHT; a Staff member in breach shall be dealt with one tier higher under the Staff Policy.

6.5. Swearing and coarse language not directed at anyone: an informal reminder under Article 4.9(a) on the first occasion; a LIGHT sanction where it continues after the reminder; systematic repetition: MEDIUM.

### Article 7. Prohibition of discrimination and hate speech

7.1. Content that denigrates, derides, incites hatred against or discriminates on the basis of region or place of origin; ethnicity, race or nationality; sex, gender identity or sexual orientation; religion or belief; disability, health status or appearance; or socio-economic circumstances, is prohibited. Tier: HEAVY. Organised or repeated conduct, or the use of severe denigrating keywords: the upper end of the HEAVY range up to a permanent ban.

7.2. Regional discrimination - including but not limited to the keywords "parky", "nam cộng", "bắc kỳ" and "nam kỳ" used in a denigrating sense, and memes mimicking a regional accent in order to belittle - is prohibited, including in the guise of a joke and including where no direct victim speaks up. The list of prohibited keywords is published at the [Prohibited Keywords Annex](https://donquaan.com/discord/rules/banned-words) and pinned in the [official rules channel](https://discord.com/channels/1342729473245577267/1342766172000616490); the list is reviewed and updated each quarter together with the audit cycle. Tier: HEAVY. Self-deprecating humour about one's own region, not directed at anyone and not using prohibited keywords, does not constitute a violation, but Staff may lock the topic where they perceive a risk of escalation.

7.3. Sexist denigration in professional discussion or in voice: MEDIUM for an isolated first statement; where repeated, joined in collectively, or persistently directed at one person: HEAVY, with Article 8 also to be considered.

7.4. Discussion of a belief is not the same as attacking those who hold it. Academic and neutral exchange concerning religion, philosophy and spirituality is permitted in the appropriate channel; describing a religion as an instrument of fraud, describing atheists as immoral, or deriding sacred rites or symbols: HEAVY, given the risk of legal escalation concerning offence to religious belief. Staff may lock a religious or spiritual topic at any time without sanctioning anyone.

7.5. Hate speech directed at a group within the meaning of the [Discord Community Guidelines](https://discord.com/guidelines) (hate speech, hate symbols): HEAVY to RED according to gravity, together with a report to Discord.

7.6. Linguistic assessment before any conclusion: where an allegation of discrimination involves a multilingual element (a Vietnamese word phonetically resembling an English slur, a distorted machine translation, foreign slang), a sanction may be pronounced only after a person competent in both linguistic Contexts has confirmed the matter. A reasonable doubt as to linguistic error shall be resolved in favour of the speaker, together with a reminder.

### Article 8. Prohibition of harassment

8.1. Harassment in every form is prohibited: stalking, persistent messaging after refusal, repeated tagging so as to cause distress, systematically following and commenting on every activity of a person, veiled threats, and sexual solicitation by word or image. Tier: HEAVY; sexual harassment: the upper end of the HEAVY range up to a permanent ban; where directed at a Minor: RED, under Article 23.

8.2. Harassment through direct messages between Members, originating in a relationship formed within the Server, falls within the jurisdiction laid down in Article 39.2(a). Since the Server cannot see direct messages, the matter shall be dealt with in accordance with the evidentiary standard in Article 4.3; the victim shall be advised to report the matter to Discord as well (Discord being able to verify genuine direct messages) and, where there are indicia of a criminal offence, to report the matter to the police. The Server maintains a confidential channel for the submission of evidence: the [Single-Window Channel](https://discord.com/channels/1342729473245577267/1343099398720065559) or the anonymous e-mail address [private@donquaan.com](mailto:private@donquaan.com). That channel also receives complaints directed at Staff of every level and at the Owner; a case record of this kind shall not pass through the hands of the person complained of (Articles 42.2 and 45.3(d)).

8.3. Where a victim publicly posts evidence containing another person's personal data, including that of the harasser or of an uninvolved third party: the Content shall be removed under Article 20, but simultaneously and inseparably the case file on the underlying allegation shall be opened at once on a priority basis, the victim shall be clearly informed of the reason for removal and of the confidential channel for submission, and the community shall receive a neutral notice that the matter has been taken up. A good-faith victim shall not be sanctioned on a first occasion; only a reminder and guidance shall be given.

8.4. All retaliation against a person who has reported or given evidence is prohibited - scrutiny, petty penalties, ostracism and public shaming. Retaliation is a free-standing violation at HEAVY tier, which may extend to a permanent ban, and applies to Members and Staff alike. Any adverse action directed at a reporting person within 90 days of the date of the report shall by default be examined through the lens of retaliation.

### Article 9. Human dignity

9.1. Content that jokes about, celebrates or derides death, accident, illness or disaster affecting any individual or group - including persons outside the Server, controversial public figures, and the opposing side in a debate - is prohibited. Tier: MEDIUM; where the Content is widely disseminated or accompanied by images of victims: HEAVY.

9.2. Posting news concerning a deceased person, a disaster or a period of national mourning is permitted in the appropriate channel and in a respectful manner. On days of national mourning or during major social events, Staff may temporarily adjust the entertainment activity of the Server, including postponing or adjusting scheduled events; notice shall be given in the Official Channels. The power to activate such an emergency adjustment belongs to Staff on duty from the rank of confirmed Moderator upwards (a Trial Mod does not hold this power) and does not require the Owner to be awaited.

9.3. This Article does not restrict civil, well-founded criticism or assessment of the public legacy of a public figure.

### Article 10. Systematic provocation and cumulative aggression

10.1. Systematic provocation - deliberate, sustained conduct (sarcasm, sniping, mimicry, emotional entrapment) intended to drive another person into a violation so that it may be recorded as evidence - is a free-standing violation at HEAVY tier, irrespective of whether any individual utterance meets the threshold. The determination shall rest on the cumulative behavioural pattern in the history of interaction, examining at least the most recent 14 days in accordance with the log-retention policy in Article 43, and shall require two Staff to reach the same conclusion, as for a sanction inferred from Context (Article 3.5).

10.2. Where a person who has been entrapped reacts in breach of this Code, the conduct shall still be recorded, but systematic provocation shall constitute a substantial mitigating circumstance under Article 3.4(c), and the record shall state expressly that the person was targeted, so as to protect them in later assessments.

10.3. Cumulative aggression - a repeated series of sub-threshold acts directed at one person or degrading the atmosphere of a channel (daily sniping, systematic mocking reactions, persistent mimicry) - shall be dealt with by reference to the overall behavioural pattern, without any single utterance needing to be sufficiently serious: on first establishment of the pattern: MEDIUM; on continuation after a warning: HEAVY.

10.4. When dealing with any matter involving a vehement reaction, Staff shall examine the two-way history of interaction before imposing a sanction; no matter shall be dealt with on the basis of a single screenshot.

---

## CHAPTER III - CONTENT RULES

### Article 11. Pornographic and sexually suggestive content

11.1. The Server standard: every channel shall be safe for viewing by a person of 13 years of age. This standard is higher than the Discord default; the Server does not open age-restricted channels.

11.2. The following are prohibited in every channel, according to a verifiable definition not dependent on the personal perception of Staff: images, video or text depicting sexual acts; nudity or partial nudity of a sexually suggestive character; Content focusing suggestively on intimate parts of the body, even where covered; poses, clothing or camera angles of a sexually inviting character; text describing sexual acts in detail; ecchi or fanservice content meeting any of the above criteria. Tier: HEAVY. A first, sophisticated attempt to circumvent the standard in a genuinely grey area: MEDIUM, together with removal and an explanation of the boundary.

11.3. Sexually suggestive Content directed at, describing, or deliberately made accessible to a Minor; and any Content sexualising a Minor in any form whatsoever, including anime or AI-generated material: RED, under Article 23.

11.4. Sustained flirtatious or sexually suggestive conversation in a shared channel readable by Minors shall be dealt with under the cumulative-pattern approach: Staff shall re-establish the channel standard by a general notice and shall not sanction individuals retrospectively; an individual who continues after that notice: MEDIUM; upon repetition: HEAVY. Staff may restructure or close a channel that has drifted from the standard.

### Article 12. Violent and gruesome content

12.1. Images or video of corpses, severe injuries, executions, abuse of persons or animals, or accidents with visible victims are prohibited in every channel, including where accompanied by a cautionary purpose. Tier: HEAVY; where posted in manifest good faith (a traffic-accident warning with good intent): MEDIUM under Article 3.4(d), together with immediate removal and guidance to share such news by way of a link to a reputable news outlet rather than an image of the scene.

12.2. Content advocating or glorifying violence, terrorism or mass shootings, or providing instructions for the manufacture of weapons or dangerous materials: RED.

### Article 13. Content unlawful under Vietnamese law - emergency removal

13.1. The RED list, to be removed immediately (the target being disposal within approximately 1 hour of detection); every Staff member on duty has the power and the duty to act under the SOP without consultation: (a) content infringing national security: propaganda against the State, organised distortion of history, insult to national leaders, incitement to riot (the framework of Điều 117 and Điều 331, Bộ luật Hình sự (the Penal Code); Nghị định 147/2024 (Decree on the management, provision and use of internet services and online information)); (b) child sexual abuse material (CSAM) - see Article 23; (c) calls for or threats of terrorism or violence; (d) the organisation of gambling and the promotion of gambling or betting for real money or property, including the disguised structures defined in Article 16.8; (e) the sale of, or instructions for the use of, narcotics, weapons or prohibited goods; (f) non-consensual intimate imagery (NCII) and sensitive deepfakes - see Article 24. Tier: RED. The person posting shall be permanently banned; the Content shall be dealt with under the emergency SOP (record the metadata, remove, report to Discord Trust and Safety, retain a timestamped case record, report upwards); the Server shall cooperate proactively with the competent authorities where the indicia are sufficient. Staff and Members shall not comment upon, re-quote or analyse Content within this list, since re-quoting is redistribution. A record showing that the matter was handled in accordance with the SOP and within time shall be retained as evidence of the Server's good faith in moderation.

13.2. As to current affairs and political discussion: the Server does not prohibit neutral, sourced discussion of technology policy or of economic and social policy in the appropriate channel. The prohibited boundary is the list in Article 13.1(a) and disinformation under Article 18. Staff may lock a current-affairs topic at any time where they perceive a risk of escalation, without accusing anyone. When removing Content in this area, Staff shall remove it under the SOP, record the provision relied upon in the case record, give brief notice to the person who posted, and shall not debate political views in a public channel.

13.3. Superstitious content exploited for profit (fee-charging fortune-telling, paid ritual services) and the promotion of unlawful multi-level marketing: HEAVY.

### Article 14. Spam

14.1. The following are prohibited: repeatedly sending identical Content across several channels or on several occasions; strings of meaningless messages causing a channel to scroll; abuse of @everyone, @here or mass mentions; excessive strings of emoji, stickers or capital letters causing disruption; and reaction spam. Tier: LIGHT for an ordinary violation; spam intended to disrupt or carried out by automated tools: HEAVY to RED, under Articles 27 and 34.

14.2. Spam containing fraudulent or phishing links, airdrop or crypto solicitations, or QR codes: RED under Article 25 - an immediate ban without prior warning, including in the case of a newly joined account.

14.3. Automated anti-spam systems (AutoMod, bots) may withhold messages or mistakenly time out genuine Members. A person wrongly dealt with has a rapid-review channel at the [Single-Window Channel](https://discord.com/channels/1342729473245577267/1343099398720065559) (Article 2.2); the Server has a duty to review and reverse the matter within 24 hours together with an apology in the standard template. Being wrongly dealt with by an automated system shall not be entered in the violation record. The operating principles of the automated systems, excluding technical parameters, are published.

### Article 15. Advertising and self-promotion

15.1. Commercial advertising, the offering of goods or services, multi-level recruitment and investment solicitation are prohibited in every form and in every channel; the Server does not operate a commercial channel at this stage, and the prohibition is total until a dedicated channel is announced in the [official announcements channel](https://discord.com/channels/1342729473245577267/1529782982016110642). Tier: MEDIUM; where repeated or directed at Members by mass direct message: HEAVY.

15.2. Self-promotion (sharing a YouTube or TikTok channel, a blog, or a personal product): the Server currently has no self-promotion channel; all self-promotion or advertising constitutes a violation until a dedicated channel is announced in the [official announcements channel](https://discord.com/channels/1342729473245577267/1529782982016110642). Sharing a personal product when asked, or in the Context of a directly related discussion, is permitted. Violation: LIGHT; upon repetition: MEDIUM.

15.3. Promotion of another Discord server: posting invitation links or mass direct-message invitations is prohibited in the absence of an official partnership agreement. Tier: MEDIUM; an organised campaign to draw Members away, or holding a server out as a backup Server or a new Server of the community: HEAVY to RED, under Article 33.

15.4. Any promotional statement made outwardly in the name of the Server, even with good intent, requires authorisation; acting spontaneously in the name of the Server so as to cause inter-server conflict: HEAVY, under Article 27.4.

### Article 16. Transactions, the prohibited-offering list, financial support and the boundary of gambling

16.1. Disclaimer, pinned on a permanent basis and effective in perpetuity: every purchase, group purchase, capital contribution or engagement of services between Members is a private transaction; the Server does not broker, does not guarantee, does not hold funds, does not mediate and does not compensate. A Member who transacts does so at their own risk.

16.2. Prohibited-offering list (a closed list, prohibited in every channel): (a) shared or illicit service accounts in breach of a third party's terms; (b) cracked keys or software, and cracking tools; (c) leaked or pirated courses, e-books or materials; (d) investment tips, coins or tokens, financial signals, and guarantees of profit; (e) artificial engagement services, and the sale or purchase of Discord or social media accounts; (f) goods and services whose trade is prohibited by law. Tiers: the person offering: HEAVY (immediate removal; a permanent ban upon repetition); a person enquiring to buy on a first occasion: LIGHT (a reminder together with a risk warning).

16.3. Acting as collector of funds for a multi-person group purchase within the space of the Server is prohibited from being organised publicly. Tier: MEDIUM (removal, warning); a person who collects funds and then misappropriates them: RED, together with the Server's assistance to victims in reporting the matter to the police (Điều 174, Bộ luật Hình sự (the Penal Code) - fraudulent appropriation of property) and the provision of data upon written request by the competent authorities.

16.4. Defrauding another Member within, or originating from, the Server (defaulting on a deal, taking a deposit and disappearing, selling goods that do not exist): RED - a permanent ban, a community warning in the neutral template, and a victim support package (guidance on reporting, and a list of evidence to preserve). The Server assists up to the door of the legal system and does not pursue the recovery of money on a victim's behalf.

16.5. The vouching by a Member, including a Staff member, for the trustworthiness of another person's transaction is a personal act and is not the voice of the Server; a Staff member who vouches for a transaction shall be dealt with under the Staff Policy.

16.6. Financial support - the legal characterisation is declared in advance and is not renegotiable afterwards: (a) every contribution to the Server is a voluntary, non-refundable gift, save for the cases of refund laid down in the Terms of Service §25.4, and is made without conditions. A contribution does not purchase disciplinary privilege, does not purchase Content, is not a service fee, and creates no commitment as to any feature, event or roadmap; any description of the intended use is indicative only and is not a contract; (b) the sole official point for receiving contributions is published at the [Support Annex](https://donquaan.com/discord/donate), which is the canonical instrument as to conditions, age and source of funds; the refund mechanism, however, is laid down exhaustively by the Terms of Service §25.4, the Annex merely cross-referring to and implementing it. Any offer to contribute made outside the officially published point is a forgery under Articles 5.2 and 33; (c) financial discipline: only the Owner may approve every flow of funds and every item of expenditure of the Server; no subordinate, including a co-owner, may spend on their own initiative; a co-owner may spend only under a written item-by-item authorisation from the Owner, including in an emergency - expenditure shall be made only under a pre-existing written authorisation, and there exists no spending limit operative in the Owner's absence. In addition there shall be an independent reconciliation bookkeeper; that person has no spending power and only records and reconciles. The receipts-and-payments book shall be published periodically in summary form each quarter, and supporting documents shall be retained under Article 43. The person approving expenditure shall in no case also be the sole person keeping the book. The sole exception is the time-limited transitional period laid down in OWN §43.2(d), during which the following compensating measures apply concurrently: item-by-item publication within 07 days, confirmation by a person independent of the Owner, a 30-day time limit for designating the independent bookkeeper, and automatic suspension of the acceptance of donations upon expiry of that time limit; outside that period, the rule in this point admits of no exception; (d) questions and queries concerning the fund are a right of Members under Article 18.1 and shall be answered with documentation.

16.7. Minors and money (implementing the Terms of Service §25.4(a) and §25.4(b); this Article creates no further case of refund, narrows none and imposes no further condition on any): the Server advises persons under 18 years of age not to make financial contributions. A contribution of 500,000 VND or more involving a person known or self-declared to be under 18 years of age shall be accepted only with the confirmation of a parent or guardian. Every contribution by a person under 18 years of age shall be refunded to the guardian upon request made within 90 days of the date of contribution, without argument; once a valid request is received, the refund shall be processed within 72 to 120 hours, larger sums being processed first. Prizes for Minors shall be delivered through the guardian in accordance with Article 23.6. The Server does not accept contributions from persons under 16 years of age where it knows this to be the case.

16.8. The boundary of gambling - prohibited in every case, with no recreational version: (a) any activity collecting real money for participation where the award of prizes depends on chance (paid entry with prizes, prediction with pooled stakes, paid-spin wheels): prohibited from being organised and from being promoted; the organiser: RED under Article 13.1(d), including where that person is Staff and including where the purpose is fundraising; (b) two-way conversion between virtual currency or reward points and real money or goods outside approved rules: prohibited; the sale or purchase of currency or points between Members: MEDIUM together with annulment of the results under Article 34.4; the systematic operation of a currency market: HEAVY to RED; (c) a skill-based event with prizes shall be lawful only where participation is free of charge and the rules are published in advance in accordance with the Framework Event Rules. No Staff member has authority to approve an exception to this Article.

### Article 17. Language, spoilers and the quality of conversation

17.1. The principal language of the Server is Vietnamese; English and technical terminology are accepted. No other language may be used to circumvent moderation; swearing in a foreign language shall still be dealt with under Article 6.

17.2. Spoiler Content concerning newly released films, fiction, games or competition results shall use the Discord spoiler tag together with a warning and shall be posted in the correct channel. Violation: LIGHT; deliberate spoiling in order to ruin another person's experience (changing a display name or avatar, spoiler spam): MEDIUM.

17.3. AI-generated content posted by a Member: the posting Member is responsible for it as for content they have written themselves. Labelling as "AI-generated" is encouraged for images or text liable to be mistaken for genuine material; AI content impersonating a real person shall be dealt with under Articles 24 and 33.

17.4. Deliberate exploitation (prompt injection, jailbreaking) of a Server AI bot in order to generate violating Content and then to circulate it as a statement of the Server: dealt with at the tier of the Content generated, and at least MEDIUM; where circulated externally together with distortion: Article 37 shall apply in addition.

### Article 18. Disinformation and harmful rumour

18.1. Questioning is a right; fabrication is a violation. Members have the right to ask questions, including uncomfortable questions, about the operation, the finances and the personal data practices of the Server; such questions shall not be deleted and shall not be sanctioned, and Staff have a duty to answer them publicly by reference to standing policy documents.

18.2. A fabricated assertion - stating as fact something harmful to an individual or to the community without verifiable foundation (verifiable foundation being evidence attaining at least Tier B under Article 4.3; hearsay, blurred images incapable of cross-reference and conjecture are not foundation), or continuing to circulate it after an official answer with corrective documentation has been given: MEDIUM; where organised or where it causes an actual crisis: HEAVY. The distinction between questioning and fabrication shall, in case of doubt, be resolved in favour of protecting the right to ask: a sentence framed as a question is questioning; a categorical assertion without foundation is fabrication.

18.3. False information concerning social events, epidemics, natural disasters or State policy (the area of Nghị định 147/2024 (Decree on the management, provision and use of internet services and online information) and Nghị định 15/2020 (Decree on administrative sanctions in the fields of posts, telecommunications and electronic transactions, concerning false information)): immediate removal; tier HEAVY; in serious cases: RED.

---

## CHAPTER IV - SAFETY RULES

### Article 19. General principles of the Safety Chapter

19.1. Violations under this Chapter shall be given the highest priority and shall be dealt with under written SOPs, in this order: protect the person first, conclude afterwards, publish last or not at all.

19.2. Protective interim measures (an interim ban, a restriction on interaction) under this Chapter are safety measures and not determinations; the case record shall state that character expressly and the measure shall be annulled where the conclusion is that no violation occurred.

19.3. Every matter under this Chapter involving a Minor shall be handled entirely confidentially; the case record shall be accessible to at most 2 named persons; no detail and no identity shall be published in any circumstances, including in the name of transparency.

### Article 20. Prohibition of doxxing

20.1. Definition: posting or aggregating identifying information concerning another person - real name, facial image, telephone number, address, school or place of work, social media accounts, family information - within or together with a Context of hostility, conflict, derision, or a call for negative attention, constitutes doxxing, irrespective of whether that information is publicly available elsewhere. An argument that the victim themselves disclosed the information on another platform carries no weight: the conduct prohibited is the aggregation and placing of information into a harmful Context.

20.2. Tier: RED - a permanent ban by default; borderline cases (sharing identifying information without malice but without consent): HEAVY; the case of a good-faith victim submitting evidence under Article 8.3 shall be dealt with under Article 8.3 and not under this Article.

20.3. The trace-removal SOP is measured in minutes: removal of the original Content within at most 15 minutes of detection; a request to the parties to delete screenshots; a report to Discord; and delivery to the victim of a support package (guidance on locking personal profiles, reporting to external platforms, and the right to report the matter under Luật 91/2025/QH15 (Law on Personal Data Protection) and Nghị định 356/2025/NĐ-CP (Decree detailing the Law on Personal Data Protection)).

20.4. The use of automated tools (self-bots, scrapers) to collect Member information (member lists, introduction posts, messages) in order to disseminate, sell or profile it: RED, together with notification by the Server to the Members affected and assistance in reporting the matter.

### Article 21. Prohibition of threats and real-world violence

21.1. A three-level scale; Staff have no power to determine for themselves whether points (b) and (c) are jest or earnest: (a) generalised aggressive trash talk, without locational detail and without specificity: dealt with under Article 6 (MEDIUM); (b) a threat accompanied by genuine locational detail (the correct district, school or place of work): HEAVY to RED - immediate removal, an immediate ban or mute, and a report to Discord; the victim shall be given written template guidance on preserving evidence and reporting to the police (with reference to Điều 133, Bộ luật Hình sự (the Penal Code) - threat to kill, where the indicia are sufficient); (c) arranging a real-world meeting to settle a dispute (fixing a place and a time): immediate intervention even where both parties present the matter as a joke - lock the topic, message each party privately using the template, and log the intervention; the instigator: HEAVY; continuation after intervention: RED.

21.2. Within the scope of the platform, the Server intervenes at once, issues warnings, preserves evidence and cooperates fully with investigating authorities. The Server has no capacity to prevent physical harm in the real world and does not replace the competent authorities; where physical safety is threatened, jurisdiction lies with the police and the Server assists the victim in reporting the matter.

### Article 22. Self-harm and psychological crisis

22.1. As regards a person in crisis: the Server does not sanction a person calling for help. Every self-harm signal (a farewell message, an allusion accompanied by means, a timeframe) shall be treated as genuine under the emergency SOP: respond using a template approved by a qualified professional, provide support contacts (the National Child Protection Hotline 111 · emergency services 115), report to Discord through the self-harm flow, report upwards regardless of the hour, and limit dissemination. The Server's e-mail addresses and support tickets do not replace those emergency hotlines. A post calling for help shall not be deleted as junk content; display may be limited or the thread locked together with a support notice, only after the SOP has been run.

22.2. As regards other Members: joking about, challenging or seeking engagement from another person's self-harm signal is prohibited: HEAVY. Giving medical or psychological advice as though one were a professional is prohibited; the correct role of a Member is to notify Staff and to provide the hotline numbers.

22.3. Content that glorifies, romanticises or gives instructions for self-harm, suicide or eating disorders is prohibited under the [Discord Community Guidelines](https://discord.com/guidelines): removal; tier HEAVY where the Content deliberately advocates such conduct. A cumulative trend of dark content (images of scars, repeated dark captions becoming a trend) shall be addressed under the behavioural-pattern approach: re-establish the channel standard, approach each person individually with support, and refrain from sanctioning as an ordinary violation unless there is deliberate advocacy.

22.4. The confiding channel shall have a permanently pinned description stating expressly that the channel is not a psychological counselling service, together with a list of hotlines (111 · 115). Staff do not provide medical or psychological services; the Server only directs persons to competent sources of support and is not a place of treatment. The channel description shall also state expressly that every channel, including the confiding channel, is logged (Article 43.1); the logs of the confiding channel are classified at Access Level 2 (Head Admin and above, and the Owner, only); Members are advised not to share sensitive identifying information, this advice appearing in the channel description itself.

22.5. This Article applies without alteration where the person in crisis is a Staff member. Staff have their own internal SOP (Staff emergency contact details - collected voluntarily upon taking up the role, retained and used under the data policy, and used only for emergencies concerning life) laid down in the Staff Policy.

### Article 23. Protection of Minors

23.1. The following four forms of conduct fall within the RED tier and admit of no exception for any person - an immediate permanent ban, a report to Discord Trust and Safety, retention of the legal case record, and a recommendation of, or proactive cooperation in, a report to the police; no amnesty and no mitigating circumstances: (a) child sexual abuse material (CSAM) in any form, including drawings and AI-generated material; (b) solicitation, enticement or courting of a Minor (grooming): requesting images, unusual invitations to converse privately, gifts in exchange for interaction, moving the conversation to another platform; (c) sexualising a Minor by word, by image, or in the guise of a joke; (d) organising or arranging access by a Minor to adult Content or adult spaces.

23.2. SOP upon a signal of grooming, including where only an unverified screenshot exists: impose a protective interim ban on the person complained of immediately (stating expressly that this is a safety measure and not a determination) → report to Discord Trust and Safety → advise the family or the victim to report the matter to the police (with reference to Điều 146 and Điều 147, Bộ luật Hình sự (the Penal Code)) → the Server shall provide data upon written request by the competent authorities → the matter shall not be dealt with publicly and no party shall be named in any circumstances. A one-sided screenshot suffices to trigger protective measures; the final determination shall follow the evidentiary standard in Article 4.3 and lies within the jurisdiction of the competent authority. All communication with the victim's family shall pass through a single spokesperson in accordance with Article 38.3.

23.3. Handling of CSAM: do not download, do not forward, do not re-photograph the Content; record only the metadata (message ID, channel, time, account); report using Discord's native report tool; remove after reporting; timestamp every step; at most 2 designated persons may access the case record. Do not pay and do not negotiate in respect of any extortion connected with CSAM; report to the police immediately.

23.4. A Member under 13 years of age (self-disclosed or verified) shall be dealt with uniformly under the following procedure: remove the Content disclosing the age, send a template notice stating expressly the right to rejoin upon reaching 13 years of age, remove the person from the Server, and report to Discord under the under-13 procedure. This is a platform requirement; the Server does not operate a separate regime for children. Such removal is not a sanction and shall not be entered in the violation record.

23.5. Risk structures prohibited for so long as the Server remains open to persons under 18 years of age: all anonymous pairing or matchmaking events, anonymous "confession" channels, and any mechanism placing two strangers into a private one-to-one space arranged by the Server. There exists no supervised version of these structures. No Staff member has authority to approve an exception.

23.6. Where a Minor receives a prize of value or takes part in an activity involving money: this shall be done in accordance with the event rules; a prize involving a person under 18 years of age exceeding 500,000 VND shall require the confirmation of a parent or guardian, shall be approved by two persons at the time of award, and shall be delivered through the guardian. Award information shall be retained for 30 days under Article 43.1. Contributions by Minors are governed by Article 16.7.

### Article 24. NCII and deepfakes targeting real persons

24.1. The following forms of conduct are prohibited at RED tier, with no exception for the purpose of technical demonstration, without any requirement that the victim be present on the Server, and without any requirement that a report be made: (a) private, sensitive images or video of another person disseminated without consent (NCII); (b) deepfakes or the grafting of a real person's face onto sensitive, pornographic or defamatory Content; (c) cloning the voice or likeness of a real person in order to defraud or to fabricate statements. This is at the same time a zero-tolerance area for Discord and presents indicia under Điều 155, Bộ luật Hình sự (the Penal Code) (humiliation of another person), Luật 91/2025/QH15 (Law on Personal Data Protection) and Nghị định 356/2025/NĐ-CP (Decree detailing the Law on Personal Data Protection).

24.2. The boundary of lawful technological demonstration: the use of a real person's face or voice is prohibited, including one's own face where it is sent to another person in a sensitive Context; the use of a wholly synthetic character who does not exist and does not evoke any specific real person is permitted in the appropriate channel, subject to Article 11.

### Article 25. Fraud, phishing and malware

25.1. RED tier, an immediate ban without prior warning: phishing links (fake Discord, Steam or bank login pages); "Free Nitro" solicitations; airdrop or crypto fraud; any request to scan a QR code (QR codes are prohibited in all Server activity); attachments containing malware; and files disguising their extension (right-to-left override characters, .scr files posing as images).

25.2. The Server has no channel for sharing executable files; the sharing of executable files (.exe, .bat, .scr, directly executable scripts and equivalents) is prohibited in every channel. Posting an executable file: MEDIUM (immediate removal); a file determined to contain malware: RED.

25.3. A Member account that has been compromised and used to distribute harmful Content shall be dealt with under Article 35 (freezing rather than banning): the Member is a victim and not an offender until there is evidence to the contrary.

25.4. A victim of fraud shall be provided by the Server with the standard support package (guidance on reporting to the police, a list of evidence, a ban and report of the fraudster, and a neutral community warning). The Server assists up to the door of the legal system; the Server does not investigate in the victim's place and does not make restitution in the offender's place.

25.5. A person holding themselves out as a Discord employee or a public authority who contacts a Member or Staff requesting urgent action shall be presumed to be a fraudster: Discord and public authorities do not operate through direct messages to require a link to be clicked. Report the matter to the [Single-Window Channel](https://discord.com/channels/1342729473245577267/1343099398720065559) before taking any action whatsoever.

### Article 26. Fabrication of evidence and false reports

26.1. It is prohibited to create, alter or stage false evidence - fake direct-message screenshots, chat logs constructed with tools or with AI, edited transfer receipts, spliced audio recordings - for the purpose of accusing, humiliating or manipulating proceedings against any person (a Member, Staff or the Owner). Tier: RED - a permanent ban, non-amnestiable. A defence that the conduct was only a joke carries no weight once the false evidence has been used to accuse or has been disseminated; this provision applies to Members and Staff alike. Where actual harm to reputation is caused, the Server shall assist the victim in reporting the matter under Điều 156, Bộ luật Hình sự (the Penal Code) (defamation) and Nghị định 15/2020 (Decree on administrative sanctions concerning false information). A meme or parody manifestly understood as a joke by every reader, not submitted to a report channel and not used to accuse anyone, does not fall within this Article, but may fall within Article 6 or Article 33 depending on its content.

26.2. The conduct laid down in Article 26.1 is classified as the most serious violation of this Code; no circumstance other than that laid down in Article 26.4 may be relied upon in mitigation.

26.3. Coordinated false reporting (several accounts jointly constructing one allegation) shall be dealt with in respect of the entire group as a coordinated attack under Article 27. A person who constructs evidence, or who uses evidence knowing it to be false: RED under Article 26.1. A person who joins in a report as a result of being drawn in, where it cannot be shown that they knew the evidence to be false: dealt with under Article 27 at HEAVY tier.

26.4. A report that is mistaken but made in good faith (misunderstanding, incomplete information) shall not be sanctioned. The boundary between Article 26.1 and Article 26.4 is the element of deliberate fabrication or staging; doubt shall be resolved in favour of the reporting person.

26.5. A good-faith reporting person shall be protected in every case: their identity shall be kept confidential upon request, and retaliation is prohibited under Article 8.4, including where the final conclusion is that no violation occurred.

### Article 27. Coordinated attack: raiding, brigading and organised disruption

27.1. A coordinated attack is a violation independent of the content of each individual message. Each individual utterance still constitutes a violation where it forms part of a scripted disruption campaign.

27.2. Identification criteria (a conclusion requires at least 2 of the 4 criteria, approved by 2 Staff): (a) a cluster of accounts joining abnormally in point of time; (b) a verifiable common source (a mutual server, a public call to action); (c) a content pattern matching a script; (d) targeting of the same target, event or moment. A genuine, isolated questioner not matching the criteria - including one asking uncomfortable questions - does not fall within this Article (Article 18.1).

27.3. Tier: RED for organisers and for deliberate participants, including raid spam or filth content; scripted brigading intended to disrupt an event; sleeper raids; vote piling intended to manipulate a result; and factional blocs within the Server operating as a coordinated bloc so as to dominate debate or to overturn a sanction.

27.4. Counter-attack in the name of the Server is prohibited: Members who move together into another community to provoke conflict, to spam or to defend the Server - even with good intent - commit a HEAVY violation; coordinated harassment within the meaning of Discord's standards may cause the Server itself to be sanctioned. The Server does not call for, and does not accept, Members attacking other places, in any circumstances.

27.5. Emergency handling of a raid: Staff may use mass measures (mass ban, lockdown, raising the verification level) in accordance with predetermined objective criteria, subject to two mandatory safeguards: a proactive post-review of the entire list by a person who did not give the order, to be completed within 72 hours (with an internal target of commencing within 24 hours); and an out-of-Server rapid ban-appeal channel - the e-mail address [support@donquaan.com](mailto:support@donquaan.com), permanently published at [APL](https://donquaan.com/discord/rules/appeals) - with disposal within 24 hours, consistently with APL. A person caught wrongly in the sweep shall have the ban lifted, shall receive an apology in the standard template, and shall have no trace left in their record. The duty to review, to lift the ban and to apologise is unconditional and admits of no exception.

---

## CHAPTER V - RULES ON CHANNELS, VOICE AND PERSONAL PROFILES

### Article 28. Correct channel, correct topic

28.1. Each channel has a topic description; Members shall post in the correct channel. Posting in the wrong channel: an informal reminder or LIGHT (a reminder, and moving of the Content); deliberate repetition after a reminder: MEDIUM.

28.2. The newcomer channel and the question-and-answer channel are protected areas: deriding basic questions is prohibited. Tier: LIGHT; upon repetition: MEDIUM. Members are under no obligation to answer questions; a person who does answer is governed by this provision.

28.3. Staff may lock the topic of any discussion presenting a risk of escalation (politics, religion, regional matters, personal conflicts) without accusing anyone; deliberately reopening a locked topic in another channel: MEDIUM.

### Article 29. Voice rules

29.1. The following are prohibited in every voice channel: destructive volume, shock soundboards, broadcasting pornographic or gruesome Content or Content in breach of Chapters III and IV, and disrupting events. Tier: according to the nature of the Content, and at least MEDIUM; Content at RED tier: RED. Staff on voice duty may server-mute or disconnect a person immediately without prior warning.

29.2. Voice evidence: voice channels have no logs. A sanction based on events in voice requires at least 2 witnesses outside the same relational group, or a valid recording; where there are only witnesses and no Tier A or Tier B recording, the ceiling of the sanction is MEDIUM, save for conduct falling within the Safety Chapter (Articles 21, 22 and 23), where protective interim measures may still be applied immediately under the SOP. The Server does not deploy undisclosed monitors in voice; monitoring shall be carried out only by Staff whose identity is public.

29.3. Audio and video recording: an official event that is recorded shall be announced in the rules and again at the start of the session, stating expressly the purpose and the place of storage; continued participation after that announcement constitutes consent. Otherwise, recording or live-streaming another person in voice without consent and then disseminating it: MEDIUM; dissemination accompanied by harmful editing: HEAVY, under Article 37.

29.4. Basic voice etiquette (muting when in a noisy environment, not interrupting, yielding the microphone at events): repeated breach after a reminder: LIGHT.

### Article 30. Display names, avatars and profiles

30.1. A name, avatar, status or biography containing the following is prohibited: Content in breach of Chapters II to IV (obscenity, discrimination, pornography, political content in breach of Article 13.1, fraudulent advertising); characters that break the interface or seize the top of the name ordering; and content mimicking or defaming another Member. Tier: LIGHT (a requirement to change within 24 hours, Staff being entitled to make an immediate provisional change); refusal to cooperate: MEDIUM; content within the RED group: dealt with as RED.

30.2. A name or avatar impersonating another person (a Member, Staff, the Owner, a celebrity) so as to cause confusion shall be dealt with under Article 33.

30.3. A coincidental identical display name is not a violation; in activities involving entitlements (giveaways, prizes), identification shall always be by user ID and never by display name.

### Article 31. Special-purpose channels

31.1. The self-introduction channel: a warning concerning self-disclosure of information shall be pinned (Article 5.4). It is recommended that telephone numbers, addresses, and specific schools or places of work not be posted.

31.2. The confiding channel operates in accordance with Article 22.4; the confiding channel is logged like every other channel (full disclosure - no channel lies outside the logging area), but access to the logs of the confiding channel is classified at Access Level 2, Head Admin and above and the Owner only (Article 43.1); all Content in this channel shall be treated to the highest standard of privacy; Members are advised not to share sensitive identifying information; recounting or deriding elsewhere the content of the confiding channel: HEAVY.

31.3. Resource-sharing and file channels: governed by Articles 25.2 and 36.

31.4. Event channels: during an event, event mode may be enabled (slow mode; links posted by Staff only); messages containing links from ordinary Members during a major event may be withheld automatically - this is a safety measure and not a sanction.

---

## CHAPTER VI - ACCOUNT RULES

### Article 32. Alternate accounts, clones and ban evasion

32.1. Each person shall participate using one account. An alternate account is not in itself a violation; the violation lies in using an alternate account for advantage or harm: farming events or points, duplicate voting, self-praise, and evading channel restrictions - MEDIUM, with any advantage obtained annulled under Article 34.4; using an alternate account to harass or to fabricate the appearance of consensus among several persons: HEAVY.

32.2. Ban evasion: a permanent ban follows the person and not the account. Returning under another account while banned, upon detection or upon report and verification to the standard in Article 32.3: the new account shall be permanently banned as soon as identification meets the standard - RED tier for the ban evasion, irrespective of how long the new account operated without violation (Article 3.9).

32.3. Standard for identifying an alternate account: a conclusion requires an admission by the person concerned, or at least 3 independent, mutually consistent indicators (behavioural pattern, timing, details known only to the former person, valid technical traces), approved by a second person. Similarity of writing style, standing alone, is never sufficient.

32.4. The path of voluntary disclosure: a permanently banned person, save in the case of RED sanctions under Articles 23, 24 and 26, may after 12 months submit an amnesty application through the official appeal window (Article 42.1; a person currently banned shall use [support@donquaan.com](mailto:support@donquaan.com)) under their former identity and not through an alternate account. Voluntary disclosure of the use of an alternate account before detection is a circumstance to be recorded when amnesty is considered.

### Article 33. Impersonation

33.1. Impersonation in every form is prohibited - RED tier: (a) impersonating the Owner or Staff (by name, by a closely similar avatar, or by self-description) in order to obtain money, to sell courses, to charge fees, to lift sanctions, or to give orders to Members; (b) impersonating a Discord employee or a public authority; (c) setting up a counterfeit Server (an "official backup", a "new DonQuaan Server") or issuing false notices that the Server has relocated; (d) forging an official Server announcement by webhook, bot, e-mail or any other means, including e-mail purporting to act in the name of the Server sent from a free-mail address or from any address other than [notify@donquaan.com](mailto:notify@donquaan.com), and any contact in the name of the Server through Zalo, Messenger or another platform (Article 2.2).

33.2. Restating Article 5.2: any request for a money transfer or for the scanning of a QR code in the name of the Owner or of Staff is by definition a forgery. A Member encountering impersonation shall not interact, shall take a screenshot and shall report the matter immediately at the [Single-Window Channel](https://discord.com/channels/1342729473245577267/1343099398720065559). The verification standard where any statement purporting to be made in the name of the Owner is in doubt, including audio or video content generated by AI, is that laid down in Article 38.4.

33.3. Manifest parody or humorous content that causes no confusion and yields no advantage does not fall within this Article, but shall cease when the person parodied so requests; if it continues: dealt with under Article 8.

### Article 34. Automation, personal bots and exploitation of mechanisms

34.1. Self-bots, user-bots, macros and scripts automating a user account - which in any event breach the Discord Terms of Service - are prohibited on the Server. Tier: HEAVY; where used to harvest data, to spam or to disrupt: RED.

34.2. A bot developed by a Member may be introduced into the Server only through the official assessment procedure (registration, minimum-privilege review, two-person approval). Introducing a bot without authorisation: the bot shall be removed at once and the person introducing it: MEDIUM. A person who donates or operates a bot bears responsibility for its management and for its conduct: where a bot causes harm through the deliberate act or gross negligence of its owner (leaking a token, failing to patch a reported defect), the owner shall be dealt with according to the actual harm, up to a maximum of HEAVY; where it is shown that the owner acted diligently and was attacked beyond their control, the matter shall end with removal of the bot and withdrawal of its privileges.

34.3. Exploitation of prompt injection or of a defect in a Server bot in order to generate violating Content or to construct an allegation: governed by Article 17.4. Good-faith defect reports shall be made by e-mail to [support@donquaan.com](mailto:support@donquaan.com) (with "Security defect report" stated in the subject line) or to [private@donquaan.com](mailto:private@donquaan.com) where anonymity is desired; the Server shall acknowledge receipt and respond within 72 hours, and the reporting person shall be publicly credited and shall not be sanctioned. Demanding money in exchange for silence concerning a vulnerability presents indicia of extortion: the Server does not negotiate and shall report the matter under the applicable procedure.

34.4. Mechanism-exploitation clause: the use of automation, multiple accounts, exploitation of system defects, or any technical device in order to obtain an advantage in outcomes (points, levels, giveaways, leaderboards, votes) shall result in the unconditional annulment or reversal of the outcome; the conduct: MEDIUM to HEAVY according to scale. Using a mechanism as designed is lawful; using a defect or automation is exploitation. Borderline questions shall be resolved by reference to the published design of the mechanism concerned.

34.5. Register of bots, webhooks and integrations: every bot, webhook and automated integration on the Server shall appear in an internal register (name, privileges granted, responsible person, source). Mandatory principles: minimum privilege - no bot shall be granted Administrator privileges save upon special approval by two persons; where the person responsible for a bot or webhook leaves their role, that bot or webhook shall be removed or its secret rotated within the handover procedure; and the entire list shall be reassessed every 6 months (the quarterly audit conducting a rapid review; the 6-month cycle conducting a deep review of OAuth and of ownership), including in respect of bots operating normally, since a bot may be transferred to a new owner or compromised on the developer's side.

### Article 35. Compromised accounts

35.1. Where a Member account suddenly behaves abnormally (spamming malicious links, Content wholly at odds with its history): Staff shall apply freezing rather than banning - a timeout or isolation, removal of the malicious Content, and contact with the account holder through another channel where one exists.

35.2. Restoration after the account holder regains control: verification by cross-confirmation through a channel of communication known before the incident, or by correctly answering at least 2 details known only to the genuine holder; 1 Staff member shall verify and 1 person shall approve; thereafter the freeze shall be lifted and no violation record shall be entered against the victim.

35.3. Feigning a compromised account in order to disclaim responsibility: where staging is proved to the evidentiary standard in Article 4.3, the matter shall be dealt with according to the underlying conduct together with Article 26.

35.4. Mandatory safety recommendations to be disseminated: enable two-factor authentication, do not click unknown links, do not scan QR codes, do not enter tokens; the Server shall issue a monthly reminder in the [official announcements channel](https://discord.com/channels/1342729473245577267/1529782982016110642).

35.5. Emergency circuit-breaker where a Staff account is compromised: where an account holding administrative privileges carries out abnormal destructive conduct (mass ban, channel deletion, posting of malicious Content, mass changes), every Staff member witnessing it has the power and the duty to act at once: strip that account of its roles or privileges, disable the bots concerned, and lock the affected channels, without awaiting a superior or the Owner. A good-faith emergency circuit-breaker action shall never be treated as an excess of authority, including where it is subsequently established to have been a false alarm; the whole matter shall be reviewed after the fact within 24 hours under the Staff Policy.

---

## CHAPTER VII - INTELLECTUAL PROPERTY RULES

### Article 36. Copyright and third-party content

36.1. It is prohibited to post or to share links to: pirated or leaked courses, e-books or software; cracked keys; films, music or matches from unlicensed sources; and aggregated repositories of infringing resources, including under the guise of sharing for study purposes. Tier: MEDIUM (immediate removal); a first violation shall be dealt with by preference through educational measures; repetition or systematic distribution: HEAVY. Basis: the Discord Terms of Service; Luật Sở hữu trí tuệ (the Law on Intellectual Property); and Điều 225, Bộ luật Hình sự (the Penal Code) in respect of infringement on a commercial scale.

36.2. Official events shall not broadcast copyright-protected Content without permission (screening films or football from pirated sources, replaying protected recordings). A proposal for an event of this kind shall be refused at the rules-approval stage, without exception. A Member who records an event and then posts the recording on an external platform, giving rise to a copyright issue, shall bear responsibility to that platform.

36.3. Attribution when using another person's material (quiz questions, formats, graphic works, articles): the use of material belonging to the community or to another author shall be attributed; appropriating another person's work as one's own within the Server (plagiarising a competition entry, plagiarising content): MEDIUM; obtaining a prize by means of a plagiarised product or in breach of the rules: the prize shall be withdrawn under the rules together with a HEAVY tier.

### Article 37. Internal Server content

37.1. The content of access-restricted channels (Member-only channels, closed event channels, beta programmes) is internal content. Extracting, copying or disseminating it externally without permission is prohibited. Tier: HEAVY; dissemination accompanied by harmful editing or distortion of Context: the upper end of the HEAVY range up to RED; where it amounts to disinformation or defamation, the Server shall assist the injured person in making a report under the law.

37.2. Good-faith whistleblowing is protected: bringing evidence of genuine wrongdoing to the correct channel (the Server's reporting channel, Discord, the competent authorities, or the press in a serious matter) does not constitute a violation of Article 37.1. What is prohibited is distorted or staged dissemination, or the scattering of internal content in order to extort by reputational threat. Article 37.1 may not be invoked so as to restrict or to retaliate against legitimate whistleblowing.

37.3. Content posted by a Member within the Server belongs to that Member; in posting it, the Member grants the Server the right to display and store it for the purposes of operation and moderation under the data policy. The Server asserts no ownership over a Member's intellectual work.

### Article 38. The name, logo, identity and speech of the Server

38.1. The name, logo and visual identity of the community are managed by the Owner. It is prohibited to use the name or logo to organise activity in the name of the Server without authorisation; to open a counterfeit server or group causing confusion; or to associate the Server with commercial activity or personal fundraising. Tier: HEAVY; accompanied by fraud or impersonation: RED, under Article 33.

38.2. A Member who leaves the community and establishes their own space exercises their own freedom; what is prohibited is only causing confusion as to authenticity and spreading false information about the Server.

38.3. The single-spokesperson principle for outward communication: only the designated Spokesperson - being the Head Admin, with a Moderator designated by the Owner as alternate, and with the Owner approving the final text - may speak in the name of the Server to the press, to persons of influence, to fan pages and to other communities, particularly during a crisis; these positions are appointed by the Owner and announced in the [official announcements channel](https://discord.com/channels/1342729473245577267/1529782982016110642), taking effect from the moment of announcement; where no person holds the position, the Owner shall discharge this role (Article 2.3). Every other Staff member and Member, when asked, shall use exactly one redirecting sentence: _"Please contact the community's official channels; I do not speak for the Server."_ Answering a journalist on terms of non-publication shall be treated as answering publicly. A Staff member whose spontaneous statement in the name of the Server causes harm shall be dealt with under the Staff Policy.

38.4. Authenticity verification standard (against forgery and deepfakes): every official statement of the Server, and of the Owner acting as Owner, has effect only where it appears in the Official Channels (Article 2.2); authenticated e-mail comes only from [notify@donquaan.com](mailto:notify@donquaan.com) and the authentication standard is published at the [identity authentication annex](https://donquaan.com/discord/verify). Any recording, video or image said to be a statement of the Owner or of Staff and circulating outside those channels shall by default be treated as unverified.

---

## CHAPTER VIII - SCOPE OF JURISDICTION

### Article 39. Conduct inside and outside the Server

39.1. Default rule: this Code governs only conduct within the Server and at official events held in the name of the Server. A Member criticising the Server or speaking ill of Staff in a private external chat group does not commit a violation and shall not be pursued on the basis of leaked evidence.

39.2. Exceptions (a closed list) - conduct outside the Server shall be dealt with where it: (a) is directed at a Member or a Staff member by reason of their status as such: doxxing, attack by direct message, dissemination of distorted internal content, organising an attack on the Server; (b) occurs at an official offline event (Article 40); (c) creates a direct safety risk to the community (for example, an individual with a legal determination concerning child abuse - the Server shall exercise its right to refuse service on the basis of a documented record).

39.3. Evidence from a leaked private external chat may be used only where it independently attains Tier A or Tier B and the conduct falls within an exception in Article 39.2; it may never be used to sanction criticism of the Server.

39.4. Real-world matters concerning a Member, including a person of influence: the Server does not act on public opinion. The Server shall act only where the matter falls within Article 39.2(c) or where there is repeated violating conduct within the Server. Reputational association is not a basis for action. When asked, the Server's standard statement is: "Conduct outside the Server does not fall within our jurisdiction."

### Article 40. Offline events

40.1. A hard division admitting of no intermediate zone: (a) an official event: has written approval from the operations function, a designated person in charge, and a safety checklist, and the whole of this Code - in particular Chapters II and IV - applies as it does within the Server; an event attended by persons under 18 years of age shall be alcohol-free and subject to separate supervision rules; (b) a spontaneous gathering of Members: may be organised freely, but the use of the Server's logo or the name of a Server event is prohibited; the Server does not lend its name to it and bears no organisational responsibility. Unauthorised use of the name: HEAVY, under Article 38. Staff attending a spontaneous gathering do so in a personal capacity and have a duty to say so when asked.

40.2. Harassment or abuse at an official event shall be dealt with under the corresponding provisions of this Code (at least HEAVY; where a Minor is involved: RED), in parallel with directing the victim to the competent authorities; the Server does not replace the law in respect of real-world conduct.

---

## CHAPTER VIII-B - INTERNAL CONFIDENTIALITY, COMPLICITY AND PREVENTION OF REPEAT OFFENDING

### Article 42-A. Confidentiality of internal information

42-A.1. Internal information comprises: system logs and moderation logs; case files and reports; exchanges in channels reserved to the Staff; direct messages between Staff and a Member in the course of handling a matter; identifying data of a reporter; and every document, image or recording that the Server has placed under restricted access.

42-A.2. No person shall copy, disseminate, republish or transfer internal information to a third party, in any form, publicly or anonymously, in whole or in extract, without the written consent of the Owner. Redacting names or blurring does not make the act lawful.

42-A.3. Three cases shall NOT be treated as a breach of Article 42-A.2, and the Server shall not sanction any person for them: a) provision to a competent authority when denouncing conduct bearing the indicia of a criminal offence, or when required under a statutory procedure; b) provision to a lawyer, a court or an arbitral tribunal in a matter to which the person providing it is a party; c) publication of the part of the information that is itself evidence of unlawful conduct directed at the person publishing it, and only to the extent necessary for that defence.

42-A.4. Article 42-A.3 is an exhaustive list of exceptions. The Server shall not invoke the duty of confidentiality to prevent a person from exercising the right to denounce or the right of self-defence; any reading to the contrary is void.

42-A.5. A breach of Article 42-A.2 is dealt with at Tier 5. Where the information disclosed contains the personal data of a third party, or discloses the identity of a reporter, the tier is 6 and no amnesty is available under Article 44.

### Article 42-B. Complicity, facilitation and concealment

42-B.1. A person who assists, enables, supplies tools, supplies access, or conceals a violation bears the same responsibility as the person who commits it, where that person knew or ought to have known of the conduct.

42-B.2. For the organised destruction group, comprising nuking, mass spam, organised fraud and the dissemination of malware: a person who intentionally facilitates it shall be dealt with at Tier 6, permanently banned, and no amnesty is available under Article 44.

42-B.3. A person who facilitates without intent shall have the tier reduced, to no lower than Tier 3, where at least one of three grounds is present: the statement of the Staff member who handled the matter; the statement of a witness with no interest in the outcome; or logs showing that the person did not know the purpose of the use. The absence of intent shall be stated in the case file and shall not be presumed.

42-B.4. A person who voluntarily discloses their own facilitation before the Server discovers it shall have the tier reduced by one, save for the group in Article 42-B.2.

### Article 42-C. The blacklist

42-C.1. The blacklist is a register of accounts that have been permanently banned or that have been found to have committed conduct falling under Article 42-B.2, impersonation of Staff or of the Owner, or organised fraud. The sole purpose of the register is the prevention of repeat offending.

42-C.2. Each entry records: the account identifier, the date of entry, the provision relied upon, and the case file number. The Server shall not record information beyond what is necessary for the purpose in Article 42-C.1.

42-C.3. The retention period is 24 months from the date of entry, save for the group in Article 42-B.2 and the group concerning harm to minors, which are retained without a time limit. On expiry the entry shall be deleted and shall not be relied upon as a ground for any decision.

42-C.4. A person named in the register shall be notified and may request a review once every 12 months through the [Single-Window Channel](https://discord.com/channels/1342729473245577267/1343099398720065559). The Server shall answer within 14 days and shall give reasons in writing.

42-C.5. The blacklist shall not be published. Staff may consult it only when handling a specific matter. Consultation outside that purpose is a Tier 5 violation by the Staff member concerned.

### Article 42-D. Prohibition of gifts and favour towards Staff

42-D.1. Staff shall not accept money, items having real monetary value, accounts, in-game benefits, or any other advantage from a Member, where that advantage is connected with a matter that the Staff member is handling or may handle concerning the giver.

42-D.2. A Staff member who receives a gift in ordinary social circumstances shall declare it to the Operations Board within 48 hours. Failure to declare is a Tier 4 violation by that Staff member, independently of whether the gift affected any decision.

42-D.3. A Member who gives or offers a gift in order to obtain leniency, to have a violation overlooked, or to obtain priority, shall be dealt with at Tier 5. An unsuccessful offer shall be dealt with as if it had been carried out.

42-D.4. A decision taken by a Staff member while receiving an undeclared advantage from a party shall be set aside and re-heard by another person. Setting the decision aside does not reduce the responsibility of the Member if the violation is established.

### Article 42-E. Responsibility of the inviter

42-E.1. A person who invites an account into the Server bears joint responsibility where that account commits conduct falling under Article 42-B.2 within 07 days of joining, and the inviter knew or ought to have known of that intention.

42-E.2. The responsibility in Article 42-E.1 is not strict liability. The inviter bears no responsibility if they establish that they did not know, or that they reported the matter to the Staff as soon as they knew.

42-E.3. An inviter who reports of their own motion before the conduct occurs is wholly relieved of responsibility, even where the conduct nevertheless occurs.

### Article 42-F. Prohibition of collective pressure

42-F.1. No person shall call for, organise or lead a number of persons in attacking, ridiculing, isolating or applying pressure to a person, even where that person has in fact committed a violation.

42-F.2. The fact that a person is at fault does not make conduct under Article 42-F.1 lawful. Dealing with violations is a matter for the Staff under the Enforcement Regulation, not a matter for the crowd.

42-F.3. The instigator shall be dealt with at Tier 5. A person who joins after a warning by the Staff shall be dealt with at Tier 3. A person who joins before any warning and stops as soon as they are told shall not be dealt with.

42-F.4. This Article applies where the person under pressure is a Staff member or the Owner, and where that person has left the Server.

### Article 42-G. The duty to de-escalate before sanctioning

42-G.1. Before applying a measure of Tier 3 or above for arguing, insult or personal conflict, the Staff member on duty shall carry out three steps in full: give one public reminder, separate the two sides from the exchange, and record the time of both steps.

42-G.2. Article 42-G.1 does not apply, that is to say the Staff may act at once, to the safety group: threats, harm to minors, dissemination of malware, fraud in progress, and destruction in progress.

42-G.3. A measure applied in disregard of Article 42-G.1, outside the cases in Article 42-G.2, shall be set aside on appeal, and the Staff member who applied it bears responsibility under the Staff Rules.

### Article 42-H. Protection of a good-faith reporter

42-H.1. A person who reports a violation that they believe to be genuine shall not be dealt with for having reported it, even where verification shows that there was no violation.

42-H.2. Article 42-H.1 does not protect a person who reports knowing that the content of the report is false. That knowledge shall be established and shall not be presumed from the fact that the report was not made out.

42-H.3. Every act of retaliation against a reporter, comprising attack, isolation, disclosure of identity, or the imposition of a disadvantage within the Server, shall be dealt with at Tier 6 and no amnesty is available.

## CHAPTER VIII-C - SCOPE OF JURISDICTION, INFRASTRUCTURE AND LIFECYCLE

### Article 42-I. Jurisdiction as to territory and as to person

42-I.1. The Community Legal Framework binds every Member, irrespective of nationality, place of residence or place of access. The basis of the binding is the act of clicking to accept on joining and continued activity in the Server, not the place where the Member lives.

42-I.2. The Server's power of enforcement is confined to the Server and to the extent that the Discord platform permits. The Server has, and claims, no authority beyond that scope.

42-I.3. For a Member residing outside Vietnam, three rules apply together: a) the relationship between the Member and the Server is governed by the law of Vietnam under the Terms of Service, but no rule in the Community Legal Framework shall be read as a waiver of a right that the law of the Member's place of residence confers on them and does not allow to be waived; b) where a provision of the Community Legal Framework conflicts with a mandatory provision of the law of the Member's place of residence, that mandatory provision applies to that Member alone, and the remainder of the Community Legal Framework remains in force; c) the Server shall not invoke geographical distance to refuse to receive an appeal, and shall not invoke foreign law to refuse an obligation of its own.

42-I.4. The Vietnamese text is the authoritative version. A translation is for reference only. Where the two differ, the Vietnamese text applies, save where the reading under the translation is more favourable to the Member in the very matter under consideration.

### Article 42-J. Bots and automated tools of third parties

42-J.1. Only the Owner may bring a bot or an automated tool into the Server. Members and Staff shall not add one, shall not grant it permissions, and shall not authorise a third party to add one in any form.

42-J.2. Before a bot is brought in, the Owner or the person designated by the Owner shall determine and record: what data that bot collects, where it is stored, for how long, and who operates it. A bot for which those four points cannot be determined shall not be brought in.

42-J.3. The Server is responsible for the processing of Members' personal data carried out by bots operating in the Server, to the extent that the Server has permitted that bot to operate. The list of bots in operation and the purpose of each is published in the [official rules channel](https://discord.com/channels/1342729473245577267/1342766172000616490).

42-J.4. A Member who adds a bot, or who uses an automated tool to collect the data of other Members, shall be dealt with at Tier 5. Where the data collected is taken outside the Server, the tier is 6 and no amnesty is available.

42-J.5. On discovering that a bot processes data beyond the scope determined under Article 42-J.2, the Server shall remove that bot at once, give notice in the official announcement channel within 72 hours, and state which data may have been affected.

### Article 42-K. Offline events and minors

42-K.1. A minor may attend an official offline event only with the written consent of a parent or guardian, submitted before the event and kept in the event file.

42-K.2. A minor shall not attend alone. A parent, a guardian, or an adult designated in writing by the guardian shall accompany the minor throughout the event.

42-K.3. The Server neither organises nor permits, within the framework of an event: activities involving alcohol in respect of minors, activities at night outside the published hours, and any activity that separates a minor from the accompanying person.

42-K.4. Photographing and recording a minor requires the separate consent of the guardian, distinct from consent to attend. The guardian may withdraw consent at any time; the Server shall remove the images concerned within 07 days of receiving the request.

42-K.5. The three obligations in Articles 42-K.1, 42-K.2 and 42-K.4 shall not be waived by agreement, shall not be replaced by oral consent, and shall not be presumed from the presence of the guardian.

### Article 42-L. Rights in content created at events and in shared activity

42-L.1. A Member retains copyright in the content they create. The Server does not take an assignment of copyright and does not require a Member to assign it.

42-L.2. On attending an official event, a Member grants the Server a non-exclusive, royalty-free and revocable licence to use images and recordings in which they appear, for the purpose of archiving and presenting the Server's activity.

42-L.3. The licence in Article 42-L.2 does not extend to: use in paid advertising, transfer to a third party, or use in a way suggesting that the Member endorses a product or a party. Each of those three requires separate written consent on each occasion.

42-L.4. A Member may withdraw the licence at any time by a request through the [Single-Window Channel](https://discord.com/channels/1342729473245577267/1343099398720065559). The Server shall remove the content concerned within 14 days. The withdrawal has no retroactive effect on copies already published beyond the Server's control, but the Server shall not publish anew.

42-L.5. The Server shall not commercialise content created by a Member without a separate written agreement with that Member stating the scope and the share of any benefit.

### Article 42-M. Procedure for reinstatement after a sanction

42-M.1. A person who has been permanently banned may apply for reinstatement after 12 months from the date of the decision, through the [Single-Window Channel](https://discord.com/channels/1342729473245577267/1343099398720065559) or [legal@donquaan.com](mailto:legal@donquaan.com).

42-M.2. No application may be made, and the Server shall not consider one, in three groups: conduct harming minors; intentional facilitation of the destruction group under Article 42-B.2; and retaliation against a reporter under Article 42-H.3.

42-M.3. The application shall state: the conduct committed, the applicant's present understanding of that conduct, and specific undertakings for the return. An application that merely asserts injustice without new evidence shall be handled under the appeal procedure in the Appeals Regulation, not under this Article.

42-M.4. The Server shall answer within 30 days and shall give reasons in writing. A refusal shall state specific grounds; it shall not be refused on a general ground.

42-M.5. A person reinstated is subject to a probation period of 06 months. During that period, a violation of Tier 3 or above restores the earlier sanction, and that person may not apply again.

42-M.6. A refusal on one occasion does not bar a further application, at the earliest 12 months after the most recent answer.

### Article 42-N. Orderly wind-down

42-N.1. Where the Owner decides to wind down the Server, the Owner shall announce it in the [official announcement channel](https://discord.com/channels/1342729473245577267/1529782982016110642) and at the [legal framework page](https://donquaan.com/discord) at least 30 days in advance.

42-N.2. Within the notice period the Server shall carry out three things in full: receive and dispose of open appeals; refund virtual items and in-platform currency under the Terms of Service §25.4(c) to those who request it; and provide a data extract to Members who request one under the Privacy Policy.

42-N.3. After the wind-down the Server shall delete Members' personal data in accordance with the retention periods in the Privacy Policy §14, save for the part that must be retained under the law or the part that is the subject of a matter not yet concluded.

42-N.4. The wind-down gives rise to no obligation of compensation on the part of the Owner towards Members, provided that the Owner has carried out Articles 42-N.1 and 42-N.2 in full. That is a condition, not a unilateral promise.

42-N.5. The wind-down does not terminate three obligations: confidentiality of a reporter's identity under the Staff Rules §29.7; confidentiality of internal information under Article 42-A; and any refund obligation that arose before the date of the wind-down.

## CHAPTER IX - ENFORCEMENT, APPEALS AND FINAL PROVISIONS

### Article 41. Sanction framework and instruments

41.1. The instruments of enforcement are: the informal reminder (Article 4.9(a)); a reminder entered in the record; removal or correction of Content; timeout; mute; withdrawal of channel access; withdrawal of a role; temporary ban; permanent ban; and the interim and emergency measures under Articles 4.4 and 27.5. The assignment of instruments by tier shall follow the table in Article 3.1, the default ladder in Article 3.9 and the range set by the individual Article; Staff shall not apply any penalty outside this list, shall not name and shame, shall not impose discretionary penalties, and shall not pronounce oral sanctions without a record. Detailed enforcement procedure: the canon is contained in ENF.

41.2. For every sanction of MEDIUM tier or above, the person sanctioned shall receive: the provision relied upon, a description of the conduct, the duration, and the avenue of appeal. A sanction not accompanied by this information is procedurally deficient and shall be dealt with under Article 4.2.

41.3. A RED violation detected by the Server shall at the same time be proactively reported to Discord Trust and Safety; this is a fixed policy intended to protect the community and to demonstrate good faith in moderation.

41.4. Tiering of adjudicative authority: everyday sanctions shall by default be handled by Staff along the ladder in Article 3.9. Special cases (Article 3.9) shall be handled by the Owner or by senior Staff; Staff may not deal with them unilaterally and alone. The Owner may intervene immediately in an emergency or a serious situation; every direct intervention by the Owner shall be entered in the record under Article 4.2 and the person sanctioned shall retain the full right of appeal under Article 42.

### Article 42. Appeals - a single window

42.1. All appeals against sanctions shall be received solely at the [Single-Window Channel](https://discord.com/channels/1342729473245577267/1343099398720065559); a person who can no longer access the Server, for example while banned, shall use the e-mail address [support@donquaan.com](mailto:support@donquaan.com). The ticket form shall take precedence. Staff are prohibited from discussing a sanction through direct messages; a direct message shall be valid only where Staff have scheduled it in advance within a ticket, and a Staff member who initiates a direct message outside the procedure commits a violation; every direct message enquiring about a sanction shall receive exactly one redirecting sentence pointing to the appeal window. A Member who messages several Staff about the same sanction shall not be sanctioned; every Staff member shall answer consistently with that redirecting sentence. Detailed appeals procedure: the canon is contained in APL.

42.2. The person deciding an appeal shall not be the person who imposed the sanction, shall not have been on the same duty shift, and shall have no relationship with the parties; where the person complained of is the most senior Staff member or the person responsible for the appeals system, the case record shall be transferred to the alternative mechanism laid down in the Staff Policy, on the principle that a person complained of shall never touch a case record concerning themselves. Time limits: 72 hours for LIGHT and MEDIUM sanctions, and 7 days for HEAVY sanctions. Outcomes: the sanction is upheld, reduced or annulled. A sanction may be increased on appeal only where the review discloses new evidence of more serious conduct or of fraud in the original record, and only by decision of the panel under Article 42.4; a sanction shall not be increased because the reviewer takes a stricter view.

42.3. Every sanction passes through the same window, including a sanction imposed directly by the Owner or arising from an emergency intervention by the Owner (Article 41.4). There exists no sanction exempt from appeal. Where the Server is wrong: the sanction shall be annulled within 24 hours, the record shall be deleted, and a public apology in the standard template shall be issued in the place where the sanction was announced.

42.4. A second-instance appeal (final) shall be examined by a panel of 3 unconnected Staff; the panel mechanism shall be activated progressively in accordance with the recruitment roadmap (Article 2.3). After the final instance, a repeat appeal on the same grounds unaccompanied by new evidence shall be refused automatically.

42.5. The outcome of an appeal shall be published to the minimum extent (the sanction upheld, varied or annulled, by reference to the corresponding group of provisions), without publishing private content and without naming any person.

42.6. Standard for applications submitted by e-mail or ticket: an application for support, a report or an appeal shall include the username and user ID of the sender and, where applicable, of the persons concerned; a clear statement or report; evidence where available (blurred screenshots and crops lacking Context should be avoided, in accordance with the evidentiary standard in Article 4.3); and a clear purpose (what support is needed, which sanction is appealed, who is reported). An application with no clear purpose: Staff shall request completion once before considering any measure; where, after that request, the application remains junk or purposeless: a warning or a timeout of 1 to 24 hours according to gravity; e-mail spam or sabotage of the intake system: a timeout exceeding 1 day according to gravity. Mandatory balance: this measure applies only to junk applications or deliberate harassment; a person who expresses themselves clumsily but in good faith shall not be sanctioned, in accordance with the principle of protecting good-faith reporters (Articles 26.4 and 26.5).

### Article 43. Evidence, logs and personal data

43.1. The Server maintains moderation logs (sanctions, Content removed for investigative purposes, case records) under the data policy published at [PRV](https://donquaan.com/discord/privacy) - the canonical instrument on data - which states the categories of data, the purposes, the retention periods and the persons granted access by level. Standard retention periods: moderation logs 24 months · bot logs 90 days · prize-award information 30 days · the confiding channel is logged like every other channel, no channel lying outside the logging area, access to the logs of the confiding channel being classified at Access Level 2 (Head Admin and above, and the Owner, only). Special logs - a narrow list comprising personnel logs, permission logs, special violation records and special context - are retained indefinitely, kept internal, and published only in anonymised or summary form, save where there is a legal obligation to provide them to the competent authorities. Roles entitled to view logs are governed by the three-level permission scheme laid down in PRV: ordinary logs (moderation logs, bot logs, sanction records) - all serving Staff; special logs - Head Admin and above, and the Owner, only; safety and child-protection records - a narrow group of 2 to 3 persons identified in advance for each matter. The data protection contact point is the Owner, with the Head Admin as alternate; the position of Head Admin is appointed by the Owner and announced in the [official announcements channel](https://discord.com/channels/1342729473245577267/1529782982016110642), taking effect from the moment of announcement; where no person holds the position, the competence lies with the Owner and shall be transferred to the legal entity once that entity is established. Members have the right to know what the Server logs. The policy states expressly that bot logs may record deleted messages for investigative purposes.

43.2. Staff access to logs is granted solely for the purpose of moderating a specific matter; using logs to pry into private life, to recount matters externally, or to exert pressure is a serious Staff violation to be dealt with under the Staff Policy; where data is disseminated, the Server shall stand with the victim in reporting the matter under Luật 91/2025/QH15 (Law on Personal Data Protection) and Nghị định 356/2025/NĐ-CP (Decree detailing the Law on Personal Data Protection).

43.3. A request for erasure of personal data under Luật 91/2025/QH15 (Law on Personal Data Protection) and Nghị định 356/2025/NĐ-CP (Decree detailing the Law on Personal Data Protection) shall be met by the Server so far as technically feasible, by a written reply in the standard template; data serving a pending appeal, a legal obligation, or the legitimate interests of a victim (for example doxxing evidence awaiting a report) shall be retained on stated grounds, for a stated period and with access frozen; such retention constitutes the exercise of a statutory exception.

43.4. The Server shall never publish raw logs containing personal data in order to rebut public opinion; corroborating material shall be provided only to Discord, to the competent authorities, or in the form of an extract with third-party identities redacted.

### Article 44. Amnesty

44.1. A permanent ban - save for RED sanctions under Article 23 (child safety), Article 24 (NCII and deepfakes) and Article 26 (fabrication of evidence), which are not amnestiable - may be considered for amnesty after at least 12 months, through the official appeal window (Article 42.1), according to published criteria: elapsed time, attitude, remedy of the harm, and absence of repetition elsewhere. A RED sanction under Article 13.1(a) may be considered only together with a written legal risk assessment.

44.2. Amnesty shall be decided by the panel on the case record; not by community vote, not by collective campaigning, and not by the personal sympathy of any person, including the Owner.

### Article 45. Amendment, entry into force, continuity of operation and the Owner's undertakings

45.1. This Code shall be amended in writing: a minor amendment shall be published at least 7 days before the date of entry into force; a major amendment affecting Members' rights shall be published at least 30 days before the date of entry into force, save for an emergency patch in a safety or legal area, which shall take effect immediately and be published at the same time. Permanent closure of the Server shall be notified at least 30 days in advance. Every version shall be retained and capable of comparison. Three categories of matter shall never be put to a majority vote: safety (children, self-harm), legal matters, and personnel; other matters may be put to the community in accordance with a poll classification published in advance (binding poll / consultative poll / no poll). Where the Owner decides otherwise than in accordance with the result of a consultative poll for reasons of safety or law, the decision shall be taken in accordance with the poll classification as published.

45.2. Amendments may only make the standard stricter or clearer in the areas of child safety, prevention of fabricated evidence and personal data; they may not relax it.

45.3. The position of the Owner and the written undertakings, established in advance and irrevocable: (a) the Owner is the supreme authority of the Server as to law, personnel and finance (details in STF and OWN); at the same time the Owner is subject to the whole of this Code as any Member is, including the speech standard and the sanction framework; (b) the Owner may intervene immediately in an emergency or a serious situation; every direct intervention by the Owner shall be fully recorded under Article 4.2, and the person sanctioned shall retain the full right of appeal through the proper window under Article 42; there exists no sanction exempt from appeal; where a sanction is wrong, it shall be annulled and an apology issued in accordance with the procedure in Article 42.3; (c) everyday sanctions shall by default be handled by Staff along the ladder in Article 3.9; special cases shall be handled by the Owner or by senior Staff and Staff may not deal with them unilaterally and alone (Articles 3.9 and 41.4); (d) where the Owner is the subject of a complaint, including an anonymous complaint sent simultaneously to Staff, the Owner shall stand outside the entire case record; intake and investigation shall be led by the Head Admin together with an independent responsible person under the written SOP in STF, on the following principles: every complaint shall be taken seriously irrespective of its form, there shall be no negotiation with ultimatums, there shall be no counter-attack against the complainant before a conclusion is reached, and communication shall pass through the single contact point (Article 38.3); any intervention by the Owner in a case record concerning themselves is a violation and shall be published; (e) no exception shall be granted without a reason recorded in writing and capable of publication.

45.4. This Code forms part of the Community Legal Framework and shall be read together with TOS, ENF, APL, DIS, PRV, STF and OWN, together with the Framework Event Rules and the safety SOPs. Overlapping areas shall be construed in accordance with the canonical instrument: discipline and evidence under ENF; appeals under APL; data under PRV; Official Channels under TOS. Where the instruments conflict as to the conduct of Members, this Code shall prevail; as to safety, whichever instrument protects persons more strongly shall prevail.

45.5. Continuity of operation and succession: (a) delegation in absence: where the Owner cannot be reached for more than 72 consecutive hours through any Official Channel, temporary operational authority shall vest only in Staff of Head Admin rank or above, or in a person holding a valid written confirmation from the Owner; the scope of that delegation is equal to the powers of a Head Admin and is temporary, and shall not be exceeded, in particular: no expenditure outside a pre-existing written authorisation under Article 16.6(c), no amendment of any instrument within the Legal Framework, and no change to senior personnel; (b) an emergency successor shall be designated in advance by the Owner in writing (the identity being held in STF), together with the activating conditions and the limits on the powers of the temporary successor; (c) loss-of-control scenario on Discord: where the Server or the Owner's account is suspended or seized, the sole channel of verification and official announcement is the website under Article 2.2; the compliance record (moderation logs, SOPs executed) shall be kept ready as the basis for an appeal to Discord; (d) any backup Server, if established, shall be held in the Owner's own name before it comes into existence; no other person may set up a backup version (Article 33.1(c)).

---

## APPENDIX A - REFERENCE TABLE: CONDUCT AND VIOLATION TIER

| Conduct | Article | Tier |
| --- | --- | --- |
| Swearing not directed at anyone; ordinary spam; wrong channel; voice etiquette | 6.5, 14.1, 28.1, 29.4 | LIGHT |
| Self-enforcement in place of Staff (a single good-faith reminder: no violation) | 4.1 | LIGHT to MEDIUM |
| Enquiring to buy an item on the prohibited-offering list (first occasion) | 16.2 | LIGHT |
| Junk e-mail or ticket applications after a request for completion | 42.6 | Warning to timeout of 1-24 hours (disruptive spam: over 1 day) |
| Personal attack; repeated coarse joking in public | 6.1 | MEDIUM to HEAVY |
| Isolated first instance of sexist denigration | 7.3 | MEDIUM |
| Advertising or self-promotion; disruptive spoilers | 15, 17.2 | MEDIUM |
| Cumulative aggression (first establishment of the pattern) | 10.3 | MEDIUM |
| Recording or disseminating a proceeding concerning a sanction; recording voice without consent | 4.6, 29.3 | MEDIUM to HEAVY |
| Sharing cracked, leaked or pirated content (first occasion) | 36.1 | MEDIUM |
| Harmful fabricated assertion | 18.2 | MEDIUM to HEAVY |
| Alternate account used for advantage; mechanism exploitation; trading virtual currency | 32.1, 34.4, 16.8(b) | MEDIUM to HEAVY |
| Sharing executable files (prohibited in every channel) | 25.2 | MEDIUM |
| Regional, sex-based, religious or racial discrimination | 7 | HEAVY |
| Harassment; retaliation against a reporting person | 8 | HEAVY |
| Pornographic content beyond the standard; gruesome content | 11.2, 12.1 | HEAVY |
| Systematic provocation | 10.1 | HEAVY |
| Offering items on the prohibited list; self-bots | 16.2, 34.1 | HEAVY |
| Threats with locational detail; arranging a meeting to settle a dispute | 21.1 | HEAVY to RED |
| Dissemination of internal content; distorted dissemination | 37 | HEAVY to RED |
| Unauthorised use of the Server's name or logo; harmful spontaneous statements | 38 | HEAVY to RED |
| Fundraising appeals within the Server | 5.6 | Removal together with guidance |
| Doxxing | 20 | RED |
| CSAM, grooming, sexualisation of a Minor | 23 | RED - non-amnestiable |
| NCII, deepfakes of real persons | 24 | RED - non-amnestiable |
| Fabrication of evidence; organised false reporting | 26 | RED - non-amnestiable |
| Content within the framework of Điều 117 and Điều 331, Bộ luật Hình sự (the Penal Code); real-money gambling; narcotics | 13.1 | RED |
| Organising paid-entry games of chance with prizes; systematic currency markets | 16.8 | RED |
| Phishing, QR-code fraud, malware, fraudulent appropriation of property | 25, 16.4 | RED |
| Raiding, brigading, coordinated attack; ban evasion by alternate account | 27, 32.2 | RED |
| Impersonating the Owner, Staff or Discord; counterfeit Servers; e-mail or platforms posing as Official Channels | 33 | RED |

## APPENDIX B - ORDER OF ACTION FOR STAFF ON DUTY

Staff on duty shall carry out the following six steps in this order:

1. Determine whether the Content falls within the emergency RED list (Article 13.1: infringement of national security, CSAM, terrorism, real-money gambling, narcotics, NCII; Article 25.1: phishing, QR codes, malware). If so: run the emergency SOP at once, with the target of removal within approximately 1 hour, performable even when on duty alone: record the metadata → remove → report to Discord → ban → report upwards along the emergency notification chain (ordinary matters: notify a Moderator; the most serious cases - indicia of a criminal offence, CSAM, threats to life: notify only an Admin who is online; do not notify the Head Admin unless the situation is simultaneously dangerous, urgent and serious; do not notify the Owner - the emergency notification chain follows the safety SOP in PRV, and the role hierarchy follows STF). Do not consult, do not comment, and do not re-quote the Content.
2. Determine whether there is a self-harm signal (Article 22). If so: treat it as genuine - respond using the template, provide the hotlines 111 and 115, report to Discord, and report upwards regardless of the hour. Do not delete a post calling for help as junk content.
3. Determine whether there are indicia of conduct targeting a Minor (Article 23). If so: apply a protective interim ban at once, stating expressly "INTERIM - safety measure" → report to Discord → report upwards. Do not deal with the matter publicly and do not name any person.
4. Determine whether a Staff account or a bot is engaged in destructive conduct (Article 35.5). If so: pull the circuit-breaker at once - strip roles, disable the bot, lock channels. This is a power and a duty, not an excess of authority; the review shall be carried out afterwards.
5. In all other cases, determine whether a sanction must be imposed at once. If not: use the soft ladder first - the informal reminder (Article 4.9(a)) → locking the topic or slow mode (Article 4.8) → an interim measure expressly marked "INTERIM" (Article 4.4). Special cases (Article 3.9): do not deal with the matter unilaterally; apply interim measures only and then refer it to the Owner or to senior Staff. When on duty alone: apply interim measures only; the formal sanction shall await confirmation by a second person within 24 hours (Article 3.5).
6. Log everything done within 15 minutes (in an emergency: 1 hour), including the provision relied upon, the evidence and the time. No record, no sanction (Article 4.2). Where the tier of a sanction is in doubt, choose the lower tier together with an interim measure; a sanction may be raised only through the proper procedure.

```json
{ "@context": "https://schema.org", "@graph": [ { "@type": "Person", "@id": "https://donquaan.com/#person", "name": "Nguyen Vu Dong Quan", "alternateName": "DonQuaan", "url": "https://donquaan.com/", "image": "https://donquaan.com/og-hero.png", "jobTitle": "Gemini Certified Faculty · Google AI Specialist", "description": "I believe in people, not tools. Teaching and applying Google AI; running Discord communities and systems; design and development for Roblox, Minecraft and the web; systems testing.", "email": "mailto:contact@donquaan.com", "knowsAbout": [ "Google AI", "Gemini", "Community operations", "Discord", "Roblox", "Minecraft modpacks", "Web development", "Systems testing" ], "knowsLanguage": [ "Vietnamese", "English" ], "hasCredential": [ { "@type": "EducationalOccupationalCredential", "credentialCategory": "certification", "name": "Gemini Certified Faculty", "recognizedBy": { "@type": "Organization", "name": "Google" }, "url": "https://edu.google.accredible.com/529911e4-a7fb-42b6-9c9f-50d29e633430" }, { "@type": "EducationalOccupationalCredential", "credentialCategory": "certification", "name": "Kaggle Learn certificates (17) and the Data Science graduate badge, 18 images", "recognizedBy": { "@type": "Organization", "name": "Kaggle" }, "url": "https://www.kaggle.com/nguyenvudongquan" }, { "@type": "EducationalOccupationalCredential", "credentialCategory": "certification", "name": "HubSpot Academy certifications (15)", "recognizedBy": { "@type": "Organization", "name": "HubSpot Academy" }, "url": "https://app.hubspot.com/academy-profile/member/94801453" } ], "address": { "@type": "PostalAddress", "addressLocality": "Da Nang", "addressCountry": "VN" }, "sameAs": [ "https://www.facebook.com/NguyenDonQuaan", "https://x.com/DonQuaanVN", "https://www.youtube.com/channel/UCvqlcKf1nm9i2LeH9hFQQYA", "https://github.com/DonQuaan", "https://www.linkedin.com/in/donquaan", "https://www.twitch.tv/donquaan_tkz", "https://open.spotify.com/user/31xr7kgwysteud3urdhzrv5ixc2q", "https://www.curseforge.com/members/yangdawn", "https://www.kaggle.com/nguyenvudongquan", "https://app.hubspot.com/academy-profile/member/94801453", "https://discord.com/invite/sangtraan" ] }, { "@type": "WebSite", "@id": "https://donquaan.com/#website", "url": "https://donquaan.com/", "name": "DonQuaan", "alternateName": "Nguyen Vu Dong Quan", "description": "Nguyen Vu Dong Quan, Gemini Certified Faculty · Google AI Specialist, Da Nang. I believe in people, not tools. Shipped work, real certificates, the Sangtraan Discord community.", "inLanguage": [ "vi", "en" ], "publisher": { "@id": "https://donquaan.com/#person" } }, { "@type": "ProfilePage", "@id": "https://donquaan.com/#webpage", "url": "https://donquaan.com/", "name": "DonQuaan | Nguyen Vu Dong Quan", "isPartOf": { "@id": "https://donquaan.com/#website" }, "about": { "@id": "https://donquaan.com/#person" }, "mainEntity": { "@id": "https://donquaan.com/#person" }, "primaryImageOfPage": "https://donquaan.com/og-hero.png", "inLanguage": "en" } ] }
```
