---
title: "Enforcement Policy - Discord Server | DonQuaan"
description: "Disciplinary principles, the sanction ladder, evidentiary standards and the handling procedure."
image: "https://donquaan.com/og-hero.png"
url: "https://donquaan.com/en/discord/rules/enforcement"
lang: "en"
---

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

ENF Enforcement Policy

# Enforcement Policy

Version 4.0 · Issued 11/08/2026 · Effective 18/08/2026 · Legacy ref: VK-03 · Ch.I-IV

# Enforcement and Sanctions Policy

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

This document is the Enforcement and Sanctions Policy (cite code: ENF) forming part of the DonQuaan Community Legal Framework. It sets out the principles governing the handling of violations, the sanction scale, the procedure for issuing a sanction, the evidentiary standard and the record-keeping regime applicable at the Discord Server "DonQuaan", identifier 1342729473245577267. This document shall be binding upon every subject listed in Article 0.2 from the effective date stated in the document control block, subject to the non-retroactivity principle in Article 5.

### Article 0. Scope and rules of reading

0.1. This document governs: the conditions of validity of a sanction; the sanction scale and interim measures; aggravating and mitigating circumstances; the procedure for opening a case; the evidentiary standard; and the regime for records and cross-audit.

0.2. Personal scope: all Members; all Staff (including trial-mod, mod, head mod, admin and head admin); and the Owner of the Server.

0.3. Relationship with higher sources: this document only supplements and sets a higher standard than the [Discord Terms of Service](https://discord.com/terms), the [Discord Community Guidelines](https://discord.com/guidelines) and the laws of Vietnam. No provision of this document may be construed as replacing or conflicting with those sources. Any conduct prohibited by Discord shall likewise be prohibited at the Server, even where this document does not restate it.

0.4. Allocation of canon: this document is canon on discipline and evidence; every other document in the Community Legal Framework, when referring to sanctions, shall cross-refer to this document and shall not restate the detail. The Privacy Policy (PRV) is canon on data. The Terms of Use (TOS) is canon on Official Channels. Matters of finance and donations, technical security, events, Staff personnel and succession shall be handled under the corresponding thematic document.

0.5. The procedures for complaint, appeal and amendment are laid down in the Complaint and Appeal Policy (APL). Any reference in this document to Article 24 and following shall be read as a reference to APL.

0.6. Citation convention: a reference within this document is written as "Article 7.5"; a reference to another document is written with its cite code, for example "CoC Section 6.3".

---

## CHAPTER I - FOUNDATIONAL PRINCIPLES

### Article 1. The four conditions of validity of a sanction

1.1. A sanction shall be valid only where all four of the following conditions are met simultaneously: (a) A provision was promulgated before the time the conduct occurred, in accordance with the prohibition of retroactivity in Article 5; (b) A valid case record exists, with traceable evidence in accordance with Chapter IV; (c) The person issuing the sanction has no conflict of interest with any party, in accordance with Article 16; (d) The sanctioned person has a route of complaint to an unconnected level, in accordance with APL Chapter VI.

1.2. Where any condition set out in Article 1.1 is absent, the sanction shall automatically be void upon complaint, even where the violation did in fact occur. A sanction void for procedural defect shall not prevent Staff from opening a new, procedurally correct case for the same conduct, within the limitation period laid down in Article 17.

1.3. Safety exception. For cases falling within the Red Sanctions groups 9.1(a), (b) and (e), a procedural defect shall not invalidate a protective measure (protective ban, removal of Content, report to Discord). A procedural defect in this group shall give rise only to an obligation to re-establish the record correctly within 72 hours and to open disciplinary proceedings against the person who erred; the protective measure shall be maintained until a conclusion is reached. No subject may invoke a procedural defect to demand restoration of access for a person under suspicion in a safety group where no finding of innocence has been made.

### Article 2. Equality before the policy, without exception

2.1. The following factors may not be used as variables of a sanction, whether in aggravation or in mitigation: number of followers; offline reputation; level of contribution to the Server (boosts, donations, building effort, seniority); relationship with Staff or the Owner; public pressure inside or outside the Server.

2.2. A Member's contribution shall be recognised in a separate honours system, published in the Server's role-explanation channel, where all information on roles, including contribution roles, is explained. The honours system shall be entirely separate from the disciplinary system. Contribution may not be used to offset, mitigate or exempt a sanction. Recognition of contribution shall not create any ownership right, veto right or equity interest in the Server.

2.3. A sanction issued by the Owner or by any level shall pass through the same case procedure, the same evidentiary standard and the same route of complaint under APL Section 30. No sanction is exempt from complaint.

2.4. Staff are subject to a higher standard of conduct than Members: for identical conduct, the range applicable to Staff shall be the range applicable to Members plus one tier, not exceeding Tier 6, together with consideration of role discipline under STF.

### Article 3. Evidence precedes assertion

3.1. No record, no sanction. No subject, including the Owner, may execute a penalty of Formal Warning (Tier 2) or above without a case record in accordance with Article 20; the time of opening the record is governed by Article 15.1. Emergency situations under Article 18 may be executed first, with the record completed within a hard deadline.

3.2. The number of reports is not evidence. Ten reports of identical content from ten interrelated accounts shall count as one source.

3.3. A screenshot that cannot be cross-checked is not evidence; its value is limited to Tier C evidence under Article 14.3.

### Article 4. Crowd pressure is not a circumstance

4.1. Any form of collective pressure (countdowns demanding a ban, mass threats to leave the Server, repeated tagging of the Owner, external campaigns) shall neither shorten the handling procedure nor aggravate or mitigate the level of sanction.

4.2. Where a case provokes a wide reaction, Staff shall apply interim measures under Article 8 and publish in the form set out in Annex D.

4.3. Three categories of matter may not be submitted to community consultation in any circumstances: safety (children, self-harm, violence); legal matters; and individual disciplinary sanctions. For all other matters, the value of the consultation result (advisory or decisive) shall be determined by the governance document before the consultation is opened; a consultation that does not state its character shall be deemed advisory.

### Article 5. Prohibition of retroactivity

5.1. Conduct occurring before the effective date of the corresponding prohibitory provision shall not be sanctioned. This document applies from the effective date of 18 August 2026 and shall not apply retroactively to conduct occurring before that date.

5.2. Where an exploited loophole is discovered, that is, harmful conduct for which no prohibition yet exists: (a) the rules shall be amended for the future and published; (b) anomalous results obtained from the loophole may be annulled under the mechanism-fraud provision in Article 11.2, provided that provision already existed; (c) the person exploiting the loophole shall not be sanctioned for conduct occurring before the date of amendment.

5.3. The sole exception to Article 5.1: conduct already prohibited by the [Discord Terms of Service](https://discord.com/terms), the [Discord Community Guidelines](https://discord.com/guidelines) or the laws of Vietnam at the time it occurred shall be handled under Article 9 or the corresponding range, irrespective of whether the Server's own rules had yet recorded it, since those sources are permanently in force at the Server under Article 0.3.

### Article 6. The enforcement power belongs to Staff alone

6.1. Only serving Staff have authority to execute disciplinary measures. Members may not deal with other Members themselves: they may not pronounce sanctions in place of Staff, may not demand that others delete posts in the name of the rules, and may not publicly denounce violations. A Member who discovers a violation shall report it through the [Single-Window Channel](https://discord.com/channels/1342729473245577267/1343099398720065559) or to [support@donquaan.com](mailto:support@donquaan.com); use of the [Single-Window Channel](https://discord.com/channels/1342729473245577267/1343099398720065559) is preferred.

6.2. Good-faith reports shall be protected in all circumstances under APL Section 29. Self-help in place of Staff as described in Article 6.1, where repeated after one formal reminder, constitutes disruption of the handling process and shall be sanctioned at Tier 1 to 2 of the scale.

---

## CHAPTER II - THE SANCTION SCALE

### Article 7. The standard progressive scale

7.1. The scale comprises six tiers, applied progressively according to the number of violations within the reset period laid down in Article 7.5:

| Tier | Form | Content | Minimum authority |
| --- | --- | --- | --- |
| 1 | Reminder | Written reminder (publicly on the spot or privately), recorded | 1 mod |
| 2 | Formal warning | Recorded warning (public or private), counted in the progressive chain | 1 mod |
| 3 | Mute / Timeout | From 1 hour to 7 days; a mute over 24 hours is a heavy timeout | 1 mod for a mute up to 24 hours; 2 approvers for a mute over 24 hours under Article 13 |
| 4 | Kick | Removal from the Server, with permission to return | 2 approvers |
| 5 | Temporary ban | From 7 days to 90 days | 2 approvers |
| 6 | Permanent ban | Removal from the Server without limit of time; the sanction follows the person, not the account, under Article 12 | 2 approvers, at least 1 of whom is head mod or above |

Exception as to authority: for Red Sanctions in the safety groups 9.1(a), (b) and (e) and in an emergency under Article 18, a mod on duty may execute an immediate interim protective ban and obtain the second approver under Article 13.3.

7.2. Conduct-based ranges. Each type of violation laid down in CoC has a range (minimum tier to maximum tier) published in the sanction range table on the [Legal Framework publication page](https://donquaan.com/discord). A mod shall select a level within the range; departure from the range requires the approval of 2 persons together with reasons recorded in the case record.

7.3. Progression. Repetition of conduct of the same group within the period in Article 7.5 shall have as its starting level the tier next above the tier most recently applied, not exceeding the ceiling of the range. A Tier 1 sanction is counted in the progressive chain and therefore gives rise to a right of complaint under APL Section 25.1.

7.4. There shall be no skipping of tiers for ordinary violations, save where an aggravating circumstance from the closed list in Article 10 applies. Each circumstance permits an increase of at most 1 tier; the total increase shall not exceed 2 tiers.

7.5. Reset period of the progressive chain (limitation period for repetition): sanctions in the light group (reminder, warning - Tiers 1 to 2) cease to count after 90 days without repetition; the medium group (mute, timeout - Tier 3) after 6 months; the heavy group (kick, temporary ban - Tiers 4 to 5) after 12 months; Red Sanctions never cease to count. After expiry, the earlier sanction shall remain in the record but may not be used as a basis for raising the tier.

7.6. Priority for self-correction. A person who admits the violation and does not repeat it may be considered for exemption or reduction under Article 10.2(a). Within one progressive chain, a person may receive at most 3 warnings (Tiers 1 to 2 combined, public or private); beyond 3, the next sanction shall start at Tier 3 as a minimum (mute, timeout), followed by a heavy timeout (mute over 24 hours, requiring 2 approvers under Article 13), a temporary ban and a permanent ban in accordance with the scale. Particularly serious violations falling within Red Sanctions shall not pass through this scale, in accordance with Article 9.2.

### Article 8. Interim measures

8.1. Interim measures comprise: interim timeout; interaction restriction; thread lock; provisional removal of Content; interim protective ban. An interim measure shall be applied where necessary to prevent continuing harm during review, on an evidentiary standard lower than that required for a concluding sanction: Tier B suffices; Tier C suffices for a measure that is not accusatory in nature, such as separation of contact.

8.2. Every notice of an interim measure must use the word "INTERIM" and must state: "This is an interim measure during review; it is not a finding of violation."

8.3. An interim measure shall have a maximum duration of 72 hours; it may be extended once with the approval of 2 persons, the extension not exceeding the original duration. Where the period expires without a conclusion, the interim measure shall lapse automatically, save in three cases: (a) Red Sanctions in the safety groups 9.1(a), (b) and (e) - the protective ban shall be maintained until a conclusion is reached; (b) an open security incident under Article 18 - the interim measure shall be maintained until the post-review under Article 18.3 is completed; (c) an interim measure arising under APL Section 26.2 - maintained until the competent level concludes, for a maximum of 14 days, after which, absent a conclusion, it shall lapse automatically.

8.4. Non-accusatory cooling measures (thread lock, slow-mode, locking a discussion thread) are official de-escalation tools. A mod may use them without accusing anyone; their use shall not create a violation record for those involved.

### Article 9. Red Sanctions - outside the progressive scale

9.1. The list of Red Sanctions is a closed list, amendable only under the amendment procedure in APL Section 35: (a) CSAM and any sexual abuse or solicitation of a minor; (b) NCII and sensitive deepfakes bearing the face or voice of a real person, irrespective of whether the victim is in the Server and irrespective of any claim of technical demonstration; (c) Doxxing, determined by context and intent: compiling or posting information identifying another person in a hostile context, irrespective of whether that information is publicly available; (d) Threats of violence with a real-location element; arranging an offline meeting to settle a dispute - immediate intervention is mandatory even where the expression is couched as a joke; (e) Content violating the criminal law of Vietnam, including conduct falling within the scope of Articles 117 and 331 of the Bộ luật Hình sự (the Penal Code), and incitement to terrorism or violence; (f) Organising or taking part in a model that collects money combined with an element of chance and a payout; trading or converting virtual coins into real money; (g) Fraudulent appropriation of property supported by Tier A or Tier B evidence, including impersonation of the Owner, Staff or the Server for fraudulent purposes; (h) Fabrication of evidence: creating or altering false Content (fake screenshots, AI-generated conversation logs, deepfake audio or video, coordinated false reports) so as to make others believe it genuine, in order to accuse, discredit or trigger the handling process. Satirical work that is plainly fictional and not intended to deceive does not fall within this item. To be handled under Article 9.4; (i) Coordinated attack (raid, _brigading_) as defined in Article 11.3; (k) Misappropriation or unlawful dissemination of a Member's personal data, including the use of access by Staff for purposes other than moderation, in accordance with Article 11.4.

9.2. Red Sanctions do not pass through the progressive scale. The default level is an immediate permanent ban, or an immediate interim protective ban together with a report to Discord Trust and Safety for groups (a), (b) and (e) under the separate safety procedure, together with monitoring for alternate accounts under Article 12. The protective action shall be taken first; the record shall be completed within 1 hour; the conclusion shall be issued thereafter; publication shall be carried out last or not at all. Cases involving children shall be handled confidentially, without naming any party.

9.3. For groups (a), (b) and (e), the accompanying obligation is to report to Discord Trust and Safety immediately and, where the legal threshold is met, to assist the victim in reporting to the competent authorities. The Server shall not investigate in their stead, shall not organise confrontation in their stead and shall not handle the matter publicly. Evidence in group (a) shall be preserved under the safety procedure: report together with recorded metadata, no download, no internal circulation.

9.4. Fabrication of evidence shall be sanctioned more severely than the conduct falsely alleged: permanent ban, not eligible for amnesty under Article 12.4, applicable to Members and Staff alike. Where actual damage to reputation results, the Server shall assist the victim in compiling a record so that the victim may report the matter under the law.

9.5. Good-faith violations touching Red Sanctions in point of content, for example posting violent content for the purpose of warning, or a victim publicly disclosing evidence containing another person's personal data under Article 14.8: the Content shall be removed in accordance with procedure, and no negotiation shall be entertained; a first-time poster acting without malice shall be handled on the ordinary scale at Tiers 1 to 2, or no case shall be opened against a victim who submits evidence through the wrong channel for the first time.

9.6. Self-harm and psychological crisis are not subjects of disciplinary sanction. A message of self-harm or suicide shall be handled under the life-safety procedure SOP-01, issued by the Owner and published in the [official announcement channel](https://discord.com/channels/1342729473245577267/1529782982016110642); where SOP-01 has not yet been issued, the principles in this clause shall apply directly: priority to connecting the person with support and reporting to Discord under the self-harm procedure; no deletion of a call for help before the support step has been taken, with visibility restricted only where the Content is liable to harmful spread; a mod shall not give medical or psychological advice but shall redirect to the official hotlines 111 (National Child Protection Hotline, 24/7, free of charge) and 115 (medical emergency), together with the support resources already published. The Server's support email is not a substitute for an emergency hotline. All related data is sensitive data and shall be accessed at the minimum level. Sustained aestheticisation of self-harm shall be handled under Article 11.5.

9.7. An account confirmed to be under 13 years of age shall not be treated as a violating subject. Handling shall be uniform and non-punitive: report to Discord under the Discord Terms of Service; removal from the Server with a neutral notice; no publication; no retention of data beyond the minimum required for the compliance record; no self-established child mode.

### Article 10. Aggravating and mitigating circumstances - closed list

10.1. Aggravation. Only the following items may be invoked; adding circumstances outside this list at the time of handling is prohibited: (a) Repetition within the period in Article 7.5; (b) Targeting a person in a markedly weaker position (a newcomer, a minor); (c) Conduct that is premeditated, prolonged or systematic; (d) Inducing others to violate as well; (e) Obstructing the handling process (deleting evidence, threatening witnesses, threatening Staff); (f) Violating while serving another sanction.

10.2. Mitigation: (a) Admitting the violation and remedying it before a case is opened. For a first violation in the light group, without repetition, exemption may be granted (stopping at a reminder not counted in the chain) or the tier reduced under Article 7.6; (b) Systematic provocation. When handling a case that is reactive in nature, a mod must review at least 14 days of interaction history between the parties before issuing a sanction; the provoked person shall receive a substantial reduction but shall not be wholly exempt, since context reduces the level of sanction but does not erase the conduct; the provoker shall be the subject of a separate case under Article 11.1 as an independent violation, without any requirement that any single utterance reach a serious threshold; (c) A first violation where the consequences have been remedied; (d) Linguistic misunderstanding confirmed by an assessor familiar with both contexts, applicable to allegations of discrimination arising in a multilingual setting.

10.3. Every circumstance invoked must be recorded in the case record together with evidence. A circumstance not appearing in this list has no effect.

### Article 11. Violations independent of the content of any individual message

11.1. Cumulative aggression. A course of conduct below the individual threshold (sarcasm, indirect attack, mocking quotation, derisive reactions) directed at the same person or group and sustained over time shall be handled by reference to a behavioural pattern over a log of at least 14 days. The standard of assessment is the understanding of an ordinary reader; a conclusion requires consultation between at least 2 mods.

11.2. Mechanism fraud. The use of automation, multiple accounts, exploitation of system faults, bot faults or rule faults to gain an advantage in results (points, prizes, benefits) shall lead to annulment of the anomalous result and handling within the applicable range, irrespective of whether the particular method was previously listed.

11.3. Coordinated attack. A conclusion requires at least 2 of the following 4 objective criteria: (i) an abnormal cluster of participation or activation in time; (ii) a common source or relationship; (iii) a content pattern following a common script; (iv) targeting of the same person or event. The conclusion must be approved by 2 persons. Where the criteria are met, interim mass measures may be applied under Article 18 together with mandatory post-review.

11.4. Abuse of authority and of data access, applicable to Staff only. Using the power to view channels, logs or records for purposes other than handling an assigned case (surveillance of private life, monitoring of individuals, disclosing Member information externally, using data to exert pressure) is an independent violation, within the Tier 5 to 6 range together with removal of role, irrespective of whether the information has been disseminated. Where an element of threat, coercion or dissemination is present, the matter shall be handled under Article 9.1(k) and the record transferred so as to assist the victim through legal channels (Luật 91/2025 (Law on Personal Data Protection) and Nghị định 356/2025 (the implementing Decree)). Written principle: moderation powers may be used for moderation purposes only.

11.5. Cumulative environmental drift. Where a channel or group drifts progressively away from the standard (18+ culture in a place where minors are present; aestheticisation of self-harm) without any identifiable date of an individual violation: step one is a non-accusatory structural measure under Article 8.4 (locking or resetting the channel, tightening permissions, issuing a standard-restoration notice, recording the date); step two is the opening of individual cases only in respect of conduct occurring after the standard-restoration notice, preserving the prohibition of retroactivity, save for conduct that in itself already violated an existing provision.

### Article 12. Permanent ban, ban evasion and amnesty

12.1. A permanent ban follows the person, not the account. A replacement account of a permanently banned person shall, upon discovery or report, be banned where identification is verified to the standard in Article 12.2, at the level of permanent ban.

12.2. Standard for identifying a replacement account: (a) admission by the party concerned; or (b) at least 3 independent, mutually consistent indicators (characteristic behaviour, time window, details known only to the former person, verifiable technical links). Similarity of writing style, standing alone, is never sufficient. The conclusion must be approved by a second person of head mod level or above.

12.3. A replacement account, once discovered, shall be banned. Time spent behaving well through a replacement account shall not count as a ground for reducing the original sanction.

12.4. Official amnesty route. A person permanently banned under the ordinary scale (Tier 6 by progression) may apply for review through the complaint channel after at least 12 months, together with a full self-disclosure, including declaration of any replacement account, made before discovery. A permanent ban imposed for a Red Sanction is not eligible for amnesty. The application shall be decided by the Appeal Board under APL Section 27 on published criteria: elapsed time, gravity of the original conduct, attitude and risk of repetition. Self-disclosure before discovery is a favourable circumstance; disclosure after discovery is not.

---

## CHAPTER III - PROCEDURE FOR ISSUING A SANCTION

### Article 13. The two-approver rule for serious sanctions

13.1. The following decisions require 2 independent approvers, named in the case record: a mute over 24 hours; a kick; a temporary ban; a permanent ban; annulment of an event result; publication of a sanction in a public channel; a conclusion as to a replacement account under Article 12.2; a conclusion as to a coordinated attack under Article 11.3.

13.2. The two approvers may not: both be a party or the reporting person; have a relationship requiring recusal under Article 16 with any party; or be direct subordinate and superior in a current evaluation period in relation to one another, in the case of Staff disciplinary sanctions.

13.3. Where an emergency leaves no time to obtain 2 approvers: execution may proceed first under Article 18, or a protective ban may be imposed under Article 9.2; the second approver shall confirm within 24 hours. Absent confirmation, the sanction shall be converted into an interim measure, subject to Article 8.3 including the exceptions in that Article, and shall be handled afresh.

### Article 14. The three-tier evidentiary standard

14.1. Tier A, sufficient to convict: Server data that the Server can verify itself, comprising messages still existing on the Server, Discord audit logs, logs exported by the Server's own bot containing message ID, user ID and timestamp, and capable of being re-checked by the person hearing an appeal.

14.2. Tier B, sufficient to open an investigation and apply an interim measure: a screenshot or recording submitted by a party together with at least one independent verifying element (a message ID that can be traced back, a witness outside the same relationship group, cross-matching metadata). Several genuinely independent Tier B sources, that is, different submitters, different times and cross-matching details, may in aggregate reach the standard for conviction for sanctions up to Tier 5.

14.3. Tier C, sufficient only for recording: an isolated statement, an unverifiable image, information of the "many people say so" kind. Tier C is never sufficient to convict or to publish; it suffices only for non-accusatory measures (separation of contact, increased monitoring, recording a pending file).

14.4. A Tier 6 sanction and any sanction carrying a serious label as to personal dignity (harassment, discrimination) may be pronounced only on Tier A evidence. The sole exception is Red Sanctions in the safety groups 9.1(a), (b) and (e), where the measure is a protective ban together with a report to Discord and the verifying body is Discord or the competent authority, the Server making no finding on the content in their stead. A Tier 5 sanction may be pronounced on Tier A evidence or on a combination of Tier B evidence meeting the standard in Article 14.2.

14.5. Evidence from private messages. The Server cannot access private messages and shall not convict on the basis of one-sided screenshots of private messages. For an allegation arising from private messages, the Server may only: (a) apply an interim protective measure where the child-safety group is engaged; (b) direct the reporting person to report to Discord, since Discord has the capability to verify; (c) investigate conduct of the accused person occurring within the Server.

14.6. Voice evidence. Voice is a weak evidentiary area. A sanction based on voice requires at least 2 witnesses outside the same relationship group or a valid recording; a recording is valid only where recording was announced in advance for that session. A sanction based on voice is capped at Tier 3, save where a Red Sanction element is present. Covert voice monitoring is prohibited.

14.7. Evidence from outside the Server (a leaked private chat group, another platform) may be used only where it independently attains Tier A or Tier B and the conduct falls within the jurisdictional scope in Article 19. Speaking ill of Staff in a closed group outside the Server is not a violation within the Server's jurisdiction.

14.8. Private evidence submission channel. All evidence containing personal data (private messages, images, identifying information) shall be submitted through a closed channel: the [Single-Window Channel](https://discord.com/channels/1342729473245577267/1343099398720065559), accessible only to the Staff handling the case, or [private@donquaan.com](mailto:private@donquaan.com) where anonymity is required. Evidence of this kind shall not be posted in a common channel. A victim who in good faith discloses evidence publicly for the first time shall be handled under Article 9.5, comprising removal of the Content and re-instruction, without a case being opened; the victim's underlying case shall still be taken up in full, and submission through the wrong channel shall not forfeit the right to have the matter handled.

### Article 15. Standard case procedure

15.1. Mandatory sequence: (1) Recording; (2) Opening the record under Article 20 in the central log channel; (3) Executing the correct level within the range; (4) Notifying the sanctioned person in writing, stating the provision violated, the level of sanction, the duration and the route of complaint; (5) Publishing in the sanctions register under Article 21. Time of opening the record: a sanction of Tier 3 or above must have a record before execution; sanctions of Tiers 1 to 2 and on-the-spot measures may be executed immediately with the record completed within 1 hour; emergencies and Red Sanctions are governed by Article 18 and Article 9.2.

15.2. Time limit for handling an ordinary case from receipt of the report: 48 hours for sanctions of Tiers 1 to 3; 7 days for sanctions of Tiers 4 to 6, given the need to hear both sides and obtain 2 approvers. Where the limit passes without a conclusion, notice of extension with reasons must be given; extension may be granted once only and the extension shall not exceed the original period.

15.3. Before a sanction of Tier 3 or above is issued, the person under consideration has the right to make written representations within 24 hours for a Tier 3 sanction and within 48 hours for a sanction of Tiers 4 to 6 or a non-urgent Red Sanction. For an urgent Red Sanction and in an emergency, the measure shall be executed first and the right to make representations shall be exercised at the complaint stage.

15.4. All proceedings concerning a sanction shall by default be conducted in writing in a channel that preserves a record. Discussion of a sanction by voice is prohibited, save in cases of force majeure under APL Section 34.1.

### Article 16. Conflict of interest and the duty to recuse

16.1. Staff must recuse themselves (_recuse_) from opening, approving, hearing an appeal in or investigating a case where they have with any party one of the following relationships: close personal friendship; family; a romantic relationship, current or past; personal conflict; a monetary or transactional relationship; receipt of a gift exceeding the symbolic threshold of 200,000 VND, including Nitro, gift codes and convertible items. Where a person cannot determine whether they fall within the duty to recuse, they must declare the matter to their superior for the superior to decide; Staff who have declared honestly and been permitted to continue shall not incur the sanction in Article 16.2.

16.2. Failure to recuse and failure to declare, once discovered, shall render the sanction void and the Staff member shall be the subject of a disciplinary record, even where the sanction was against the right person for the right conduct.

16.3. Two Staff having a relationship described in Article 16.1 with one another may not jointly approve the same sanction, may not hold the same area of authority and shall not handle cases involving one another.

16.4. Staff shall maintain an interests declaration register covering material relationships within the Server, transactions with Members and gifts; declaration is a condition of holding the role. A Member has the right to request a change of handler where a specific ground of conflict of interest is shown; that request shall be decided by the superior of the handling mod within 24 hours.

### Article 17. Limitation period for past violations

17.1. The limitation period for opening a case runs from the date the conduct occurred, or from the date continuing conduct ceased: (a) Ordinary-scale violations of Tiers 1 to 3: 60 days; (b) Ordinary-scale violations of Tiers 4 to 6: 6 months; (c) Red Sanctions in groups 9.1(c), (d), (g), (h), (i) and (k): 24 months; (d) Red Sanctions in groups 9.1(a), (b), (e) and (f): no limitation period applies, since such conduct is simultaneously a matter of law and of safety.

17.2. The limitation period shall be suspended while the party concerned actively conceals the conduct, or leaves the Server after the case has been recorded or while it is under investigation. Leaving the Server in ordinary circumstances shall not be treated as evasion.

17.3. Once the limitation period has expired, no new case shall be opened for that conduct; the conduct shall still be recorded with contextual value and may not be used as a basis for raising the tier.

### Article 18. Emergency status

18.1. Emergency status shall be activated on pre-set objective criteria (a raid, Red Sanction Content spreading, a privileged account compromised) in accordance with the thematic security document on defence levels. Where the thematic security document is not yet in force, the basis for activation shall be STF Sections 38 to 39. Raid threshold: 20 or more coordinated accounts, or 10 or more joins per minute.

18.2. In emergency status, the mod on duty may: execute interim measures and mass measures without prior approval by 2 persons; lock a channel or the Server; temporarily strip permissions from a Staff account showing signs of compromise, including an account of a higher level than their own. The Owner may intervene immediately in an emergency or serious situation under APL Section 30.1(b). Emergency action taken in good faith and in accordance with procedure shall not be subject to discipline, even where it is subsequently determined to have been unnecessary or mistaken.

18.3. Post-review is mandatory within 24 hours, carried out by a person who did not order the action: review of 100 per cent of the list of those affected; completion of all case records; immediate restoration of any person wrongly affected together with an apology in the form set out in Annex C, the content of which confirms that the emergency measure wrongly affected that person, admits the specific error and does not disclaim the system as a whole.

18.4. Emergency challenge channel for persons dealt with in an incident: [support@donquaan.com](mailto:support@donquaan.com), with the subject line "URGENT BAN CHALLENGE", since a banned person cannot access the Server. Time limit for handling: 24 hours. This channel shall be published permanently.

### Article 19. Jurisdictional scope

19.1. By default, the Server shall handle only conduct (a) occurring within the Server; (b) occurring at an official event held in the name of the Server, authorised in writing by the Operations Board. An event organised by Members without written authorisation is not an official event. The Server shall publish this delimitation rule permanently.

19.2. By way of exception, under a closed list: conduct outside the Server shall be handled where it targets a Member or Staff directly by reason of their membership (doxxing, harassment via private messages, dissemination of distorted internal content, organising an attack on the Server), or where it involves impersonation or misuse of the Server's name, including provoking conflict with or attacking another community in the name of the Server, even with the motive of protecting the Server.

19.3. Private-life matters of a Member outside the Server, including a person of influence, shall not be handled according to public opinion. The Server shall act only where there is a legal determination directly connected with community safety, or where the conduct is repeated within the Server. Standard formulation: "Conduct outside the Server does not fall within our jurisdiction."

---

## CHAPTER IV - CASE RECORDS

### Article 20. Internal case record

20.1. Every sanction of Tier 1 or above shall have an entry in the central log channel, within the Staff log channel category (the Staff Log category); the category is the identifier, and individual channels are not listed. The entry shall be created by the bot or in the form set out in Annex A, and must contain: (a) The user ID of the sanctioned person; identification by display name alone is prohibited; (b) The provision invoked, with the specific article number; (c) The evidence: message link, message ID, or image with cross-reference ID, together with the evidence tier A, B or C; (d) The level of sanction, its duration, and the aggravating and mitigating circumstances invoked; (e) The user ID of the mod opening the case and of the second approver, where Article 13 applies; (f) The timestamp.

20.2. The time of opening the record is governed by Article 15.1: sanctions of Tier 3 or above shall be recorded before execution; sanctions of Tiers 1 to 2 and emergencies shall be recorded within 1 hour. A sanction without a record within the time limit shall be void upon complaint, save for the exception in Article 1.3, and the mod shall receive a disciplinary reminder; repetition shall be handled under STF.

20.3. A case record may not be deleted or altered. Correction shall be effected by a supplementary entry stating the reason. Every modification must be traceable.

20.4. Retention periods, in compliance with the purpose-limitation principle of Luật 91/2025 (Law on Personal Data Protection) and Nghị định 356/2025 (the implementing Decree); the full data policy is set out in PRV: (a) Ordinary case records (mod logs) shall be retained for 24 months; bot logs for 90 days; (b) All channels, including the confiding channel, shall be logged, without exception, and shall be published as such under PRV. Logs of the confiding channel shall be classified at access level 2, comprising Head Admin and above and the Owner; the description of the confiding channel must warn Members not to share sensitive identifying information; (c) Records of cases with a legal element shall be retained until the related legal obligation ends; (d) Special logs, under a narrow list comprising personnel logs, permission logs, special violations and special context, shall be retained indefinitely and kept internal; they shall be published only in anonymised or summary form, save where there is a legal obligation to provide them to the competent authorities; (e) Access rights are allocated according to the three-level permission scheme in PRV Section 13.2 and by case: ordinary logs (mod logs, bot logs, Member sanction records) are accessible to all serving Staff; special logs are accessible only to Head Admin and above and the Owner; records involving children are accessible to a narrow group of 2 to 3 persons identified in advance for each case; (f) The data protection contact point is the Owner during the period before a legal entity exists, transferring to the legal entity upon its establishment; the deputy position is Head Admin, appointed by the Owner and announced in the [official announcement channel](https://discord.com/channels/1342729473245577267/1529782982016110642), taking effect from the time of announcement. Where no person holds the position, the authority rests with the Owner; (g) A data deletion request by a party shall be answered in writing in the form issued by the Owner: the part serving a complaint or a legal obligation shall be retained on a lawful basis; the part outside that scope shall be met so far as technically possible.

### Article 21. Anonymised public sanctions register

21.1. The Server shall maintain an anonymised sanctions register operating on a request-based lookup mechanism, in place of proactive periodic publication. A Member may create a request in the [Single-Window Channel](https://discord.com/channels/1342729473245577267/1343099398720065559) to ask for anonymised sanction information. The information provided shall comprise: type of conduct, provision, level of sanction, date and handling mod; the identity of the sanctioned person shall be withheld.

21.2. The exception permitting a user ID to be named applies only to a permanent ban imposed for a Red Sanction and only where all of the following are met: (a) the period for complaint has expired or the appeal has upheld the sanction; (b) the sole purpose is community defence, comprising warnings about fraud and dangerous replacement accounts; (c) the case does not involve children, self-harm or ongoing proceedings; (d) no sensational detail is given. Where a sanction in which an ID was named is subsequently overturned, it must be removed and corrected with the same degree of visibility under APL Section 28.

21.3. A Member has the right to compare sanction levels across cases of the same type of conduct, on the principle that the same fault attracts the same range, through the lookup mechanism in Article 21.1.

### Article 22. Periodic cross-audit

22.1. Each quarter, a Staff member from a different shift, designated on a rotating basis, shall review: 10 per cent of sanctions selected at random; 100 per cent of the sanctions of any mod who has been the subject of 2 or more complaints in the period; statistics on the distribution of sanction levels by mod; 100 per cent of invocations of the exception in Article 1.3.

22.2. Where systematic deviation by a mod is found, for example consistently applying the maximum of the range to certain persons or consistently applying a low level to acquaintances, a Staff disciplinary record must be opened. Selective enforcement (_selective enforcement_) is a disciplinary violation by the mod.

22.3. The results of the cross-audit shall be consolidated, without naming individual cases, and published internally. A statistical summary shall be published to the community each quarter, immediately after the cross-audit period referred to in Article 22.1.

### Article 23. Compliance records

23.1. Every Red Sanction case shall have a report recording a timestamp for each step: detection, removal, report to Discord, ban, escalation, logging. This body of records is the basis for rebuttal where the Server is accused of tolerating violating Content, including where an attacker posts violating Content themselves and then reports the Server, where an appeal is made to Discord Trust and Safety, and where the competent authorities so require. This body of records must be capable of being packaged within 1 hour.

23.2. The use of case records as media material is prohibited, including for the purpose of demonstrating handling capability, and in particular in respect of cases involving children and self-harm.

---

The complaint and appeal procedures are published in a separate document: [Complaint and Appeal Policy](https://donquaan.com/discord/rules/appeals).

```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" } ] }
```