---
title: "Appeals Policy - Discord Server | DonQuaan"
description: "The right to appeal a sanction, the procedure, the time limits and the guarantee against retaliation."
image: "https://donquaan.com/og-hero.png"
url: "https://donquaan.com/en/discord/rules/appeals"
lang: "en"
---

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

APL Appeals Policy

# Appeals Policy

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

# Appeals Policy

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

The Appeals Policy (cite code APL) is a component instrument of the DonQuaan Community Legal Framework, published on the [Legal Framework publication page](https://donquaan.com/discord). This instrument governs the procedure for appealing sanctions, the protection mechanism for appellants and reporters, the highest adjudicative authority, speech discipline concerning sanctions, and the entry into force and amendment procedure. This instrument shall be binding upon Members, Staff and the Owner of Server 1342729473245577267 from the effective date published in the document control block, and forms part of the contractual relationship between the Member and the Server.

### Article 0. Scope and rules of construction

0.1. This instrument comprises Chapter V, Chapter VI and Chapter VII of the sanctions regime. The sanction scale, the evidentiary standard, the case-filing procedure and the case file are governed by the [Enforcement Policy](https://donquaan.com/discord/rules/enforcement) (cite code ENF), Chapter I through Chapter IV, Article 1 through Article 23.

0.2. Cross-references in this instrument shall be construed as follows: a reference in the form "Article 26.2" denotes a provision of this instrument; a reference in the form "ENF §14" denotes a provision of the instrument bearing the corresponding cite code within the Community Legal Framework.

0.3. The terms Member, Server, Owner, Staff, Content, Official Channel and Single-Window Channel shall have the meanings uniformly assigned to them in the [Terms of Service](https://donquaan.com/discord/tos).

---

## CHAPTER V - APPEALS

### Article 24. Single window

24.1. All appeals against sanctions shall be received solely at the [Single-Window Channel](https://discord.com/channels/1342729473245577267/1343099398720065559) in the form of a ticket on Server 1342729473245577267; the ticket form shall take precedence. A person who has been banned or kicked and cannot access the Server shall appeal by e-mail to [support@donquaan.com](mailto:support@donquaan.com); where anonymity is required, [private@donquaan.com](mailto:private@donquaan.com) shall be used; for general contact, [contact@donquaan.com](mailto:contact@donquaan.com) shall be used; the official web address is [donquaan.com](https://donquaan.com/). E-mail is ordinarily answered within 24 hours; substantive review may take 1-3 days or 3-7 days depending on the case, and does not replace the first-instance appeal deadline under Article 26.2. The Single-Window Channel is publicly published on a permanent basis. The complete list of Official Channels and the verification mechanism for e-mail dispatched from [notify@donquaan.com](mailto:notify@donquaan.com) - an address on a proprietary domain, send-only and not receiving, configured with SPF, DKIM and DMARC, with the authentication standard published in the [identity authentication annex](https://donquaan.com/discord/verify); these configurations shall be completed before the effective date of this instrument - are determined by the [Terms of Service](https://donquaan.com/discord/tos). Any free e-mail address or other variant, and any contact through Zalo, Messenger or another platform, constitutes impersonation.

24.2. Any communication concerning a sanction outside the channels specified in Article 24.1 shall have no legal effect; no promise made by any Staff member through direct messages, voice channels or other channels shall bind the system.

24.3. Staff may not respond to the substance of a sanction through direct messages. The only permitted reply is the template in Appendix B, whose content redirects the matter to the appeal channel. A reply exceeding the template constitutes a Staff disciplinary violation.

24.4. A Member's contacting of multiple channels, including messaging several Staff members directly or presenting the matter on another server, shall not constitute an aggravating circumstance and shall not be sanctioned; unofficial channels shall be handled under Article 24.3. Only accompanying conduct, comprising fabrication, forgery or the organisation of a coordinated attack, shall be dealt with under the corresponding provisions.

24.5. Direct messages on Discord are not an official support channel. A direct message between Staff and a Member concerning a matter 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 Staff disciplinary violation. No person belonging to the Server, including the Owner, may send a private message requesting a Member to transfer money; any request for money or QR code outside the officially published point constitutes fraud and shall be dealt with under ENF §9.1(g).

### Article 25. Right of appeal

25.1. A person sanctioned at Tier 1 or above, and a person under a provisional sanction exceeding 24 hours, shall have the right to appeal within 30 days from receipt of the sanction notice, including a sanction executed directly by the Owner under Article 30.1(d); a person who has been banned or kicked shall appeal by e-mail under Article 24.1. Where no sanction notice has been received under ENF §15.1, the 30-day period shall run from the day the person concerned became aware of the sanction.

25.2. An appeal or report, including one submitted by e-mail, shall as a minimum contain: (a) the username and User ID of the submitter, and of the person complained of if known; (b) the sanction appealed against, or a clearly stated report; (c) the grounds, comprising factual error, procedural error, incorrect tier, conflict of interest or new evidence; (d) a clearly stated purpose of the submission; (e) supporting evidence if any, avoiding blurred screenshots or screenshots cropped out of context, in accordance with the evidentiary standard in ENF §14.

25.3. An appeal shall not suspend execution of the sanction, save where the appellate reviewer orders a stay upon determining that there are clear indications of nullity, comprising a missing case file or a missing recusal step.

25.4. A person who reports a violation shall have the right to appeal a decision not to act, or a sanction level which that person considers below the applicable tier, through the same channel and within the same time limits laid down in Article 24 and Article 25.1.

### Article 26. First-instance appeal

26.1. The appellate reviewer shall be assigned by a head mod or head admin and shall simultaneously satisfy the following conditions: not being the person who issued the sanction, not being the person who approved it, not being on the same duty shift as the matter, and having no relationship falling within the grounds for recusal with respect to any party. The assigning person may not be the issuer of the sanction, the approver, or a party to the matter; where any of those situations applies, the power of assignment shall pass to the immediate superior level or to the Owner.

26.2. Processing time limits: 72 hours for Tier 1 through Tier 3 sanctions; 7 days for Tier 4 through Tier 6 sanctions and Red Cases, running from confirmation of receipt of a valid submission. Where no conclusion is reached within the time limit, the appeal shall be deemed procedurally well-founded and the sanction shall be converted into a provisional sanction under ENF §8.3(c), pending disposal by the Final Review Panel.

26.3. The appellate reviewer shall review the entire case file, may require both parties to make written supplementary submissions, and shall issue one of the following conclusions: (a) upholding the sanction; (b) reducing or annulling the sanction; (c) increasing the sanction where it is found that the matter was improperly disposed of below the applicable tier, provided that an increase on the sole ground that the person concerned has appealed is prohibited; (d) nullity for procedural error under ENF §1.2, together with directions to re-file the case in due form if the limitation period has not expired.

26.4. The appellate conclusion shall be entered in the case file and notified to the parties in writing.

26.5. Protection against deliberate overloading and inadmissible submissions: a duplicate submission, a submission lacking a mandatory element under Article 25.2, or a submission by a person who is neither a party nor the reporter, shall be the subject of one written templated request for supplementation; where, after that request, the submission is still not supplemented or no purpose is stated, it shall be refused by written template and shall not count towards the time limits in Article 26.2. Sanctions for inadmissible submissions or deliberate harassment: continuing to file inadmissible or purposeless submissions after a request for supplementation shall attract a warning or a timeout of 1 hour to 24 hours according to gravity; mass e-mailing or sabotaging the receiving channel shall attract a timeout exceeding 1 day according to gravity. Such sanctions shall apply only to inadmissible submissions or deliberate harassment; a person who presents a matter incompletely but in good faith shall be given further guidance and shall not be sanctioned, in accordance with the principle of protection of good-faith reporters in Article 29.3. Where the number of submissions rises abnormally owing to an incident, comprising a raid or a coordinated campaign, the head admin may announce once the doubling of the time limits in Article 26.2 for matters arising from that incident, together with published reasons; the time limits may not be doubled without such announcement.

### Article 27. Final review - highest instance

27.1. Where a party does not agree with the appellate conclusion, the parties may appeal a second time to the Final Review Panel consisting of 3 persons drawn by lot from the list of eligible Staff, namely those unconnected with the matter and not falling within the grounds for recusal. The processing time limit is 7 days. Where 3 eligible Staff are not available, whether by reason of the size of the Server or because the matter involves many persons, the composition shall be supplemented in the following order: an appellate reviewer from an unrelated matter, then an external adviser to whom neither party objects; the composition of the panel shall be recorded in the case file.

27.2. A decision of the Final Review Panel is the highest and final decision in an individual matter. The Owner retains the highest authority over the norms, including amending instruments for the future under Article 35, but shall not reverse a final review decision in an individual matter that has been closed; a sanction shall be adjudicated under the norms in force at the time of the conduct, in accordance with Article 35.3.

27.3. A re-appeal on the same substance without new evidence shall be refused automatically. New evidence meeting Grade A or Grade B which emerges after final review constitutes grounds for reopening the matter once.

27.4. Where a matter involves a head admin or the Owner in the capacity of issuer of the sanction or party, the substitution mechanism in Article 30 shall apply to both the first-instance appeal stage and the final review stage.

### Article 28. Wrongful sanctions - restoration and apology

28.1. Where a sanction is annulled as wrongful or void, a restoration package shall be completed within 24 hours, comprising: (a) Removal of all penalties and restoration of access, roles and pending event entitlements; (b) Removal of the sanction from the escalation chain and marking of the file as "ANNULLED"; the file shall be retained for audit purposes and may not be used against the person concerned; (c) A correction issued in the same place where the sanction was announced, with the same visibility; (d) A written apology in the form set out in Appendix C.

28.2. The apology shall mandatorily contain, so as to resist being taken out of context: acknowledgement of the specific error; a statement of the remedial step preventing recurrence; no wholesale repudiation of the system; no attribution of blame to the sanctioned person; no generic attribution of blame to the process.

28.3. An appeal outcome favourable to a Member, including in respect of a sanction executed by the Owner, shall be published under the same rules as any other outcome. Staff may not speak or act in a manner treating the annulment of a sanction as damage to the team's reputation.

28.4. Where a wrongful sanction originates in a Staff violation, comprising failure to recuse, forgery or coercive adjudication, a Staff disciplinary file shall be opened in parallel and independently.

### Article 29. Protection of appellants and reporters - prohibition of retaliation

29.1. Retaliation of any kind against an appellant, a reporter or a good-faith witness is prohibited. Any sanction or scrutinising conduct directed at such a person within 90 days from their appeal or report shall be subject to supplementary approval by a person outside the matter; the acting party bears the burden of proving that the action does not constitute retaliation. This protection is a supplementary layer of approval and not an immunity; a reporter who has in fact committed a violation shall still be dealt with at the correct tier through that layer of approval.

29.2. Retaliation is an independent Staff violation, carrying a heavier sanction range than the underlying violation reported.

29.3. The boundary of protection is determined as follows. Good-faith reporting means bringing into the correct channel a matter which the reporter believes to be true; such conduct shall be protected in all circumstances, including where the final conclusion is that the evidence was insufficient. Malicious distortion means forgery, selective editing, or dissemination in disregard of channels; such conduct shall be dealt with under ENF §9.1(h). In no circumstances shall a sanction be imposed on a person by reason of that person having made a report.

### Article 30. Highest authority and matters involving the Owner

30.1. Tiers of adjudicative authority:

(a) Ordinary day-to-day matters: dealt with by default by the Staff team under the sanction scale in ENF Chapter II and the procedure in ENF Chapter III; the Owner does not automatically take part in individual matters;

(b) Emergency or serious situations: the Owner may intervene immediately by protective measures, provisional sanctions, mass actions, channel lockdown or Server lockdown; the case file shall be completed within the time limits in ENF §15.1 and ENF §18; matters constituting Red Cases in the safety group under ENF §9.1(a), (b), (e) shall be dealt with under ENF §9.2 and ENF §8.3(a);

(c) Special matters, comprising those which this instrument requires to be dealt with at a senior level - Red Cases; determinations concerning alternate accounts under ENF §12.2; determinations concerning coordinated attacks under ENF §11.3; matters involving Staff; matters with a legal or litigation element; matters carrying crisis risk - constitute a closed list; additions to the list may be made only by the amendment procedure in Article 35; special matters shall be dealt with directly by the Owner or by senior Staff at head mod level or above; Staff may not deal with a special matter unilaterally and alone;

(d) Every direct intervention by the Owner shall be recorded in the sanction file under ENF §20, and the person sanctioned retains the right of appeal under Chapter V as for any other sanction, in accordance with ENF §2.3; no sanction is exempt from appeal.

30.2. An appeal against a sanction issued by a head admin: the first-instance appeal shall be chaired by the Owner together with 2 mods drawn by lot; the head admin may not have access to the case file.

30.3. An appeal or report in which the Owner is a party: the Owner shall stand outside the file; the matter shall be chaired by the head admin together with an independent responsible person, following the panel-by-lot procedure in Article 27; the Owner is prohibited from taking part in the investigation, prohibited from contacting the reporter privately, and prohibited from accessing the file. The Owner undertakes to observe this principle by this instrument itself at Article 37. Since Discord does not permit the technical revocation of the Owner's powers, this norm establishes that any technical intervention by the Owner in a matter concerning the Owner constitutes a violation and shall be publicly announced under the neutral template in Article 33, without inference.

30.4. Allegations directed at the Owner or senior Staff which bear indications of criminal conduct, considered in both directions, namely that the conduct alleged is true or that the allegation constitutes staged extortion: the parties are advised to use statutory legal procedures; the Server shall provide data upon written request from the competent authorities; there shall be no negotiation with ultimatums; no public denial before examination; no public defence of the individual accused.

30.5. Procedure for handling an anonymous report accompanied by an ultimatum, for example a message sent simultaneously to all Staff with a fixed deadline for publication: (a) every Staff member who receives it shall forward it unaltered to the focal point under Article 30.3 and shall not reply individually; (b) the focal point shall send a single templated response comprising acknowledgement of receipt, an invitation to provide evidence through a secure channel, and an undertaking to protect good-faith reporters under Article 29; (c) an investigation under Article 30.3 shall be activated irrespective of whether the reporter identifies themselves; (d) there shall be no negotiation, no payment, and no public statement other than an approved holding statement; (e) every step shall be timestamped in the compliance file, in preparation for both scenarios, namely a true allegation, with a complete handling record, and extortion, with a criminal complaint record.

30.6. Delegation where the Owner becomes unreachable: only (a) Staff at Head Admin level or above, or (b) a person holding a valid written confirmation from the Owner, may temporarily act in the Owner's stead. The scope of delegation is temporary Head Admin authority and may not exceed that scope; the delegate may not amend the norms, may not take financial decisions, and may not change senior personnel. Details of succession and operational continuity are governed by the [Owner Charter](https://donquaan.com/discord/rules/owner).

### Article 31. Temporary suspension of Staff under investigation

31.1. A Staff member against whom a serious and substantiated allegation at Grade B or above has been made shall be temporarily suspended from their powers for the duration of the investigation, with a hard time limit of 14 days, extendable once for a period not exceeding the original limit; upon expiry of the time limit, including any extension, without a conclusion, the powers shall be restored.

31.2. The internal notice shall use the following template verbatim: "Temporarily suspended pending investigation under standard procedure - a measure applied uniformly to all allegations, implying no conclusion." The template shall be applied uniformly in all cases of suspension, including where the allegation is subsequently found to have been fabricated. Suspension is not a finding of violation.

31.3. The investigator shall not be on the same duty shift and shall have no relationship falling within the grounds for recusal with respect to the person concerned or the reporter. A conclusion of no violation shall result in full restoration of powers and an internal correction with the same visibility as the suspension notice.

---

## CHAPTER VI - SPEECH DISCIPLINE CONCERNING SANCTIONS

### Article 32. Prohibition of public argument about sanctions

32.1. Staff may not argue publicly about any sanction, whether in general channels, through direct messages, or on external platforms, including for the purpose of defending the sanction, defending themselves or defending a colleague. The only valid channels for discussing a sanction are the internal Staff channel and the appeal channel.

32.2. Where two Staff members disagree about a sanction, the disagreement shall be resolved in the Staff channel within a time limit of 48 hours, decided by the adjudicator according to rank; while the disagreement remains unresolved, the existing sanction shall retain its status, in accordance with the principle that a sanction properly filed is in force and that its reversal must follow the appeal procedure. Arguing about a sanction in front of a Member shall result in discipline for both parties, irrespective of which party was correct.

32.3. Where a Server sanction is published one-sidedly on an external platform, only the authorised spokesperson may respond, in writing, under the minimum public response template comprising: confirmation that the matter exists; confirmation that it was handled under the published procedure; confirmation that the appeal route is open. Limits: at most one response per development containing a new element, comprising a new allegation or new evidence; there shall be no response to individual comments. The publication of raw logs containing personal data for accountability purposes is prohibited; original logs are reserved for the appellate reviewer, for Discord Trust & Safety, or for the competent authorities; publicly released extracts shall redact the identities of third parties.

32.4. Within the Staff channel, discussion about a Member shall use professional language only, comprising conduct, the provisions relied upon and the evidence. Baseline rule: all content shall be written on the assumption that it will become public. A breach constitutes a Staff disciplinary violation from the moment the content is written, irrespective of whether the content is in fact leaked.

### Article 33. Publication of sanctions - the same level of discretion for all persons

33.1. Sanctions at Tier 1 through Tier 4 shall not be published publicly; such sanctions shall be recorded only in the anonymised sanctions register under ENF §21.

33.2. Sanctions at Tier 5, Tier 6 and Red Cases shall be published in a neutral form comprising the conduct group, the provisions relied upon and the sanction level; no inflammatory details, no insults, and no publication of private life.

33.3. The level of discretion shall be applied identically to all persons, comprising new members, long-standing members, persons of influence, Staff and the Owner. In respect of persons of influence, the team shall prepare a communications response plan before execution, comprising a pre-assembled file and a spokesperson on duty, but the content published shall not differ from the content published in respect of an ordinary Member.

33.4. Matters involving children, self-harm, or an ongoing litigation element shall not be published in any form or at any level of detail.

### Article 34. Hearings and audio or video recording

34.1. All hearings concerning a sanction shall be conducted in writing under ENF §15.4. Where force majeure requires the use of a voice channel, the rules on recording shall be announced at the very start of the session, at least 2 Staff members shall attend, and written minutes shall be drawn up immediately after the session.

34.2. A Member who records and disseminates a closed hearing with harmful editing shall be dealt with under ENF §9.1(h) or ENF §11.1 according to gravity. A Member who records verbatim in order to submit the recording to the appeal channel or to a competent authority, for the purposes of that Member's own matter, shall not be sanctioned; this is the right of evidentiary self-defence. A Member who publicly disseminates a recording of a closed hearing, including a verbatim recording, containing another person's data, shall be dealt with for dissemination of data under ENF §9.1(k) or the corresponding tier; the right of evidentiary self-defence is the right to submit through the correct channel and does not include a right to disseminate publicly.

---

## CHAPTER VII - ENTRY INTO FORCE AND AMENDMENT

### Article 35. Amendment of this instrument

35.1. This instrument may be amended only in a stricter or more precise direction. Advance notice schedule for amendments: a minor amendment, namely one which does not affect Members' rights, shall be announced at least 7 days before the effective date; a major amendment, namely one which affects Members' rights, including any relaxation of the protective procedures concerning the evidentiary standard, the single window for appeals, recusal, the prohibition of retroactivity, the prohibition of retaliation and the right of appeal, shall be publicly announced together with reasons at least 30 days before the effective date.

35.2. The list of Red Cases in ENF §9.1 and the list of circumstances in ENF §10 are closed lists; amendment shall be effected by a new version of the instrument and may not be effected during the handling of a matter.

35.3. Former versions shall be archived permanently and without time limit; a sanction shall be adjudicated under the version in force at the time of the conduct.

35.4. Closure of the Server for an indefinite period shall be notified at least 30 days in advance; details are governed by the [Terms of Service](https://donquaan.com/discord/tos).

### Article 36. Transitional provisions

36.1. Sanctions existing before the effective date shall remain in force; the right of appeal under this instrument shall apply to prior sanctions as well, within 30 days from the effective date of this instrument.

36.2. During the first 30 days from the effective date, first-time Tier 1 and Tier 2 violations shall preferably be dealt with by a reminder citing the relevant provision, as part of the norm-dissemination phase.

36.3. Period without Staff: during the period in which the Server has no Staff, the Owner shall temporarily assume the operational roles; mechanisms requiring several persons - two-person approval under ENF §13, the appellate reviewer under Article 26, the Final Review Panel under Article 27, cross-audit under ENF §22, the independent investigator under Article 31, and the substitution mechanism under Article 30 - shall be activated progressively in accordance with the recruitment roadmap, and each activation shall be publicly announced in the [official announcement channel](https://discord.com/channels/1342729473245577267/1529782982016110642). All positions requiring an identified individual shall be appointed by the Owner and announced in the [official announcement channel](https://discord.com/channels/1342729473245577267/1529782982016110642); a position takes effect from the moment of announcement; where no person holds the position, the corresponding authority vests in the Owner. A sanction executed during a period in which a multi-person mechanism has not yet been activated shall record that fact expressly in the sanction file under ENF §20; the sanctioned person's right of appeal under Chapter V is preserved.

### Article 37. Owner's undertaking

I, the Server Owner, undertake by this instrument: (1) not to issue, amend or pardon any sanction outside the procedure; every sanction I execute directly shall be recorded in a file under ENF §20 and shall be subject to the appeal route under Chapter V as for any other sanction, in accordance with Article 30.1(d); (2) to stand outside any investigation file in which I am a party, in accordance with Article 30.3; (3) to be bound by all the norms of this instrument on speech and conduct as any Member is; (4) that any intervention by me contrary to the above undertakings constitutes a violation and shall be publicly announced; (5) not to use the power of amendment under Article 35 to legitimise retroactive application to any open matter concerning me.

Signed: Owner (Server Owner), as of the date of issuance published in the document control block.

---

## APPENDIX A - SANCTION FILE TEMPLATE

```
[SANCTION FILE #____]
User ID of the sanctioned person:
Provisions relied upon: ENF §___ / Server Rules item ___
Evidence (link/message ID/file) + Evidence grade (A/B/C):
Summary of conduct (professional language, no personal remarks):
Aggravating/mitigating circumstances relied upon (per ENF §10, with evidence):
Sanction level + duration: [PROVISIONAL / FINAL]
Filing mod (User ID):
Second approver (if within ENF §13):
Recusal checked: [Yes / Not applicable]
Timestamp:
```

## APPENDIX B - SOLE TEMPLATE REPLY WHEN ASKED ABOUT A SANCTION BY DIRECT MESSAGE

> "I do not discuss sanctions through direct messages - this rule applies to the whole team, not just to your case. If you wish to appeal, the only official channel is a ticket at the [Single-Window Channel](https://discord.com/channels/1342729473245577267/1343099398720065559); if you cannot access the Server, send an e-mail to [support@donquaan.com](mailto:support@donquaan.com). A valid submission will be reviewed by a person unconnected with the sanction within the published time limit."

No word constituting comment on the matter may be added or removed.

## APPENDIX C - TEMPLATE CORRECTION AND APOLOGY FOR A WRONGFUL SANCTION OR MISTAKEN SWEEP

> "On \[date\], sanction \[sanction code\] applied to \[@user\] was reviewed under the standard appeal procedure and annulled by reason of \[category of ground: evidence below standard / procedural error / error during the security incident of X\]. We have restored all your rights, removed the sanction from your file, and apologise to you for the impact. To prevent recurrence, we have \[specific remedial step\]. The correction of a sanction through the appeal procedure is part of the published process, applicable to every member and every position."

## APPENDIX D - HOLDING STATEMENT UNDER COLLECTIVE PRESSURE

> "The matter was received at \[time\]. A PROVISIONAL measure has been applied to prevent continuing impact - this is not a conclusion. The conclusion will be published within \[the time limit under ENF §15\] in accordance with the published procedure at \[link\]. Please send all evidence to a ticket at the [Single-Window Channel](https://discord.com/channels/1342729473245577267/1343099398720065559) or to [support@donquaan.com](mailto:support@donquaan.com); we do not adjudicate under collective pressure, in either direction."

## APPENDIX E - RAPID HANDLING FLOWCHART FOR THE MOD ON DUTY (printable for shifts)

Step 0 - Classification within 30 seconds:

1. Is it a Red Case in the safety group (CSAM, child grooming, NCII-deepfake, content criminal under Vietnamese law)? If yes: remove the Content and apply a protective provisional ban immediately, which may be done unilaterally under the exception in ENF §7.1; report to Discord Trust & Safety; file the record within 1 hour; escalate to the senior person on duty. For CSAM: do not download, do not forward; only report and record metadata. Publish no content whatsoever.
2. Is it a self-harm situation or a psychological crisis? If yes: this is not a sanction matter. Apply the safety SOP under ENF §9.6: do not delete a call for help; provide hotline 111 (child protection) and 115 (emergency) together with the published support resources; report to Discord through the self-harm channel; escalate. Do not give medical or psychological advice.
3. Is it a raid or a security incident? If yes: activate the security instrument referenced in ENF §18: lock channels; mass action is temporarily permitted; post-review is mandatory within 24 hours under ENF §18.3; good-faith action in accordance with the SOP shall not be disciplined, under ENF §18.2.
4. Is it an ordinary violation? If yes: consult the sanction scale published in the [Enforcement Policy](https://donquaan.com/discord/rules/enforcement). Tier 1 and Tier 2: deal with it immediately, file the record within 1 hour. Tier 3 and above: file the record first; a mute exceeding 24 hours, a kick or a ban requires a second approver. Special matters under Article 30.1(c): do not deal with them alone, escalate to head mod level or above. Where the tier cannot be determined: apply a non-accusatory measure, comprising locking the thread or slow-mode under ENF §8.4, and refer the decision to the next duty shift.
5. Is it merely a heated argument? If yes: apply ENF §8.4, comprising locking the topic or slow-mode, without accusing either party.

Three prohibitions while on duty, without exception: do not answer about a sanction by direct message, use only the template in Appendix B; do not commit to anything in the name of the team; do not publish or comment on a matter publicly.

Where the position cannot be determined, apply a PROVISIONAL sanction and escalate. An incorrect provisional sanction lapses of its own accord under ENF §8.3; an incorrect final sanction is dealt with under Article 28.

---

The specialised instruments referred to - SOP-01 on protection of life; the specialised instrument on security (DEFCON); the specialised instrument on finance and donations; the [Staff Policy](https://donquaan.com/discord/rules/staff) and the [Owner Charter](https://donquaan.com/discord/rules/owner); the specialised instrument on events; the specialised instrument on succession and operational continuity - shall be issued by the Owner and published in the [official announcement channel](https://discord.com/channels/1342729473245577267/1529782982016110642). Where a specialised instrument has not yet been issued, matters within its scope shall be handled in accordance with the general principles of this instrument and the power of decision vests in the Owner.

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