---
title: "Owner Charter - Discord Server | DonQuaan"
description: "The Owner binds themselves by the framework: the higher the power, the higher the standard."
image: "https://donquaan.com/og-hero.png"
url: "https://donquaan.com/en/discord/rules/owner"
lang: "en"
---

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

OWN Owner Charter

# Owner Charter

Version 4.0 · Issued 11/08/2026 · Effective 18/08/2026 · Legacy ref: VK-05 · Q.II

Article 43.2(d) alone takes effect on 10/09/2026, under the major-amendment procedure laid down in that provision.

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

This instrument is the Owner Charter, cite code OWN, a component instrument of the DonQuaan Community Legal Framework. This instrument governs the status, the authority and the limits of the power of the Owner over the Server, the obligations to which the Owner is self-bound, the mechanism applicable where the Owner commits a violation, the regime of succession of authority during the absence of the Owner, and the financial discipline of the Server. This instrument shall be binding upon the Owner from the effective date and may be invoked directly in the relationship between the Server and Members.

---

## PRELIMINARY PART

### Article 0. Scope of application and relationship with other instruments

0.1. This instrument shall apply to the Owner; and to Staff and Members to the extent of the provisions that refer to them directly.

0.2. No provision of this instrument shall be construed in a manner inconsistent with the Terms of Service ([Discord ToS](https://discord.com/terms)) and the Community Guidelines ([Discord Community Guidelines](https://discord.com/guidelines)) of Discord, or with the law of Vietnam, including but not limited to: Bộ luật Hình sự (the Penal Code), Bộ luật Dân sự (the Civil Code), Luật 91/2025/QH15 and NĐ 356/2025/NĐ-CP on personal data protection, NĐ 147/2024/NĐ-CP on the management of the Internet, and NĐ 93/2021/NĐ-CP on the mobilisation of charitable contributions.

0.3. Order of precedence in the event of conflict: the law of Vietnam and the Discord ToS shall prevail over this instrument; this instrument shall prevail over any practice, custom or unwritten precedent.

0.4. Any citation of a statutory provision contained in this instrument may be used in public communications only after it has been confirmed by a lawyer pursuant to Article 54.1(f).

### Article 1. Purpose and foundational principles

1.1. This instrument governs: (a) the scope of the obligations binding upon a person entrusted with operational authority; (b) the authority and the procedure applicable where a person so entrusted commits a violation; (c) the mechanism applicable where the Owner commits a violation.

1.2. Four foundational principles:

- (a) The higher the authority, the higher the standard. Staff shall be held to a higher standard than Members; the Owner shall be held to the highest standard. No person shall be exempt from this instrument; the Owner is bound in accordance with the undertakings in Article 55.
- (b) Recording is a condition of validity. Every exercise of authority (imposing a sanction, disbursing funds, granting permissions, withdrawing permissions) must be recorded before or at the time it is carried out; an act that is not recorded shall not be recognised.
- (c) Writing standard in every channel. All content in every channel, including internal channels, must be written on the assumption that it may be made public out of context.
- (d) No person shall adjudicate a matter concerning that person. A conflict of interest gives rise to a duty to recuse; where a complaint is directed at a given level, that level loses the right to preside.

1.3. Emergency handling situations have an abridged version in Appendix E (Duty-shift reflex card). Appendix E does not replace this instrument; in the event of divergence, the source provision referred to in Appendix E shall prevail.

### Article 2. Definitions

2.1. "Server": the Discord server "DonQuaan" (ID 1342729473245577267) together with all attached identity assets (name, icon, official channels, self-operated bots, operational data).

2.2. "Owner": the individual holding technical ownership of the Server on Discord and, at the same time, the person bearing ultimate responsibility in law and in reputation. Rule of designation, permanently applicable throughout the Community Legal Framework: in every instrument, notice, record, template and official communication, this person shall be referred to solely as "Owner" or "the server owner"; no real name, alias, nickname or any other personal designation may be used, anywhere, without exception.

2.3. "Staff": every individual granted any operational authority above that of an ordinary Member, comprising the grades Trial-Mod (probationary), Moderator, Head Moderator, Admin, Head Admin, and every specialised role granted operational authority (Event Manager, Community Manager, Security/Bot Manager and equivalents). A specialised role shall be assigned an equivalent grade in the roster of titles and shall be subject to this instrument in full. The structure of the apparatus comprises the Owner, one Head Admin, two to three Moderators and Trial-Mods recruited by intake; specialised roles (Event, Security) are held concurrently and shall be recorded expressly in the roster of titles. Staff positions shall be appointed by the Owner; an appointment takes effect upon its publication in the [official announcement channel](https://discord.com/channels/1342729473245577267/1529782982016110642). Where a position is vacant, the authority of that position vests in the Owner. During the period in which there is no Staff, the Owner shall discharge the operational roles; mechanisms requiring more than one person (two-person approval, council) shall be activated in accordance with the recruitment roadmap and such activation shall be published. "Senior Staff": Staff of the grade of Admin or above.

2.4. "Operations Board": the body comprising the Head Admin and the incumbent Admins.

2.5. "Integrity Council": the mechanism for handling complaints directed at Staff or the Owner, governed by STF §29 and Articles 36 and 37 of this instrument.

2.6. "Audit-trail channel": a text channel within the Server whose log is procedurally non-erasable, such that every edit or deletion is traceable through the audit log or the bot log. If the bot log ceases to function, every operation subject to the recording requirement shall be suspended until the log functions again, save for an emergency subject to post hoc review under Article 39.4.

2.7. "Red Zone matter": a matter falling within the safety and serious-legal category (CSAM, grooming of minors, content falling within the scope of Articles 117 and 331 of the Bộ luật Hình sự (the Penal Code), threats to life accompanied by location data, NCII and sensitive deepfakes, self-harm), handled under the dedicated SOP in ENF and not under the ordinary procedure of this instrument.

2.8. "Day": a calendar day, unless stated to be a "working day".

2.9. "Continuing violation": conduct in a continuing state (unlawful retention of data, maintenance of a backdoor, ongoing dissemination) shall be deemed to be occurring for so long as that state subsists, for the purposes of Article 3.1.

2.10. The Community Legal Framework and the canon rule: the Framework comprises TOS (Terms of Service), CoC (Community Rules), ENF (Enforcement), APL (Appeals), DIS (Disclaimer), PRV (Privacy and Data Map), STF (Staff Policy) and OWN (this instrument), together with the annexes ANX-1 (prohibited terms), ANX-2 (identity authentication) and ANX-3 (donations). Where subject matter overlaps, the canon rule applies: ENF is canon on discipline, the sanction scale and the evidentiary standard; APL is canon on appeals; PRV is canon on data, logs and retention periods; TOS is canon on the list of official contact channels. This instrument merely refers to those areas; where the detail diverges, the canon instrument shall prevail.

2.11. "Single-Window Channel": the ticket channel of the Server - see [Single-Window Channel](https://discord.com/channels/1342729473245577267/1343099398720065559) - which is the official intake point for support and appeals; the fallback channel outside Discord is [support@donquaan.com](mailto:support@donquaan.com). Direct messages (DM) on Discord are not an official support channel, in accordance with STF §7.4.

### Article 3. Entry into force, amendment, prohibition of retroactivity

3.1. This instrument was promulgated on 11 August 2026, takes effect on 18 August 2026, ensuring a minimum of 7 days' prior notice, is published on the [Legal Framework publication page](https://donquaan.com/discord) and in the [official announcement channel](https://discord.com/channels/1342729473245577267/1529782982016110642), and applies to conduct occurring from the effective date onwards, without retroactive effect. The prohibition of retroactivity applies to the new internal standards established by this instrument; the prohibition of retroactivity does not exempt: (a) conduct that already breached the Discord ToS, the law, or rules in force at the time it was carried out, which shall be dealt with under the standard applicable at that time; (b) a continuing violation under Article 2.9, the continuing part of which occurring after the effective date shall be dealt with under this instrument.

3.2. Amendment of this instrument shall follow this sequence: a written proposal, consideration by the Operations Board, ratification by the Owner, and publication together with the effective date and a comparison of the changes. Mandatory notice periods: a minor amendment, a minimum of 7 days; a major amendment, that is, an amendment affecting the rights of Members, a minimum of 30 days. All previous versions shall be archived without any time limit.

3.3. An amendment concerning the rights or obligations of the Owner may only make the position stricter or clearer as regards the Owner. Any amendment relaxing an obligation of the Owner must: (a) be supported by an objective reason (legal, technical, or demonstrated impossibility) recorded in writing; (b) be published at least 30 days before the effective date, applying the "major amendment" standard of Article 3.2, because the obligations imposed on the Owner form part of the guarantee of the rights of Members; (c) not apply to any matter open at the time of publication.

---

## CHAPTER IX - STATUS AND AUTHORITY OF THE OWNER

### Article 31. Ownership and ultimate responsibility

31.1. The Server, its name, its identity assets, its operational data and every official backup server are owned by the Owner, and by the successor legal entity where one exists under Article 45.

31.2. The Owner acknowledges by this instrument: pursuant to NĐ 147/2024/NĐ-CP (Decree on the management of the Internet) and as a matter of public perception, the Owner is the point of ultimate responsibility for what exists on the Server. The Owner self-binds the manner in which the Owner exercises authority in accordance with Chapter X.

31.3. Permanent closure of the Server: the decision to close the Server permanently vests solely in the Owner, but must be publicly announced at least 30 days before the date of closure, together with guidance for Members concerning their data and concerning outstanding obligations (funds, prizes, open appeals).

### Article 32. Authority of the Owner

32.1. The Owner is the highest authority of the Server along three axes:

- (a) Law: promulgation, amendment and ratification of every legal instrument of the Server, in accordance with the procedure and the notice periods in Article 3.2;
- (b) Personnel: final decision on the appointment and removal of Staff at every grade, including the Head Admin; new recruitment shall pass through the single-window procedure in STF §18; where the Owner nominates a candidate, the Owner shall have no vote on the review panel; every personnel decision of the Owner shall be recorded together with its grounds;
- (c) Finance: only the Owner may approve every cash flow and every disbursement of the Server, as detailed in Chapter XIII.

32.2. Compliance veto: the Owner may veto an operational decision in writing where that decision breaches the law of Vietnam or the Discord ToS and Community Guidelines. A veto must state specific grounds and shall be logged internally.

32.3. Beyond the authority set out in Articles 32.1 and 32.2, the power of the Owner to intervene in cases shall be exercised in accordance with the tiering in Article 33. The Owner undertakes to exercise every other technical permission conferred by Discord on the owner account within the framework of this instrument. Use outside that framework constitutes a violation of this Charter and shall be dealt with under Article 36.

---

## CHAPTER X - TIERING OF CASE AUTHORITY AND OBLIGATIONS BINDING THE OWNER

### Article 33. Tiering of case authority

33.1. Day-to-day cases: by default these shall be handled by the moderation team in accordance with the scale and procedure of ENF. In day-to-day operations the Owner shall not impose a sanction, shall not amend a sanction, and shall not grant individual clemency.

33.2. Urgent intervention by the Owner: the Owner may intervene directly and immediately (imposing, amending or lifting a sanction) where the situation falls within the EMERGENCY category under Chapter XI or within the SERIOUS category, that is, a matter involving a Red Zone element, human safety, indicia of criminal liability, or spreading harm to which the ordinary handling chain cannot respond in time. Every intervention under this clause is subject to Article 34 concerning record-keeping and the right of appeal.

33.3. SPECIAL cases, that is, matters of particular gravity under the classification in ENF (RED cases, sensitive multi-party matters, matters involving Staff, matters carrying legal or media risk): shall be handled by the Owner or by Senior Staff under Article 2.3. Staff may not handle a SPECIAL case unilaterally and alone in any circumstances; a minimum of two persons must participate in the decision, or the matter must be escalated to the Owner. A breach of this clause is a disciplinary violation with its own scale in Appendix D.

33.4. The Owner has the same right as any Member to report a violation through the proper report channel. A report by the Owner shall be handled under the ordinary procedure, without priority and without being labelled as a direction from above.

33.5. In respect of open day-to-day cases in which the Owner does not intervene under Article 33.2 or 33.3, the Owner shall read the statistics and the audit results; the Owner shall not receive interim reports on a particular hearing or appeal, save where the Owner is a party, in which case the Owner shall have the rights of a party and no more.

### Article 34. Records and appeals concerning direct intervention by the Owner

34.1. The recording principle in Article 1.2(b) applies to the Owner as well: every direct intervention by the Owner in a case under Article 33.2, Article 33.3 or during an emergency under Chapter XI shall be fully recorded in the same manner as a sanction by any Staff member - grounds, time, sanction, persons affected - in the audit-trail channel, before or at the time it is carried out; in an emergency, post hoc review shall apply under Article 39.4.

34.2. Undiminished right of appeal: a Member affected by a direct intervention of the Owner shall enjoy the full right of appeal through the single appeal window under APL, as with any other sanction. The reviewer shall not be the Owner and shall not be selected by the Owner for that matter. An appeal outcome reversing a sanction of the Owner shall be published in the same manner as any other appeal outcome.

34.3. Direct intervention by the Owner outside the scope of Articles 33.2 and 33.3 (a day-to-day case that is not urgent, not serious and not special) shall nonetheless be recorded under Article 34.1 and shall be subject to appeal under Article 34.2, and shall in addition be considered by the Council as a violation of this Charter under Article 36. Notice of the annulment of a sanction shall use the template: _"The sanction of \[X\] has been reviewed under the standard procedure applicable to all sanctions and has been annulled. We apologise to \[the person affected\]."_ The notice shall not attribute personal blame.

### Article 35. Standards of speech and conduct applicable to the Owner

35.1. The Owner is subject to all content and conduct rules applicable to Members, without exemption from any of them.

35.2. Additional standards applicable to the Owner alone:

- (a) No use of double-meaning slang that is easy to clip out of context ("lùa", "gà", "con mồi", "chăn" and equivalents) in any channel, including private channels and voice channels;
- (b) No immediate speech during a crisis: every public statement of the Owner while a matter is unfolding must be drafted by the Spokesperson and must be held for a minimum of 2 hours before release;
- (c) No comment on a matter under investigation, carrying a legal element, or involving minors, other than an approved holding statement;
- (d) In internal channels, the Owner shall comply with STF §7.2 as any Staff member does.

### Article 36. Handling of violations by the Owner

36.1. A violation by the Owner of the rules on speech or conduct shall be received through the ordinary report channel or the escalation channel; handling shall be carried out by a Council comprising the Head Admin and two Staff drawn by lot, excluding any person having a declared relationship with the Owner beyond a working relationship; the substitution mechanism shall follow STF §29.2.

36.2. Sanctions applicable to the Owner: a recorded reminder, a formal warning, a requirement to issue a correction or a public apology, and publication of the conclusion. The Owner undertakes in advance, in Article 55, to comply with the conclusion of the Council and not to use technical permissions to reverse that conclusion.

36.3. Any use by the Owner of technical permissions to intervene in a matter concerning the Owner (deleting records, stripping the permissions of the person handling the matter, altering the configuration of the investigation channel) is a violation of this Charter at the gravest level, and the Council is under a duty to publish that conduct to the entire community.

### Article 37. Serious complaints directed at the Owner

37.1. This Article applies to every serious allegation (harassment, abuse, misappropriation, breach of law) directed at the Owner, including anonymous complaints and complaints accompanied by an ultimatum as to publication within 48 hours. Foundational principle: the Owner stands outside the file, without exception; the Head Admin together with an independent case handler shall deal with the matter.

37.2. Procedure:

- (a) Intake: by the Head Admin and an independent case handler. In a matter involving a gender element, the intake group must include a female Staff member aged 18 or over; this position shall be appointed by the Owner upon recruitment and takes effect upon publication in the [official announcement channel](https://discord.com/channels/1342729473245577267/1529782982016110642); where no qualifying female Staff member exists, a matter involving a gender element shall use a neutral external person under point (c). Intake personnel shall be designated in advance and listed internally;
- (b) The Owner is prohibited from: participating in the investigation, accessing the file, contacting the complainant in any form, and undertaking any form of attempt to identify an anonymous complainant;
- (c) Neutral third party: a matter shall be regarded as objectively serious where the allegation - if true - would give rise to criminal liability, or concerns abuse or harassment, or where the complainant so requests. In that event the Council must invite a reputable person from outside the team, accepted by both sides, to witness the procedure. A list of two to three neutral external persons, meeting the criteria of being aged 18 or over, of good standing in the community, having no financial interest in and no close relationship with the Owner, and having given prior consent, shall be compiled by the Owner upon recruitment and published in the [official announcement channel](https://discord.com/channels/1342729473245577267/1529782982016110642), taking effect upon publication;
- (d) Parallel handling of two hypotheses: the matter shall be handled simultaneously on the hypothesis that the allegation is true (seriousness, protection of the complainant, confidentiality) and on the hypothesis that the allegation is fabricated (recording of the extortionate conduct, no negotiation over deadlines, preparation of a holding statement for the scenario in which the article is published);
- (e) The only permitted statement during the investigation: _"We have received the matter and are verifying it under the standard procedure. No comment on individuals."_ Both public defence and public condemnation are prohibited;
- (f) Indicia of criminal conduct in both directions - the conduct complained of being true, or the complaint itself constituting extortion against reputation: the legal route shall be recommended; the Server shall provide records upon lawful request; the Server shall not substitute itself for a court.

37.3. A person who complains against the Owner in good faith shall enjoy the full anti-retaliation protection mechanism under STF §29.6, including the limits of that protection mechanism as provided in that provision, with the monitoring period extended to 180 days.

---

## CHAPTER XI - STATE OF EMERGENCY

### Article 38. Narrow definition and closed list

38.1. A state of emergency exists only upon the occurrence of one of the following events; this list is closed and may not be extended by analogy:

- (a) An attack in progress: a raid on the scale of 20 or more coordinated accounts or 10 or more joins per minute, an abnormal mass-ban or channel deletion, or a compromised privileged account causing destruction;
- (b) Red Zone content spreading to which the ordinary handling chain cannot respond in time;
- (c) A serious infrastructure incident: the main bot compromised, a webhook exploited, a secret leaked;
- (d) Loss of command capacity: the entire Operations Board being uncontactable during an incident in progress. In that case, the most senior duty Staff member still contactable may declare and act under Article 39, subject to full post hoc review.

38.2. The following do not constitute a state of emergency: an unfolding controversy, a crowd demanding a ban, a spreading attack post, a long-standing Member threatening to leave the Server, internal disagreement, or a backlog of appeals. These situations shall follow the ordinary procedure together with the communications playbook. For the Owner, these situations must in addition be assessed against the "serious" threshold in Article 33.2; controversy alone does not constitute "serious".

### Article 39. Activation, powers, duration

39.1. Persons entitled to activate: any duty Staff member of the grade of Moderator or above, in respect of defensive measures (lockdown, slowmode, stripping the permissions of an account causing destruction under STF §20.5); the Owner or the Head Admin, in respect of a Server-wide state of emergency. Activation in good faith but in error shall not be subject to discipline; activation on fabricated grounds constitutes fabrication under STF §20.5.

39.2. During a state of emergency the Owner may act directly, this being an instance of the power of urgent intervention in Article 33.2: stripping permissions, banning, locking channels, disconnecting bots, to the extent necessary to stop the harm in progress.

39.3. Duration: a state of emergency lapses automatically after 72 hours, unless re-declared by a person entitled to activate under Article 39.1, and each re-declaration must state fresh grounds. There is no such thing as a standing state of emergency.

39.4. Mandatory reporting back:

- (a) Within 24 hours after the state of emergency ends: a full internal report comprising the event, the actions taken, and the list of persons and assets affected;
- (b) 100% post hoc review: every sanction imposed during a state of emergency is by default a PROVISIONAL sanction, to be reviewed within 24 to 72 hours by a person who did not participate in ordering it; a sanction applied in error shall be lifted together with an apology in the standard form: _"During the handling of the security incident of \[X\], an emergency measure affected you in error; we have restored the position and we apologise."_;
- (c) Minimum public notice to the community: the type of incident that occurred, without technical detail capable of exploitation; the fact that it has been dealt with; and the fast-track channel for persons affected in error;
- (d) Emergency action by the Owner is likewise subject to post hoc review as for any other person, and subject to appeal under Article 34.2.

39.5. Action taken in the name of a state of emergency outside the list in Article 38.1, or after the expiry of the duration, shall not enjoy any exemption and shall be dealt with as an ordinary violation; in respect of the Owner, it shall be dealt with under Article 34.3 and Article 36.

---

## CHAPTER XII - SUCCESSION OF AUTHORITY DURING THE ABSENCE OF THE OWNER

### Article 40. Peacetime delegation (short-term absence)

40.1. The state of being "uncontactable" shall be established by verifiable criteria: the Owner having been messaged on a minimum of two fixed channels (Discord and the external channel under Article 41.1(b)), with the time of each message recorded, and no response after 72 hours. In that case, for so long as matters requiring decision arise, the Head Admin shall by operation of this instrument have the power to decide all operational matters, save for the following locked list: (a) transfer of ownership or dissolution of the Server; (b) amendment of the legal instruments; (c) any disbursement from the fund, save a disbursement covered by a subsisting item-by-item written delegation signed in advance by the Owner under Article 43.2; (d) personnel at the grade of Admin or above; (e) any statement accepting legal responsibility in the name of the Server; (f) any new financial commitment or partnership.

40.2. The delegation terminates automatically when the Owner returns and confirms in the audit-trail channel. Every decision taken during the delegation shall be fully reported back.

40.3. A second emergency successor, designated by the Owner upon recruitment and taking effect upon publication in the [official announcement channel](https://discord.com/channels/1342729473245577267/1529782982016110642), shall be designated in advance for the scenario in which the Owner and the Head Admin are both uncontactable; that person must satisfy the conditions in Article 40.4.

40.4. Limits on the person and the scope of delegation, permanently in force and not amendable in the direction of relaxation: the person taking over management where the Owner is uncontactable may only be (a) Staff of the grade of Head Admin or above, or (b) a person holding a subsisting written confirmation from the Owner. The maximum scope in every case equals the authority of the Head Admin and is temporary in nature; it may not exceed that scope, and it gives rise to no right of ownership and no financial power beyond Article 40.1.

### Article 41. Loss of the Owner account (compromise, wrongful suspension, mass-report)

41.1. Peacetime preparation, being an obligation of the Owner, to be checked once every 6 months:

- (a) The Owner account shall have 2FA enabled at the highest level, use a dedicated recovery e-mail address, and not reuse passwords;
- (b) A verification channel outside Discord shall be permanently published: every critical announcement (change of server, succession, emergency) takes effect only when cross-posted on the [donquaan.com website](https://donquaan.com/), in the [identity authentication annex](https://donquaan.com/discord/verify). No second cross-verification channel shall be used; the addition of a verification channel, upon the establishment of an official fanpage, shall follow the amendment procedure in Article 3.2. This channel shall be controlled by the Owner independently of Discord;
- (c) A Discord appeal file prepared in advance: a description of the Server, the compliance history, and evidence of proactive moderation;
- (d) A backup server held in the name of the Owner, kept empty, the existence of which shall be published together with the statement: _"The Server has one and only one official backup, being this server, held in the name of the Owner. Any other 'backup' is not ours."_ A backup server set up by any other individual shall not be recognised, and the use of such a server to solicit Members constitutes a violation for impersonation.

41.2. Where the Owner account is compromised: Staff shall apply the emergency permission-cut measure under STF §20.5 to the Owner account itself if that account is causing destruction. This instrument confirms in advance that this is required action, not usurpation.

41.3. Where the Owner account is suspended by Discord: the Head Admin shall manage under Article 40; community communication shall proceed through the fallback channel; the appeal shall be lodged using the file prepared in advance. No person may on their own initiative move the community to any server other than the published, Owner-held backup server.

41.4. During every period of absence of the Owner, the procedures for handling violations and appeals shall not change in speed and shall not change in standard. A vacuum of authority is not a ground for lowering the standard of handling or for suspending resolution.

### Article 42. Operational Will (permanent absence)

42.1. The Owner shall draw up and maintain a sealed Operational Will, entrusted to two custodians comprising one trusted person outside the apparatus and one member of the Operations Board; the Will may be activated only where both cross-confirm. Both custodians shall be designated by the Owner upon recruitment, taking effect upon publication in the [official announcement channel](https://discord.com/channels/1342729473245577267/1529782982016110642). Minimum content of the Will: (a) the long-term successor and the transfer plan, taking into account the technical limitation that Discord requires the owner account itself to carry out the transfer of ownership, such that the practical plan rests on the backup server under Article 41.1(d) and on the highest admin permissions granted in advance; (b) the treatment of the fund and outstanding financial obligations; (c) the method of verifying the authenticity of the activation of the Will, comprising cross-checking against the channel outside Discord and the cross-confirmation of the two custodians; (d) the content of the community announcement.

42.2. Conditions for activation: cogent grounds that the Owner has lost long-term capacity to manage or has died, confirmed by both custodians of the Will. Wrongful or forged activation is a violation at the gravest level and carries a legal element.

42.3. Updating of the Will: at least once every 12 months.

---

## CHAPTER XIII - FINANCIAL TRANSPARENCY AND DONATIONS

### Article 43. Principles governing the acceptance of donations

43.1. If and only if the Server opens the acceptance of donations, the following principles shall be displayed at the point of donation at all times:

- (a) A donation is a voluntary gift, unconditional and non-refundable, save for the cases of refund laid down in the Terms of Service §25.4 (of which Article 43.3 implements §25.4(a)); a donation does not purchase privileges, does not purchase any feature commitment, and creates no reciprocal obligation of the Server;
- (b) All fundraising language linking a donation to a condition or a reciprocal commitment, in the form "donate so that the Server does X" and equivalents, is prohibited;
- (c) Recommended cap per transaction: VND 500,000. A donation exceeding the cap shall display the confirmation _"I am 18 or over, or I have the consent of my guardian"_. In the specific case of a prize or a donation involving a person under 18 exceeding VND 500,000: confirmation by a parent or guardian and two approvers at the time of award are mandatory.

43.2. Fund ledger and disbursement authority, on a one-approver and one-bookkeeper design:

- (a) Only the Owner may approve every cash flow and every disbursement. No level below the Owner - including a co-owner, that is, another account granted the highest technical administrative permissions if such exists, and including the Head Admin - may disburse on their own. A co-owner may disburse only under a subsisting item-by-item written delegation from the Owner, stored in the audit-trail channel. In an emergency during the absence of the Owner, disbursement may be made only under a written delegation signed in advance by the Owner, item by item or according to a pre-approved scenario; without a delegation there shall be no disbursement;
- (b) Reconciling bookkeeper: one person shall be designated whose sole function is to record and reconcile every inflow and outflow together with supporting documents; that person shall have no disbursement power. Cash flows of the Owner through the fund shall be entered in the ledger as those of any other person; no item of the Owner is exempt from the ledger;
- (c) Periodic publication in summary form: the fund ledger shall be published quarterly, on a quarterly cycle aligned with CoC and PRV, in a public channel, in summary form comprising total receipts, total disbursements by category, and the balance; the detailed version with supporting documents shall be retained internally for reconciliation and legal obligations;
- (d) Donations shall be accepted only while a reconciling bookkeeping mechanism is in operation with an independent bookkeeper under point (b). For so long as no independent bookkeeper has been designated, donations may be accepted only where all the substitute conditions below are satisfied concurrently, and the Owner keeping the ledger shall not be treated as satisfying point (b): (i) every receipt and every disbursement shall be published publicly, item by item and with a timestamp, in a public channel, no later than 07 days after it arises; (ii) the publication under sub-point (i) shall be confirmed, before it is issued, by a person independent of the Owner. That person shall have no disbursement power, shall receive no material benefit from the Server and shall be in no relationship of dependence on the Owner; the role of that person shall be published in the official announcement channel. The Owner keeping the ledger, or confirming it, shall not be treated as satisfying this sub-point or point (b); (iii) the independent bookkeeper under point (b) shall be designated no later than 30 days after the first donation; (iv) where the time limit in sub-point (iii) expires without an independent bookkeeper having been designated, the acceptance of donations shall be suspended automatically until that designation is completed; (v) this point (d) constitutes a RELAXATION of the standard laid down in point (b). Its enactment, extension or expansion shall follow the major-amendment procedure: prominent publication, public reasons and a minimum notice period of 30 days, in accordance with TOS §31.5. In compliance with that procedure, this point (d) takes effect on 10/09/2026, being 30 days from the date of promulgation of 11/08/2026, and the general effective date of this instrument under Article 3.1 shall not apply to it. Before 10/09/2026, donations may be accepted only where an independent bookkeeper under point (b) is already in place. This point (d) shall lapse automatically on the date the Server announces that an independent bookkeeper has been designated.

43.3. Refunds for donations and prizes of minors (implementing the Terms of Service §25.4(a); this Article creates no further case of refund): a donation by a minor shall be refunded in full where the guardian so requests within 90 days of the transaction, without dispute, subject to retention of the receipt. Processing time for a refund after receipt of a valid request: 72 to 120 hours; larger amounts shall be given priority. Beyond the 90-day window, a request by a guardian shall nonetheless be considered in accordance with legal advice, since a transaction by a minor may be void under the Bộ luật Dân sự (the Civil Code); a request made out of time shall not be refused automatically.

43.4. Temporary use of fund monies in any form, by any person including the Owner, is a violation at the highest level of the financial framework and shall be dealt with regardless of whether the monies have been repaid.

### Article 44. Absolute financial prohibitions (no person may approve an exception, including the Owner)

44.1. Prohibited, without exception:

- (a) Any structure collecting money from participants combined with an outcome of chance and the payment of prizes, as this constitutes gambling or the organisation of gambling under Articles 321 and 322 of the Bộ luật Hình sự (the Penal Code);
- (b) Virtual coins or reward points convertible into money or into goods having a market value by any route; where a spontaneous secondary market in coins is detected, that coin mechanism shall be closed rather than moved to a managed regime;
- (c) Soliciting or channelling charitable contributions through a personal account, since NĐ 93/2021/NĐ-CP (Decree on the mobilisation of charitable contributions) restricts the persons entitled to solicit; the Server shall only link to a licensed organisation and shall not receive any monies;
- (d) Payment of salaries from the fund before a legal entity and a tax framework exist under Article 45.

44.2. Every proposal touching the prohibited subject matter in Article 44.1, whether from a Member, Staff, a sponsor or the Owner, shall be refused. No person within the system has authority to approve an exception to this Article.

44.3. Third-party monies and sponsorship: a sponsorship commitment may be publicised by name or promoted only after the monies or goods have been received by the fund-holding function. A sponsor or partner touching cash flows or Member data must pass a minimum recorded due diligence, comprising identification, sector and legal risk; the detail is governed by the Framework Event Regulations. The foundational principle is placed in this Article so that no subordinate instrument may relax it.

### Article 45. Matters suspended pending a legal entity

45.1. The following matters are suspended and shall not be implemented until an operating legal entity exists and legal advice has confirmed the position under Article 54.1(d): profit-sharing or payment of salaries to Staff; the charging of event fees, including skill-based events; the acceptance of large-scale sponsorship; and commercialisation in any form.

45.2. As soon as the legal entity is operational: all cash flows shall be transferred to the account of the legal entity and the personal wallet route shall be closed permanently; the whole of this Book shall be re-reviewed by a lawyer under Article 54.1(d).

45.3. Before that point, the standard answer to every argument about the sharing of money is: all roles are voluntary; revenue, if any, is spent only on operations and prizes, with a public ledger; and the financial principles were established in writing before any revenue arose.

---

## CHAPTER XIV - SEPARATION OF RESPONSIBILITY; ANTI-IMPERSONATION AND FALSE EVIDENCE

### Article 46. Separation of personal speech and Server speech

46.1. Personal speech of the Owner outside the Server (personal pages, separate content channels, interviews given in a personal capacity, other projects) does not represent the Server, is not the position of the community, and may not be used as a ground for attributing responsibility to the Server, unless the Owner expressly states that the Owner is acting in the name of the Server. However, public personal speech of the Owner that refers directly to the Server, to Members, or to a matter of the Server remains subject to the standard in Article 35 and may be considered by the Council under Article 36; the separation does not create a right to criticise one's own community from a personal channel.

46.2. Conversely: speech, decisions and content of the Server, whether generated by the operations team, by Members or by bots, are not automatically the personal speech of the Owner. Day-to-day sanctions imposed by the moderation team do not bear the name of the Owner, in accordance with Article 33.1; content posted by a Member belongs to that Member.

46.3. Standing identity declaration, publicly pinned; the list of official channels is governed by TOS, which is canon on official channels, and is published in the [identity authentication annex](https://donquaan.com/discord/verify): _"Official speech of the server appears only at: the Discord server 'DonQuaan' (ID 1342729473245577267), the [donquaan.com website](https://donquaan.com/), and e-mail addresses on the donquaan.com domain - support: [support@donquaan.com](mailto:support@donquaan.com); anonymous: [private@donquaan.com](mailto:private@donquaan.com); general contact: [contact@donquaan.com](mailto:contact@donquaan.com). The sole official outbound address is [notify@donquaan.com](mailto:notify@donquaan.com), send-only and not receiving. Any gmail address or other variant, and any contact through Zalo, Messenger or another platform - even where it matches in form, in voice or in image - is impersonation and is not ours."_ Before the effective date of 18 August 2026, the SPF, DKIM and DMARC configuration for the official outbound address must be completed and correct, and the authentication standard must be published in the [identity authentication annex](https://donquaan.com/discord/verify).

46.4. Immutable principle, pinned in perpetuity and repeated periodically: _"No one from the server - including the Owner - sends direct messages asking for money, charging fees, demanding a transfer or requiring the scanning of a QR code, for any reason, in any circumstances. Every such message is a scam, without exception."_

46.5. Article 46 applies in both directions: it guards against attributing conduct to the wrong person, as regards both the Server and the Owner, while not exempting the Owner from responsibility for the Owner's own speech under Article 35 and from statutory legal responsibility as the person managing the platform under Article 31.2.

### Article 47. Impersonation, deepfakes and false evidence directed at the Owner

47.1. Where content impersonating the Owner appears (clone accounts, fabricated screenshots, deepfake audio or video), the Server shall respond under the standard playbook: (a) a single statement from an official channel, stating that the content does not exist in the system, that the file has been preserved, that the platform has been notified, and that the Server is prepared to work with the competent authorities in respect of the dissemination of false information (NĐ 15/2020/NĐ-CP as amended by NĐ 14/2022/NĐ-CP (Decree on administrative sanctions in the field of posts, telecommunications and information technology); Article 156 of the Bộ luật Hình sự (the Penal Code) on defamation where the elements are made out); (b) reporting to the disseminating platform; (c) no reply to individual comments and no attempt to prove a negative before a crowd, forensic examination and adjudication being matters for third parties, namely Discord and the competent authorities; (d) the declared readiness to work with the competent authorities must be acted upon in fact.

47.2. A Member of the Server found to have fabricated evidence directed at the Owner or at Staff shall be dealt with under the fabrication framework, at the highest level in the system. The Server shall support the injured person through the legal route, including where the injured person is the Owner; in that case the Owner shall be protected as any other victim, no more and no less.

### Article 48. Boundaries of responsibility

48.1. The Server shall permanently publish the boundaries of responsibility, as detailed in CoC and DIS: private transactions between Members are at the parties' own risk, the Server does not guarantee them, does not act as intermediary, and does not compensate; direct messages lie outside the technical visibility of the Server; an unregistered offline event is not an event of the Server.

48.2. The boundaries in Article 48.1 carry corresponding obligations of the Server: active enforcement, comprising the prohibition and removal of the categories of prohibited transactions and periodic scam warnings; support for victims towards the proper legal route, comprising guidance on reporting to the authorities and the provision of metadata upon written request by the competent authorities; and no undertaking to recover assets on behalf of a Member.

48.3. Where a criminal matter originates from the Server (fraud, grooming, threats): the Server shall cooperate fully as regards action, comprising the provision of evidence, logs and platform reports, and shall observe wording discipline without exception, under which the Server shall not accept legal responsibility on behalf of the offender, and all speech shall pass through the Spokesperson, in writing, on the assumption that it is being recorded or will be published.

### Article 49. Spokesperson

49.1. The principal Spokesperson is the Head Admin and the one alternate is a Moderator competent in drafting. Both shall be recorded by title or username, and the real name of the Owner shall not be used, in accordance with Article 2.2; both positions shall be appointed by the Owner upon recruitment, taking effect upon publication in the [official announcement channel](https://discord.com/channels/1342729473245577267/1529782982016110642). These are the only two persons who may speak in the name of the Server externally, and they may speak only in writing. During the period in which there is no Staff, the Owner shall temporarily discharge the spokesperson role, while maintaining the discipline in Article 35.2(b) as to the minimum period of 2 hours and the written form. The Owner is by default not the spokesperson in a hot situation, in accordance with Article 35.2(b); the final statement nonetheless requires the approval of the Owner. If both spokespersons are uncontactable during an unfolding crisis, the incumbent manager - where the Owner is absent, the manager under Article 40 - may use only a pre-drafted holding statement and may not draft a new statement.

49.2. The set of documents drafted in peacetime, being an annex to the Crisis Playbook and maintained together with this instrument, comprises: three versions of the holding statement; the standard holding line for Staff; the script for dealing with parents; the letter responding to a data request under NĐ 13 (Decree on Personal Data Protection), to be used only after approval by a lawyer under Article 54.1(a); and the correction notice. Drills shall be held twice a year, activated once a Staff team exists; during the period in which there is no Staff, the Owner shall review the pre-drafted set of documents on the same cadence.

---

## CHAPTER XV - IMPLEMENTING PROVISIONS

### Article 50. No negotiation with extortion

50.1. Principle applicable at every level and in every situation (internal leaks, "white hat" demands for money, complaints accompanied by an ultimatum, CSAM planted on the Server): no payment, no promise, no deletion or amendment of any content on the demand of a threat, and no negotiation over deadlines. All correspondence shall be preserved; a report shall be made to the authorities where the elements of Article 170 of the Bộ luật Hình sự (the Penal Code) are made out. In the specific scenario of planted CSAM: proceed under the Red Zone SOP - report to Discord Trust & Safety immediately, do not download and do not retain any copy of the content in any circumstances, retain only metadata comprising the channel, the posting account, the time and the message ID, remove under the SOP, and report to the competent authorities; every step shall be timestamped.

50.2. The good-faith vulnerability reporting channel (responsible disclosure) shall be published: [support@donquaan.com](mailto:support@donquaan.com), with the subject line "Security/Disclosure"; the anonymous channel: [private@donquaan.com](mailto:private@donquaan.com). The Server undertakes to respond within 72 hours and to give public credit to good-faith reporters.

### Article 51. Categories of matters not put to a community vote

51.1. Three categories of matters, namely safety (children, self-harm, the Red Zone), legal matters and personnel matters, shall not be put to a vote, shall not be decided by majority, and shall not have their procedures shortened under pressure. The Server shall classify publicly from the outset: which matters are voted on to decide, which matters are voted on for reference, and which matters are not put to a vote.

### Article 52. Relationship with other instruments

52.1. This instrument forms part of the Community Legal Framework under Article 2.10 and refers to: CoC (Community Rules); ENF (Enforcement - canon on the sanction scale, the evidentiary standard and the Red Zone SOP); APL (Appeals - canon on single-window appeals); PRV (Privacy - canon on data, containing the Data Map); DIS (Disclaimer); TOS (canon on official contact channels); STF (Staff Policy); and the operational instruments: the Security Code (bots, webhooks, DEFCON), the Framework Event Regulations, and the Crisis Playbook. This instrument merely refers to the canon areas and does not repeat the detail; where the detail diverges, the canon instrument shall prevail. For so long as a referred instrument has not been promulgated, the gap shall be filled in the following order: (a) the foundational principles in Article 1.2; (b) a provisional evidentiary standard of "clear and convincing" for every sanction of removal from role or ban and above; (c) where the grounds remain insufficient, the most provisional, reversible and least intrusive measure shall be chosen, with simultaneous escalation to the level above, and no new procedure shall be created.

52.2. The instruments of the Community Legal Framework are published on the [Legal Framework publication page](https://donquaan.com/discord), each instrument at its own address published on that page. Every reference to an address within the Community Legal Framework must use the exact list of addresses published on that page.

### Article 53. Severability

53.1. Where a provision is invalid, by reason of illegality, inconsistency with the Discord ToS, or impossibility, that shall not render the whole instrument invalid; that provision shall be amended under the procedure in Article 3.2, and the remainder shall remain in force.

### Article 54. Items awaiting professional approval before implementation

54.1. The following items shall not take effect for implementation until they have been approved by a lawyer or by an expert with the corresponding professional competence: (a) the template response to a data request under NĐ 13 (Decree on Personal Data Protection), referred to in STF §11.2(b) and Article 49.2; (b) the content of the self-harm and psychological SOP, referred to in STF §21.2 and §23.4; (c) the decision to report to the authorities in a matter involving dissemination by a former Staff member, referred to in STF §27.2(d); (d) the whole of the block suspended pending a legal entity in Article 45; (e) the assessment of procedural obligations under NĐ 147/2024/NĐ-CP (Decree on the management of the Internet) upon reaching the scale threshold, activated automatically together with the rapid-growth regime in STF §19.4; (f) confirmation of every citation of a statutory provision in this instrument before its use in any public statement or external document; (g) assessment of the legal effect of undertakings established online, referred to in STF §5.3. Pending that approval, the parts of the procedure not dependent on these templates shall be implemented as normal.

### Article 55. Undertakings of the Owner

55.1. By promulgating this instrument, the Owner confirms in writing, publicly and with a timestamp:

- (a) Day-to-day sanctions shall be imposed by the team in accordance with the sanction scale; the Owner shall not impose a sanction, shall not amend a sanction, and shall not grant individual clemency in day-to-day operations; the Owner shall intervene directly only in an emergency or in a serious matter under Article 33.2 or in a special case under Article 33.3, and every intervention of the Owner shall be recorded and shall be subject to appeal in the same manner as a sanction by any other person, under Article 34;
- (b) The Owner is subject to the rules on speech and conduct as any Member is, together with the higher standard in Article 35;
- (c) A matter concerning the Owner shall follow the proper appeal procedure; a complaint directed at the Owner shall be investigated with the Owner standing entirely outside, in accordance with Article 37;
- (d) Every cash flow passing through the hands of the Owner in connection with the Server shall be entered in the reconciled ledger as that of any other person, in accordance with Article 43.2;
- (e) The Owner understands that a breach of the above undertakings will be published by the Council, and accepts that mechanism in advance;
- (f) The above undertakings are established by the Owner before any matter concerning the Owner arises.

55.2. Form of signature: public confirmation by a post in the [official rules channel](https://discord.com/channels/1342729473245577267/1342766172000616490), signed "Owner", with a timestamp, completed before the effective date of 18 August 2026; the real name shall not be used, in accordance with Article 2.2.

---

## APPENDICES

### Appendix A - Template set of three undertakings upon assuming a Staff role

A.1. Confidentiality undertaking: I, \[name or ID\], understand that the role gives me access to internal information and to the personal data of Members. I undertake: not to disclose this information beyond the scope of my authorisation, during and after my tenure of the role; to use my access only for operational purposes; and to report immediately any leak that comes to my knowledge. I understand that a breach leads to internal discipline and may give rise to liability under the law, including Luật 91/2025/QH15 and NĐ 356/2025/NĐ-CP (on personal data protection) and related regulations.

A.2. Acknowledgement of ownership: I acknowledge that the Server and its identity assets belong to the Owner; my contributions shall be recognised and honoured but give rise to no right of ownership, no shareholding and no debt; the operational documents I create belong to the common repository of the Server.

A.3. Undertaking to comply with STF: I have read STF in full; I accept a standard of conduct higher than that of Members, the rule of writing in every channel on the assumption that the content may be made public, the duty to recuse upon a conflict of interest, the discipline standard raised by one grade, the rule against handling a special case unilaterally, and the offboarding procedure. I have enabled 2FA and completed the SOP test.

A.4. Confirmed in the audit-trail channel, dated \[ \].

### Appendix B - 24-hour offboarding checklist (implementation summary of STF §26)

1. Remove roles and permissions in the Server.
2. Remove bots hosted or administered by that person.
3. Revoke and recreate the related webhooks.
4. Withdraw permissions on external services (Drive, hosting, social media).
5. Rotate shared secrets, tokens and passwords.
6. Review the audit log for the last 30 days.
7. Remove the person from the emergency contact list.
8. Draw up a record in the audit-trail channel, signed by the person carrying out the steps and by the person verifying them.

### Appendix C - Mandatory template lines

1. When receiving a direct message about a sanction: "I do not discuss sanctions through direct messages. Please submit an appeal through the [Single-Window Channel](https://discord.com/channels/1342729473245577267/1343099398720065559) - every appeal is considered under the procedure."
2. When contacted by the press, a community page or an influencer: "I am not the spokesperson of the server. All official communication is through the [Single-Window Channel](https://discord.com/channels/1342729473245577267/1343099398720065559) or by e-mail to [contact@donquaan.com](mailto:contact@donquaan.com)."
3. Internal provisional suspension: "Permissions are provisionally suspended to allow the standard review procedure - a neutral measure applied to every allegation of this category, implying no conclusion."
4. Verification in progress, for external use: "We have received the matter and are verifying it under the standard procedure. No comment on individuals."
5. Correction: "The sanction of \[X\] has been reviewed under the standard procedure and has been annulled. We apologise to \[the person affected\]."
6. Lifting a sanction applied in error after an emergency: "During the handling of the security incident of \[X\], an emergency measure affected you in error; we have restored the position and we apologise."

### Appendix D - Staff disciplinary framework table (publicly published)

| Conduct | 1st instance | 2nd instance | 3rd instance onwards |
| --- | --- | --- | --- |
| Replying about a sanction through direct messages / speaking outside the procedure / initiating direct messages to a Member outside a ticket | Recorded reminder | Formal warning | Suspension of authority for 30 days |
| Public argument in front of Members | Formal warning to both sides | Suspension of authority | Demotion |
| Breach of the internal-channel speech standard (STF §7.2) | Formal warning | Suspension of authority | Removal from role |
| Failure to log a sanction / imposing a sanction outside the framework | Reminder, sanction void | Formal warning | Suspension of authority and audit of every sanction imposed |
| Handling a SPECIAL case unilaterally and alone (Article 33.3) | Formal warning, matter referred for review | Suspension of authority | Removal from role |
| Failure to recuse upon a conflict of interest | Formal warning, outcome void | Removal from role | - |
| Selective enforcement, established through audit | Suspension of authority and review of the related sanctions | Removal from role | - |
| Guaranteeing a transaction or soliciting in the name of the Server | Formal warning | Removal from role | - |
| Failure to report an offer of a bribe | Suspension of authority | Removal from role | - |
| Omitting an item of the offboarding checklist (person responsible) | Reminder and immediate remedy | Formal warning | Suspension of authority |
| Activating an emergency or a mass action outside the list in Article 38.1, in good faith | Reminder and post hoc review | Formal warning | Suspension of authority |
| Accepting a benefit in return for lenient handling | Removal from role and ban | - | - |
| Breach of confidentiality, not widely disseminated | Suspension of authority, removal from role according to gravity | Removal from role and ban | - |
| Misuse of permissions: retrieval, disclosure, aggregation of data | Removal from role, with a ban where dissemination occurred | - | - |
| Using data to threaten or bargain with a Member | Removal from role, ban, referral of the file to the authorities | - | - |
| Abuse of the emergency permission-cut measure on fabricated grounds (STF §20.5) | Dealt with as fabrication of evidence | - | - |
| Fabrication of evidence, including fabrication of the content of a complaint | Removal from role and permanent ban, no clemency | - | - |
| Retaliation against a complainant | Heavier than the framework for the underlying violation complained of | - | - |
| Temporary use of fund monies or disbursement without the approval of the Owner (Article 43.2) | Removal from role and ban, regardless of repayment | - | - |
| Ordinary breach of the Member rules | The Member framework plus one grade, together with a proportionate role sanction | | |

Every level in the table is a minimum framework; the Council may apply a heavier level on the grounds exhaustively listed in ENF, and may not apply a lighter level without recording a publishable reason.

### Appendix E - Duty-shift reflex card

This card is pinned in the Staff channel. General principle: every step shall be timestamped into the audit-trail channel; where uncertain, use only provisional and reversible measures, then ask the level above. Each item below points back to its source provision.

1. Red Zone content (CSAM, grooming of minors, content falling within the scope of Articles 117 and 331 of the Bộ luật Hình sự (the Penal Code), threats to life, NCII, self-harm): run the Red Zone SOP in ENF. In the specific case of CSAM: report to Discord immediately, do not download, retain only metadata, remove under the SOP, escalate to the Head Admin (Article 50.1). Danger to life: 115; matters involving children: 111 (STF §23.4).
2. A privileged account causing destruction, including an admin account and including the Owner account: strip permissions or kick immediately, and report within 1 hour together with a description of the grounds observed (STF §20.5; Article 41.2).
3. A raid in progress: lockdown or slowmode, defensive measures requiring no order; notify the Staff channel (Article 39.1).
4. Receiving a direct message about a sanction: use only line 1 of Appendix C, adding nothing further (STF §7.4).
5. Contact from the press, a community page, an influencer or a parent: use only line 2 of Appendix C (STF §7.5).
6. Being offered money, a gift or a benefit: refuse in writing on the spot and notify the Staff channel within 24 hours (STF §14.2).
7. Contact from someone claiming to be Discord, a partner or a competent authority: post in the Staff channel before taking any action (STF §20.4).
8. A Member or a Staff member showing signs of self-harm: run the self-harm SOP; do not provide psychological counselling, do not delete posts outside the SOP, escalate immediately (STF §21.2, §23.4).
9. Being threatened or extorted: no payment, no promise, no deletion on demand; preserve all correspondence; escalate (Article 50.1).
10. A request to delete a channel or a role, to carry out a mass action, or to add a bot or a webhook: stop; two-person approval is required, save in a genuine state of emergency (STF §20.3; Article 38.1).
11. A matter showing indicia of being SPECIAL (a RED case, sensitive multi-party, involving Staff, carrying legal or media risk): do not handle it alone; call in Senior Staff or escalate to the Owner (Article 33.3).

---

This instrument may be amended only under Article 3.2, with a minimum notice period of 7 days for a minor amendment and 30 days for a major amendment, and only in the direction of greater strictness as regards persons holding authority. Periodic review cycle for the whole instrument: 12 months, aligned with the cycle for re-signing the Staff undertakings under STF §5.2; the next review is due before 31 July 2027.

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