---
title: "Terms of Service - Discord Server | DonQuaan"
description: "Contract of adhesion between the Member and the Server: eligibility, content scope, limits of liability, official channels and governing law."
image: "https://donquaan.com/og-hero.png"
url: "https://donquaan.com/en/discord/tos"
lang: "en"
---

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

TOS Terms of Service

# Terms of Service

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

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

The Terms of Service (cite code TOS) is the founding instrument of the [Community Legal Framework](https://donquaan.com/discord). This instrument sets out the conditions for joining the Server, the rights and obligations of participants, the legal relationship between participants and the Server and the Owner, the ownership regime applicable to Content, the termination of membership, the amendment procedure and the limitations of liability. This instrument shall be binding upon every Member from the effective date stated in the document control block; joining or remaining present in the Server constitutes acceptance under Article 7.

How to read: normative units follow the order Article → Clause → Point (Article 6 → 6.1 → 6.1(c)). References within this instrument are written as "Article 6.3"; references to another instrument of the Community Legal Framework carry the cite code, written as "CoC §6.3" or "under ENF §7.1". Terms defined in Article 2 are capitalised and bear a single consistent meaning throughout the Community Legal Framework.

---

## CHAPTER I - GENERAL PROVISIONS

### Article 1. Scope of regulation and standing of this instrument

1.1. This instrument (the "Terms" or "TOS") governs the conditions of participation, the rights and obligations of every participant in the Server, the legal relationship between participants and the Server and the Owner, the ownership regime applicable to content, the termination of membership, the amendment of the Terms, and the limitations of liability.

1.2. These Terms are the founding instrument of the Community Legal Framework. The instruments of the Framework carry system-wide cite codes (the list may be supplemented under Article 31):

a) [TOS - Terms of Service](https://donquaan.com/discord/tos) (this instrument);

b) [CoC - Code of Conduct](https://donquaan.com/discord/rules) (rules of behaviour);

c) [ENF - Enforcement and Sanctions Regulation](https://donquaan.com/discord/rules/enforcement) (the sanction ladder, recidivism limitation periods, detailed evidentiary standards);

d) [APL - Appeals Regulation](https://donquaan.com/discord/rules/appeals) (the procedure for receiving and resolving appeals);

e) [DIS - Disclaimer of Liability](https://donquaan.com/discord/disclaimer) and [PRV - Privacy Policy](https://donquaan.com/discord/privacy) (collection, storage, access, deletion of data, log retention periods);

f) [STF - Staff Rules](https://donquaan.com/discord/rules/staff) and [OWN - Owner Charter](https://donquaan.com/discord/rules/owner) (selection, probation, tiered delegation of authority, conflicts of interest, handover and revocation of privileges, Staff discipline, escalated whistleblowing);

g) [ANX-1 - Annex on Prohibited Keywords](https://donquaan.com/discord/rules/banned-words), [ANX-2 - Annex on Identity Verification](https://donquaan.com/discord/verify), [ANX-3 - Annex on Donations](https://donquaan.com/discord/donate);

h) The Framework Rules for Events and Giveaways together with the procedural annexes (SOPs) and model documents, which must include the Emergency Action Card - a one-page reference for the person on night duty (Article 13.6).

In this instrument, a reference to the "Code of Conduct" shall be read as the CoC together with its corresponding enforcement framework in ENF and APL; a reference to the "Privacy Policy" means PRV; a reference to the "Staff Rules" means STF.

1.3. Where instruments conflict, the following order of precedence shall apply: the law of Vietnam → the [Discord Terms of Service](https://discord.com/terms) and the [Discord Community Guidelines](https://discord.com/guidelines) → these TOS → the remaining instruments. Any provision of the Community Legal Framework that conflicts with a higher tier shall be void to the extent of that conflict, while the remaining provisions retain full force. In subject areas that appear in more than one instrument, the canon-instrument rule applies: ENF is the sole source of record on discipline, the sanction ladder and evidentiary standards; PRV is the sole source of record on data and logs; TOS is the sole source of record on the list of Official Channels. Other instruments may only cross-refer and must not restate the detail; where a discrepancy nevertheless exists, the text in the canon instrument shall prevail.

1.4. These Terms apply to every Member, regardless of role. No provision may be construed as granting any individual - including the Owner - a privilege standing outside the procedures established by this instrument (Article 5).

### Article 2. Definitions

Throughout the Community Legal Framework, the following terms shall bear a single consistent meaning:

2.1. "Server": the online community founded and operated by the Owner on the Discord platform, identified in Article 6, together with the affiliated spaces officially announced by the Owner.

2.2. "Discord": the platform provided by Discord Inc. The Server operates on Discord infrastructure and is subject to Discord; the Server is not Discord, does not represent Discord, and does not control Discord's decisions.

2.3. "Owner" (or "Server owner"): the individual registered as the owner of the Server on Discord at any given time, who bears ultimate responsibility for the Server. Delegation or succession shall be carried out under Article 29. The Community Legal Framework uses only the designations "Owner" or "Server owner"; the real name, nickname and any other personal identifier of the Server owner must not be used in any instrument.

2.4. "Staff" (or "the Team"): persons appointed by the Owner or by a duly authorised person to an operational role (administrators, moderators, event organisers, and equivalent roles), for as long as they hold that role. Staff are volunteers; the relationship between Staff and the Server or the Owner does not constitute an employment, agency, partnership or legal representation relationship, unless a separate instrument provides otherwise. During the period in which no Staff have been appointed, the Owner shall temporarily assume the operational roles; mechanisms that require several persons (two-person approval, panels, a designated Spokesperson) shall be activated progressively along the recruitment roadmap, and each activation shall be announced publicly in the [official announcement channel](https://discord.com/channels/1342729473245577267/1529782982016110642).

2.5. "Member": any Discord account that has joined the Server, including Staff and the Owner when they act in the capacity of a participant. Every provision applicable to Members applies to Staff and the Owner, except where the Community Legal Framework sets a higher standard for Staff or the Owner.

2.6. "Content": anything posted, sent, broadcast or shared in the Server: text, images, audio, video, files, links, custom emoji, voice messages, material broadcast in voice or stage channels, and event entries.

2.7. "Official Channels": the only recognised channels of communication and public statement, listed in Article 6.

2.8. "Single-Window Channel": the primary intake channel for appeals, reports and formal requests - the ticket channel identified in Article 6.1(c), in accordance with the CoC; the official email addresses in Article 6.1(d) are the fallback intake channel (Article 6.8). The [Single-Window Channel](https://discord.com/channels/1342729473245577267/1343099398720065559) provides a private submission flow for evidence containing personal data (Article 16.4).

2.9. "Minor": a Member under 18 years of age under the law of Vietnam. "Child": a person under 16 years of age under Luật Trẻ em (the Law on Children) of Vietnam.

2.10. "Conduct within the Server": conduct occurring in the Server's channels, at an official event held in the name of the Server, or conduct outside the Server falling within the exceptions set out in Article 23.3.

2.11. "Coordinated attack": a course of conduct by two or more accounts (or by one person using several accounts) acting on a shared script in order to disrupt, provoke, manipulate mechanisms, defame or harm the Server or its Members - constituting a standalone violation independent of the content of each individual message (Article 21.5).

### Article 3. Statement of standing - what the Server is

3.1. The Server is a voluntary, non-commercial community as at the date of promulgation, focused on technology, artificial intelligence and personal development, operating principally in Vietnamese, founded by an individual and run by a volunteer team.

3.2. Participation in the Server is a conditional access licence, granted free of charge and revocable in accordance with this instrument. Participation creates no service contract for consideration, no customer - supplier relationship, and no property right whatsoever (Article 10).

### Article 4. Statement of standing - what the Server is not

The Server declares, and Members acknowledge that they understand, that the Server is not and does not operate as:

4.1. A trading venue or commercial intermediary: the Server does not broker, does not guarantee, does not hold funds in escrow, and does not resolve trading disputes between Members (detail in Article 24).

4.2. A financial institution, investment fund, or provider of investment advice: any content concerning finance, cryptocurrency or investment appearing in the Server is the personal opinion of the poster and not a recommendation of the Server.

4.3. A certifying training institution: learning and knowledge-sharing activity in the Server is not a licensed training programme and carries no warranty as to accuracy or outcome.

4.4. A charitable organisation or fundraising body: the Server shall not solicit, receive or channel charitable donations in any form (consistent with Nghị định 93/2021/NĐ-CP (decree on the mobilisation and use of voluntary charitable contributions)); the Server may only share links to organisations legally permitted to solicit contributions. No Staff member or Member may organise fundraising in the name of the community within the Server; well-intentioned proposals of this kind must be refused and the proposer given the legal reasons.

4.5. An employer, employment agency, or legal representative of any Member.

4.6. A psychological or medical counselling service: any venting or emotional-support channels are community spaces only; Staff are not professionals and may not provide psychological or medical advice; the Server permanently displays professional support contacts: the national child protection hotline 111 and the emergency medical line 115. The Server's support email addresses (Article 6.1) do not replace these emergency hotlines: life-threatening situations must be reported by hotline, not by waiting for an email or a ticket.

4.7. Any statement, promotion or implication that the Server is one of the above - whether from a Member, Staff or a third party - shall not bind the Server and may be dealt with under the CoC.

### Article 5. Founding principles of all instruments

5.1. Primacy of process: all authority within the Server - including that of the Owner - may only be exercised through documented process. Action outside process produces no effect and may be examined as a violation.

5.2. The Owner is the supreme authority and is himself subject to the Community Legal Framework:

a) the Owner is the supreme authority of the Server in three domains: law (promulgating and amending the Community Legal Framework), personnel, and finance; that authority shall be exercised through documented process under Article 5.1;

b) the Owner may intervene directly and immediately in an emergency or serious situation;

c) day-to-day cases shall by default be handled by the Team under the ENF ladder; cases classified as "special" shall be handled by the Owner or senior Staff under ENF - no Staff member may handle a case of this class unilaterally and alone;

d) every direct intervention by the Owner shall be documented and shall be subject to the same appeal mechanism as any other measure (Article 27.6);

e) as to conduct, the Owner is bound by the same rules as every Member; allegations directed at the Owner shall be handled under the separate procedure in Article 30.5, under which the Owner may not take part in investigating himself, may not access the investigation file, and may not contact the complainant privately. By promulgating this instrument, the Owner binds himself in advance and publicly to those restrictions.

5.3. Uniform treatment: the same conduct attracts the same handling framework, whoever the violator may be. Follower count, level of contribution, level of financial support, seniority, and relationship with Staff or the Owner shall not be a ground for any handling decision, whether in aggravation or in mitigation. Every Member is handled with the same degree of privacy as provided in Article 27.11.

5.4. Non-retroactivity: no one shall be sanctioned for conduct occurring before the rule prohibiting that conduct took effect. Regulatory gaps shall be closed prospectively (Article 32.5).

5.5. Evidence first, action second; emergency action first, mandatory post-review second: every measure taken against a Member must be documented; emergency measures may be taken first but must be documented and re-reviewed within the time limits set in the CoC.

5.6. Human safety ranks above the Server's reputation, the Server's reputation ranks above harmony, and harmony ranks above operational convenience. Where the instruments require interpretation, they shall be interpreted according to this order of priority.

5.7. Minimum evidentiary standard (applicable to every handling and investigation procedure; the detailed text is in ENF):

a) logs exported by the system itself (audit logs, the Server's bot logs, data supplied by the platform) carry greater weight than screenshots; an isolated screenshot that cannot be reconciled with a log is not sufficient to establish a serious violation;

b) the number of reports is not evidence: multiple reports of identical content have no greater probative value than a single report unless accompanied by independent, verifiable evidence;

c) evidence of events occurring by DM or outside the Server must be assessed against the CoC's specific standard (multi-source reconciliation, signs of alteration, context) before being used as a ground for action;

d) fabrication of evidence (staged chat images, altered logs, deepfakes, set-ups) - whether aimed at a Member, Staff, the Owner or the Server itself - is a violation at the most serious tier of the Community Legal Framework, shall be dealt with as soon as it is proven, irrespective of whether the underlying allegation has been answered, and the Server reserves the right to report the matter to the authorities;

e) a finding of "same person" or "alternate account" must meet the CoC's evidentiary standard; no such finding may rest on impressions of writing style, time zone or avatar alone.

5.8. Conflict of interest: a person with a close personal relationship, a romantic relationship (including a former one), a personal dispute, or a material interest connected to a case may not take part in deciding, investigating or reviewing that case, and has a duty to self-declare and withdraw. Breach of the duty to withdraw may render the related decision void on appeal. The detail (declaration of gifts, separation of privileges between related persons) is in STF.

5.9. Enforcement authority belongs to the Team alone: a Member who is not Staff has no power to enforce the rules in the Team's place (self-help enforcement, demanding that others delete posts, threatening others with the rules). A Member who discovers a violation has a duty to report it confidentially through the [Single-Window Channel](https://discord.com/channels/1342729473245577267/1343099398720065559) or the report tool, and must not organise a public pile-on. Repeated self-help enforcement after a warning shall be dealt with under the CoC.

5.10. Classification of decisions and consultation: the Server publicly distinguishes three classes of matter - (a) matters put to a binding vote (the outcome binds and is stated as binding before opening); (b) matters put out for consultation (the outcome is an input only, non-binding, and is stated as such before opening); (c) matters that may never be put to a majority vote in any circumstances: safety, legal matters, platform compliance, personal data, personnel, and measures against individual violators. Any poll that does not state its class at the outset is deemed to be of class (b).

### Article 6. List of Official Channels and the No-Money-Request Principle

6.1. The Server's Official Channels are determined by control of the domain, not by an enumerated list. Every email address at the domain donquaan.com is an address of the Server, carries authority and is bound by the Community Legal Framework, including an address not named in this Article; an address not named here is an address with its own reserved function, not an address that does not exist. An email address NOT at the domain donquaan.com that holds itself out as the Server is impersonation, without exception, save for the single backup mailbox named in point i. The Official Channels are:

a) the identified Discord server: the server "DonQuaan", ID 1342729473245577267;

b) the website: [donquaan.com](https://donquaan.com/) (the full text of the Community Legal Framework is published at [donquaan.com/discord](https://donquaan.com/discord));

c) the [Single-Window Channel](https://discord.com/channels/1342729473245577267/1343099398720065559): the ticket channel for receiving appeals, reports and formal requests (the fastest intake channel, and the recommended first choice);

d) inbound email addresses, by function: [support@donquaan.com](mailto:support@donquaan.com) and [contact@donquaan.com](mailto:contact@donquaan.com) (support and general contact - usually answered within 24 hours; matters requiring review may take 1-3 days or 3-7 days depending on the case) · [legal@donquaan.com](mailto:legal@donquaan.com) (claims, requests to amend the instruments and legal matters generally) · [private@donquaan.com](mailto:private@donquaan.com) (reports and submissions requiring anonymity; the identity of the sender is kept confidential under STF §29.7 even where the matter is published) · [collab@donquaan.com](mailto:collab@donquaan.com) and [contact@donquaan.com](mailto:contact@donquaan.com) (partnership and collaboration with the Server);

e) the only official outbound email address: [notify@donquaan.com](mailto:notify@donquaan.com) (own domain, send-only - it does not receive mail) - authenticated by the SPF, DKIM and DMARC standards; the authentication configuration shall be completed and published at the [Annex on Identity Verification](https://donquaan.com/discord/verify) before the effective date of this instrument. Any gmail address or other variant claiming to be the Server is an impersonation;

f) official social media pages: the list of official social media accounts of the Server and the Owner is published in one place only, in the footer of [donquaan.com](https://donquaan.com/) (currently: Facebook, Twitch, X, Spotify, YouTube, Roblox, GitHub, Discord, HubSpot - the footer list is the most current version); any account not on that list is an impersonation;

g) the [official rules channel](https://discord.com/channels/1342729473245577267/1342766172000616490) (which publishes and pins the full text of the Community Legal Framework inside the Server);

h) the [official announcement channel](https://discord.com/channels/1342729473245577267/1529782982016110642) (an announcement made in the name of the Server takes effect only when posted there).

i) the single backup mailbox outside the domain: [contact.donquaan@gmail.com](mailto:contact.donquaan@gmail.com), to be used only where the domain donquaan.com is unavailable; response time is significantly slower. This is the only exception to the domain rule in this Article; every other address outside the domain is impersonation;

k) direct messages from Staff within the Server, and the Server's [online support form](https://forms.gle/f1V76wZvdkyHxc1Y9) (full backup link: [full version](https://docs.google.com/forms/d/e/1FAIpQLSenOB6ZqHxBB2W6LorEeNbFCsbKk09L0o10cKjdG4EZsve8ig/viewform)), which is also published at the [Single-Window Channel](https://discord.com/channels/1342729473245577267/1343099398720065559) and the [official announcement channel](https://discord.com/channels/1342729473245577267/1529782982016110642). A direct message is a valid support channel, but it does not alter the No-Money-Request Principle in Article 6.3 or the QR code rule in Article 6.4: no one belonging to the Server asks for money, proposes a bank transfer or sends a QR code through direct messages, in any circumstances and without exception;

l) apart from the channels named in this Article, every other channel holding itself out as a support channel of the Server is fraudulent. The safest channels, in recommended order, are: email at the domain donquaan.com, the [Single-Window Channel](https://discord.com/channels/1342729473245577267/1343099398720065559), direct messages from Staff within the Server, and the Server's [online support form](https://forms.gle/f1V76wZvdkyHxc1Y9).

6.2. The Server has no secondary server, no public backup server, and no other official copy beyond those listed in 6.1. A backup server (if any) shall be registered in the Owner's own name and may be activated only by a cross-posted announcement on at least two Official Channels, one of which must be the website in 6.1(b). Any invitation to move to a new or backup server that does not satisfy this condition is a forgery.

6.3. The No-Money-Request Principle (in force in perpetuity, without exception):

a) no one associated with the Server - the Owner, Staff, event organisers, the Server's bots - may send a direct message (DM) asking for money, charging a fee, requesting a transfer, requesting a deposit, demanding a "prize collection fee" or a "reservation fee", or sending a QR code, for any reason whatsoever, even where the voice, image or video appears identical to the real person;

b) every legitimate financial request or item of financial information of the Server exists in exactly one place: the donation intake point permanently and publicly published at the [Annex on Donations](https://donquaan.com/discord/donate), cross-checked against the website in 6.1(b). The Server shall not change its payment details by DM, by urgent announcement, or with a deadline attached, in any circumstances;

c) any message contrary to (a) and (b) is by default a scam or a forgery, even if it comes from an account or bot that appears genuine (it may have been compromised); Members have a duty not to comply and are asked to report it through the [Single-Window Channel](https://discord.com/channels/1342729473245577267/1343099398720065559).

6.4. QR code rule: the only QR code permitted in the Server's activities is the donation-receipt code at the fixed published point referred to in 6.3(b), cross-checked against the website. All other QR codes are prohibited without exception in every activity (including "role-claim QR", "event check-in QR", "verification QR"); and no QR code whatsoever may be sent by direct message (DM) in any form, including the donation-receipt code at the fixed published point referred to in 6.3(b). Any QR code outside the published point in 6.3(b) is by default a forgery.

6.5. A statement made in the name of the Server to the outside world (press, news sites, KOLs, other communities) is valid only if made by the Spokesperson designated under STF and through an Official Channel. A statement by any other individual - including Staff - does not represent the Server.

6.6. The provisions of Article 6 are permanently pinned in the [official rules channel](https://discord.com/channels/1342729473245577267/1342766172000616490) and are restated monthly using a fixed template post (with reminders on 2FA safety and QR codes) in the [official announcement channel](https://discord.com/channels/1342729473245577267/1529782982016110642). This is a baseline declaration made in peacetime, serving as the reference point against which any impersonation, image or voice forgery, or false report about the Server or the Owner is to be checked.

6.7. Anti-fraud protection for the Team: any contact claiming to be a Discord employee, a platform representative, a public authority, a lawyer or a partner, sent to any Staff member, must be reported to the Team's internal channel before any request is complied with; Discord does not handle violations by personal DM. This rule is a mandatory part of role-onboarding training (STF).

6.8. DMs are not an official support channel: Discord direct messages are not a channel for support, intake or official handling by the Server. A DM between Staff and a Member about Server business is legitimate only where the Staff member has arranged it in advance in a ticket in the [Single-Window Channel](https://discord.com/channels/1342729473245577267/1343099398720065559); a Staff member who initiates a DM to a Member outside process commits a Staff disciplinary violation (STF). Zalo, Messenger and every other platform outside the list in 6.1 are not official channels; any contact in the name of the Server through those channels is by default an impersonation. General recommendation: use a ticket in the Single-Window Channel first; email is the fallback.

6.9. Standard for submissions through the Single-Window Channel and by email: every submission, report or appeal must contain at a minimum - (i) the sender's Discord username; (ii) the user ID concerned; (iii) a clear statement of the matter; (iv) evidence if available (avoid blurred screenshots or crops that omit context - see the evidentiary standard in Article 5.7); (v) a clear purpose (appeal, report, enquiry, data request). Where a submission lacks information or its purpose is unclear, Staff shall request completion once before considering any sanction. Junk submissions or deliberate harassment after such a request may attract a warning or a timeout of 1-24 hours depending on severity; spamming submissions or sabotaging the intake channel may attract a timeout exceeding 1 day depending on severity - the detailed framework is in ENF. These sanctions apply only to junk submissions or deliberate harassment: a person who states their case clumsily but in good faith shall not be penalised, and the principle of protecting good-faith reporters (Article 27.9) remains fully intact.

---

## CHAPTER II - CONDITIONS OF PARTICIPATION AND ACCEPTANCE OF THE TERMS

### Article 7. Acceptance of the Terms

7.1. On joining the Server, a Member must read and click to confirm acceptance through Discord's rules screening mechanism or an equivalent confirmation mechanism established by the Server. That confirmation, together with the related system logs (time of joining, time access was granted), constitutes evidence of consent to the entire Community Legal Framework listed in Article 1.2.

7.2. Continued presence and activity in the Server after the Terms take effect or are validly amended (Article 31) shall likewise be deemed acceptance. A Member who does not agree with any provision may leave the Server at any time under Article 27.1.

7.3. Members confirm that they participate entirely voluntarily, free from coercion, and not in reliance on any promise outside the content of the official instruments.

7.4. Where a person does not satisfy the conditions in Article 8, clicking to accept does not create valid membership, and the Server may terminate it under Article 27.

### Article 8. Conditions of participation and protection of minors

8.1. Minimum age: a Member must be at least 13 years old and must meet the minimum age for using Discord under the law of their place of residence, in accordance with the [Discord Terms of Service](https://discord.com/terms). The Server shall not lower this standard in any circumstances.

8.2. Persons under 13: if the Server discovers, or has reasonable grounds to believe, that an account belongs to a person under 13 (including where that person discloses it themselves), the Server shall act uniformly and without exception: (a) report the account to Discord under the platform's under-age procedure; (b) remove the account from the Server; (c) send a notice using a pre-drafted template stating clearly that the person may rejoin when they reach the required age; (d) establish no separate access arrangement of any kind for persons under 13. This is a platform-compliance obligation, not a punishment.

8.3. Advice and restrictions applicable to Members aged 13 to under 18:

a) the Server strongly recommends that participation take place with the knowledge and consent of a parent or guardian;

b) minors may not take part in any space, event or content marked 18+ (if any), and the Server applies a public content standard that is safe for a 13-year-old - stricter than Discord's default (detail in the CoC);

c) minors should not make financial donations to the Server and are discouraged from doing so; donations by minors shall be refunded under Article 25.4;

d) a prize or award worth 500,000 VND or more involving a minor may be awarded only with the confirmation of a parent or guardian and through the two-person approval procedure at the time of award, under the Framework Rules for Events;

e) the Server prohibits, without exception and irrespective of channel structure or age labelling, any event or mechanism for anonymous pairing or Server-arranged private one-to-one chat between strangers. This prohibition admits of no exception for 18+ channels.

8.4. Warning concerning direct messages (DMs): DMs between Discord accounts lie outside the Server's visibility and outside its technical control. Members - particularly minors and parents - are warned that the risks of fraud, grooming and harassment by DM exist on every platform. The Server's responsibility for events occurring by DM is a responsibility to warn proactively, to support victims and to cooperate with the authorities under Article 23.4; it is not a responsibility to guarantee or to compensate.

8.5. Child safety commitment: every signal of grooming, of the solicitation of minors, or of child sexual abuse material shall be handled under the procedure at the highest protective level of the Community Legal Framework: immediate protective isolation, a report to Discord Trust & Safety, guidance to the family on reporting to the police, no public handling in any circumstances, and no variation of the handling for any pressure or relationship whatsoever. Inviting a minor to move to private chat on another platform is a signal that mandatorily triggers review under the safety SOP. Detail is in the CoC and the safety SOP.

8.6. The Server has no full means of age verification and does not warrant that every Member states their age truthfully; a Member who misstates their age bears responsibility for that misstatement, and it gives rise to no liability of the Server beyond the duty to act on discovery under Article 8.2.

### Article 9. Accounts and identity

9.1. Members are responsible for the security of their own Discord account (password, 2FA, devices). Conduct originating from an account is by default treated as the conduct of the account holder. A self-declared account compromise does not automatically excuse liability: such a declaration shall be accepted only where objective indicators exist (a break in behavioural pattern, unusual timing, recovery verification under 9.2); the duty to cooperate in verification rests with the account holder.

9.2. Where there are signs that a Member's account has been compromised (posting scams, unusual destructive activity), the Server shall prefer a protective freeze (temporary isolation) over punishment, and shall apply a verification procedure before restoration, under the CoC. This rule applies to Staff accounts as well, together with the Circuit Breaker mechanism in Article 21.4.

9.3. Impersonation prohibited: impersonating the Owner, Staff, an official bot, or another Member (by name, avatar, webhook or any other means) is a serious violation and may also constitute an offence at law; the Server shall report it to the platform and assist the victim in making a report.

9.4. Alternate accounts (alts): using an alternate account to evade a measure in force is a standalone violation (Article 27.8). Using multiple accounts to exploit mechanisms (events, points, voting) shall be dealt with under the mechanism-abuse provisions of the CoC.

### Article 10. Membership is not a property right

10.1. Membership, roles, levels, virtual points or coins, badges, channel access and every other status within the Server are usage privileges granted by the Server and are not the property of the Member. They have no cash value, are not transferable, are not inheritable, and may be adjusted, reset or revoked under the Community Legal Framework.

10.2. Virtual coins and points in the Server may in no circumstances be converted into money or into goods with market value by any route, and the Server does not sell coins or points. Any buying or selling of coins or points between Members is prohibited; if a grey market is found to be forming, the Server may shut down the entire coin or point mechanism concerned without any obligation to compensate. Shutting down the mechanism is a technical measure protecting the Server's legal position, not a punishment aimed at good-faith users, and shall be announced together with the reasons.

10.3. Right to refuse service: the Server may refuse, restrict or terminate the participation of any account in accordance with the procedures of the Community Legal Framework. No one has a right to remain in the Server; equally, no one shall be terminated without grounds, documentation and an avenue of appeal under Article 27.

10.4. Restriction or termination of membership gives rise to no obligation of the Server or the Owner to compensate any loss that the Member considers themselves to have suffered (including business opportunity, income, or reputation associated with activity in the Server), because membership is a free conditional licence under Article 3.2 and Article 10.1.

### Article 11. Ownership of the Server, operational assets and recognition of contributions

11.1. The Server, its name, its emblem, its channel structure, its identity assets and the official accounts listed in Article 6 are owned and disposed of by the Owner (and by any lawful successor legal entity in future).

11.2. Every contribution of effort by Staff and Members to the Server shall be recognised and honoured publicly under a dedicated mechanism, but constitutes no co-ownership, equity, debt, or veto right over the Server, regardless of the scale and timing of the contribution. No one may claim to be a co-founder with ownership rights in the absence of an instrument signed by the Owner establishing that status.

11.3. No individual may set up a "backup", "reserve" or "branch" server in the name of the community. A copy of the community registered in another individual's name is not recognised and may be dealt with as impersonation under Article 9.3.

11.4. On taking up a role, Staff must confirm in writing that they have read and accept this Article 11, in accordance with STF.

11.5. Operational assets belong to the common repository: all operational documents, event plans, process data, bots, webhooks, integrations, and access to external services (drive, hosting, social media management) created or used for the operation of the Server are operational assets of the Server, must be stored in the common repository controlled by the Owner, and must be entered in the technical asset register (a list of bots, webhooks and integrations together with the person responsible and the privilege level). When a person leaves a role: privileges and assets shall be recovered immediately under the STF offboarding checklist; retaining access, webhooks or data, or refusing to hand over, is a serious violation that survives departure from the role (Article 27.4) and may, depending on its nature, be dealt with at law.

---

## CHAPTER III - RELATIONSHIP WITH DISCORD AND WITH THE LAW OF VIETNAM

### Article 12. Relationship with the Discord Terms of Service and Community Guidelines

12.1. Everything Discord prohibits is prohibited in the Server, even where the Community Legal Framework does not restate it. The fact that conduct is not named in a Server instrument does not mean that it is permitted, if it breaches the [Discord Terms of Service](https://discord.com/terms) or the [Discord Community Guidelines](https://discord.com/guidelines).

12.2. The Server's rules may supplement Discord's only in a stricter direction and may never relax them in any circumstances. Where the Server sets a higher standard (for example the 13-year-old-safe content standard in Article 8.3(b)), the Server's standard applies.

12.3. The Server has the right, and in certain cases the duty, to report to Discord Trust & Safety violations falling within the platform's jurisdiction (child sexual abuse material, threats of violence, self-harm, under-age accounts, and other serious violations). Proactive reporting by the Server is part of the standard procedure, is not contingent on personal sympathies, and the self-reporting record constitutes evidence of the Server's good-faith compliance where a third party alleges tolerance of violations.

12.4. Members understand and accept that: Discord may independently act against an account or against the Server itself (suspension, restriction, deletion) at the platform's sole discretion; the Server does not control, does not warrant and is not responsible for those decisions, nor for technical outages of the platform. Where communication through Discord is lost, the only authenticated information channels are the remaining Official Channels in Article 6.1; the Server maintains an appeal record and fallback communication arrangements prepared in peacetime under the crisis SOP.

### Article 13. Compliance with the law of Vietnam

13.1. The Server and every Member acting within the Server must comply with the law of Vietnam, with particular attention to:

a) Bộ luật Hình sự (the Penal Code) - the following are prohibited in the Server without exception: any content or conduct bearing signs of propaganda against the State, insulting national leaders, or incitement to violence (Articles 117, 331 and related provisions); child sexual abuse in any form (Articles 146, 147); humiliation and defamation (Articles 155, 156); threats to kill (Article 133); intentional infliction of bodily harm and preparatory acts (Article 134); fraudulent appropriation of property (Article 174); extortion of property (Article 170); gambling and organising gambling (Articles 321, 322); infringement of copyright on a commercial scale (Article 225);

b) Luật 91/2025/QH15 (Law on Personal Data Protection) and Nghị định 356/2025/NĐ-CP (decree detailing personal data protection) - governing the Server's collection, storage and use of Member data (Article 22 and PRV);

c) Nghị định 147/2024/NĐ-CP (decree on the management, provision and use of Internet services and online information) - governing the duty to remove infringing content and related management duties;

d) Nghị định 93/2021/NĐ-CP (decree on the mobilisation of voluntary charitable contributions);

e) the rules on fake news and false information (Nghị định 15/2020/NĐ-CP (decree on administrative sanctions in the post, telecommunications and information technology sectors), as amended and supplemented).

13.2. Emergency Takedown List: content bearing signs of a criminal offence or falling within the high-danger group (child sexual abuse; subversion of the State; calls for terrorism or violence; non-consensual intimate imagery, including deepfakes bearing a real person's face; pornography accessible to minors; organising gambling; threats to life with a location element; arrangements to meet offline to settle a dispute by violence) shall be removed or isolated as soon as it is discovered, without waiting for consultation, under an SOP that timestamps each step, with an internal SLA target of 1 hour from the Team's discovery; time bands with no one on duty rely on automod as the first tier. The Server retains the handling record (metadata, timestamps) as evidence of compliance.

13.3. Special rule for child sexual abuse material (CSAM): in no circumstances shall it be downloaded, forwarded or copied for any reason, including as evidence; it shall only be removed or blocked, reported through the platform's official tool, with metadata and timestamps retained (not the content), and reported to the authorities under the SOP. Planting illegal content in the Server in order to entrap, extort, or denounce the Server is a violation at the most serious tier; the Server does not pay, does not negotiate, and reports immediately (Article 21.3 applies mutatis mutandis).

13.4. The Server has a duty, and undertakes, to cooperate with the competent State authorities upon a lawful written request: providing data and relevant logs within the scope held by the Server, in accordance with due legal process. Members are given advance notice of this principle here.

13.5. If any activity of the Server crosses a threshold giving rise to administrative procedural obligations at law (by scale or by the nature of the service), the Owner is responsible for completing those procedures or for adjusting the activity accordingly; components requiring legal conditions that are not yet met shall remain in the Suspended-pending-conditions state and may not be activated by any Staff member (Article 33).

13.6. Emergency Action Card: the Server maintains a one-page guide, published in the Team channel, for the person on duty who encounters an Emergency Takedown situation with no superior online, comprising at a minimum: remove or isolate → do not destroy system traces, do not download prohibited content to any device → report to the platform → record timestamps → escalate along the emergency contact chain. A person on duty who follows this Card correctly is internally absolved of responsibility for the outcome, even where the handling was less than optimal.

13.7. The Server is not an investigative authority and is no substitute for the law. In a case bearing signs of a criminal offence, the Server's role is limited to: acting on content or accounts within the community's jurisdiction, preserving evidence properly, guiding victims to the correct reporting channel, and cooperating with the authorities. The Server does not promise investigative outcomes, does not conduct public trials, does not publish findings in place of the competent authority, and does not offer further qualitative commentary on politically or legally sensitive matters beyond the standard handling notice.

---

## CHAPTER IV - CONTENT: OWNERSHIP, LICENSING, REMOVAL

### Article 14. Ownership of Member content

14.1. Members retain all intellectual property rights in Content they create and post in the Server. Participation in the Server transfers no ownership of content to the Server, the Owner or anyone else.

14.2. The Server, the Owner and Staff may not appropriate, independently commercialise, or claim ownership of a Member's content beyond the scope of the licence in Article 15.

### Article 15. Licence granted by Members to the Server

15.1. By posting Content in the Server, a Member grants the Server a non-exclusive, royalty-free, worldwide licence, sublicensable to infrastructure providers to the extent necessary, in order to:

a) store, display and transmit the Content within the Server through Discord's normal operating mechanisms;

b) back up and log it for administration, safety, investigation of violations and resolution of appeals, in accordance with PRV;

c) quote, pin and compile the Content within the Server for community purposes (for example: compiling learning resources, honouring good posts).

15.2. Use outside the Server (re-posting a Member's content to the Server's website, social media or promotional materials) may only take place where (a) the author consents, or (b) the Content was submitted to a space or event whose published rules announced that use in advance; and in every case the author must be credited unless the author requests anonymity. A Member may withdraw consent as to future uses outside the Server at any time through the [Single-Window Channel](https://discord.com/channels/1342729473245577267/1343099398720065559).

15.3. The licence in 15.1(a) and (c) terminates when the Content is deleted or the Member leaves the Server, save for: (i) log records and evidence retained on a lawful basis under Article 22; (ii) content validly quoted in other persons' conversations through the platform's natural mechanisms; (iii) technical backups, which are deleted on their rotation cycle.

15.4. The Server does not sell, does not lease, and does not use Member Content to train commercial AI models without the author's express and separate consent.

### Article 16. Member warranties as to Content

16.1. In posting Content, a Member warrants that: (a) they have the right to post it; (b) it does not infringe anyone's intellectual property rights, image rights or privacy rights; (c) it does not breach the law of Vietnam, the Discord Terms of Service, the Discord Community Guidelines or the Community Legal Framework.

16.2. Members bear legal responsibility for the Content they post. Where a Member's Content causes the Server or the Owner to face a third-party complaint, demand, action or penalty, the Member shall cooperate in resolving it and shall be responsible for loss arising from their own violation, to the extent permitted by law.

16.3. The following are prohibited from being posted (minimum list, not exhaustive): content on the Emergency Takedown List (Article 13.2); content infringing copyright (cracked courses or software, pirated service accounts, unauthorised broadcasts - including where presented as sharing for study purposes); another person's identifying information placed in a hostile context (doxxing - defined by context and intent, irrespective of whether the information was already public); fabricated evidence (Article 5.7(d)); malware; fraudulent content; deepfakes or composites placing a real person's face into a sensitive or degrading context - prohibited in every case, whether or not the person harmed is a Member, and with no exception for technical demonstrations. Detail and the handling framework are in the CoC; the list of prohibited keywords is in ANX-1.

16.4. Submitting evidence containing another person's data: a Member who needs to report or appeal with evidence containing another person's personal data (DM screenshots, images, phone numbers) must submit it through the private flow of the [Single-Window Channel](https://discord.com/channels/1342729473245577267/1343099398720065559) and must not post it publicly. A good-faith victim who inadvertently posts publicly shall be handled on a support-first, no-blame basis: the third-party data shall be removed or masked, the person shall be shown how to resubmit through the correct flow, and the case shall be taken up immediately - that removal is not a rejection of the report and shall not be counted as a violation where good faith is clear.

### Article 17. Right to remove content and Server measures

17.1. The Server may remove, hide, limit the visibility of, or lock a topic in respect of any Content that breaches the Community Legal Framework, the Discord Terms of Service, the Discord Community Guidelines or the law, under the procedure corresponding to its severity (emergency takedown under Article 13.2; ordinary handling under the CoC). A topic lock is a cooling-off tool, not a punishment, and creates no violation record for those taking part in the discussion.

17.2. Removal of content for compliance purposes is not, and may not be construed as, a finding of fault against the poster; a finding (if any) follows the separate violation-handling procedure, with documentation and an avenue of appeal.

17.3. For content relating to a mental health crisis or signals of self-harm: the Server acts under the safety SOP (limiting spread, connecting the person to support resources, reporting to the platform) - a cry for help is not deleted as a violation would be; the guidance content of this SOP must be approved by a suitably qualified professional before promulgation. The safety SOP also governs cumulative patterns of self-harm behaviour (not merely isolated posts) in accordance with the CoC.

17.4. Content posted by the Server's bots or automated systems is the Server's responsibility to manage; the Server maintains an emergency stop for all automation which every Staff member on duty is authorised to trigger. Deliberately manipulating the Server's bots or AI (including prompt injection) to generate infringing content is a violation by the manipulator, and the Server shall in addition remove that content under the same procedure as ordinary infringing content.

17.5. Content broadcast at events: the Server does not organise the replay of unlicensed copyright content (films, sport, music) at official events; the specific limits and responsibilities are set by the Framework Rules for Events. Event hosts and moderators are pre-authorised to cut off a guest's content when it enters a prohibited area (Article 19.2) without seeking permission in the moment.

---

## CHAPTER V - BOUNDARIES OF RESPONSIBILITY

### Article 18. General principle on responsibility

18.1. The Server is provided as-is, free of charge, by a volunteer community. To the maximum extent permitted by law, the Server and the Owner do not warrant: continuous, uninterrupted operation; the absence of technical faults; the accuracy, completeness or usefulness of any content shared by Members or guests; complete safety from third-party misconduct; or the presence of the Team at every hour. The full disclaimer is in DIS.

18.2. Nothing in this instrument excludes or limits liability that the law of Vietnam does not permit to be excluded (including liability for loss caused intentionally). The limitations of liability in this Chapter apply to the maximum extent permitted by law.

18.3. The limitations of liability in this Chapter do not release the Server from its positive duties: the Server binds itself to the positive duties set out throughout the Community Legal Framework (content-removal SLAs, periodic warnings, victim support, compliance records). A disclaimer of compensation always travels together with a duty to act correctly under process.

### Article 19. Content and advice of Members and guests

19.1. Every opinion, technical instruction, knowledge share, professional assessment, and item of financial, health or legal information appearing in the Server belongs to the individual speaker, not to the Server, and does not constitute professional advice. Members assess it and act on it at their own risk. Shared content in sensitive categories (money, health, career and education decisions) carries a mandatory disclaimer under the CoC.

19.2. A guest's statement at an event does not represent the Server; the Server has the right and the duty to intervene during an event where a statement enters a prohibited area (under the Framework Rules for Events and Article 17.5), but is not responsible in place of the guest for what the guest says.

19.3. The fact that the Server has previously invited, introduced or collaborated with an individual or organisation is not an indefinite endorsement of that individual or organisation. Where a third party connected to the Server's older content becomes involved in a serious violation, the Server shall handle the legacy content under the crisis SOP (contextual note or removal, with a trace retained), and shall not remove it silently.

### Article 20. Third-party links, files and tools

20.1. Links, files, source code and tools shared by Members lie outside the Server's control; Members download and use them entirely at their own risk. The Server applies automated filtering layers and sharing-control rules (the Server has no channel for sharing executable files: sharing executables - .exe, directly runnable scripts - is prohibited in every channel; the list of prohibited formats admits of no exception under the CoC), but does not warrant that all malicious content will be detected.

20.2. Third-party bots and integrations operating in the Server must be vetted before being added (least privilege, the provider's data policy, the reputation of the source) under the two-person approval procedure, entered in the register under Article 11.5, and re-vetted periodically even while running stably (guarding against changes of ownership or behaviour). A bot or integration that touches Member data must additionally pass review under PRV. Bots and integrations are operated by third parties and may change behaviour outside the Server's control; on discovering that a bot or integration is causing harm, the Server shall isolate it immediately, trigger the emergency stop (Article 17.4) and notify the affected Members.

### Article 21. Security incidents, emergencies and attacks

21.1. The Server maintains reasonable defensive measures (mandatory two-factor authentication for Staff, least privilege and tiered delegation - including authority over emoji and asset management, a two-person approval rule for dangerous operations, and pre-set defence levels with objective criteria for raising and lowering them). No system is immune; Members understand that attacks may occur.

21.2. In an emergency (raid, account takeover, mass dangerous content), the Server may apply immediate broad measures (channel locks, slow mode, mass blocking or isolation). Being caught by such an emergency measure in error is an operational risk announced in advance; the Server has a duty to: (a) operate a fast objection channel, published in advance, and to handle every objection within 24 hours; (b) proactively review groups of accounts showing signs of having been wrongly caught, within 72 hours; (c) restore access and apologise using the standard template to those wrongly affected.

21.3. The Server operates a responsible disclosure policy for good-faith vulnerability reports through the [Single-Window Channel](https://discord.com/channels/1342729473245577267/1343099398720065559) (Article 6.1(c)) or the email address [support@donquaan.com](mailto:support@donquaan.com), and undertakes to respond within 72 hours. Any demand for money or benefit in exchange for non-disclosure shall be treated as extortion: the Server does not pay, does not negotiate, retains all evidence and reports the matter to the authorities.

21.4. Circuit Breaker mechanism: where destructive activity is under way from an account holding legitimate privileges (a compromised Staff account, a compromised bot, or a Staff member acting destructively on purpose), any Staff member who witnesses it is entitled and obliged to apply emergency measures immediately within their technical reach (removing privileges, isolating, stopping automation), including against a person of higher rank, subject to two constraints: immediate escalation along the emergency contact chain, and mandatory post-review under Article 5.5. A person who acts in good faith and by the correct procedure shall not be disciplined, even where they misjudged the situation. Whether the Staff account concerned was a victim or an accomplice shall be determined afterwards, under the evidentiary standard in Article 5.7.

21.5. Coordinated attack (Article 2.11 - including raids, brigading, sleeper raids, false-report campaigns, and scripted provocation) is a standalone violation: the fact that each individual message would be acceptable does not excuse the conduct taken as a whole. The Team is authorised to act quickly and broadly against an attacking group under the identification criteria in the CoC (time of joining, behavioural pattern, signs of coordination), subject to post-review and to the objection channel under Article 21.2 in order to protect those swept up in error.

### Article 22. Personal data (by reference)

22.1. The collection, use, storage, sharing and deletion of Members' personal data shall be carried out under [PRV - Privacy Policy](https://donquaan.com/discord/privacy) (the canon instrument on data) - an instrument that Members accept at the same time as these TOS - on the principles of: minimal collection, use for the announced purpose only, time-limited retention, access by privilege tier, and respect for the rights of data subjects under Luật 91/2025/QH15 (Law on Personal Data Protection) and Nghị định 356/2025/NĐ-CP (decree detailing personal data protection).

22.2. Members are given advance notice here of the two most important points:

a) the Server keeps logs for administration, safety and the resolution of appeals (including enforcement logs and, within technical limits, deleted messages in certain channels) - the scope, the retention period for each log type and the persons permitted to access them are published in PRV;

b) deletion requests shall be met so far as technically feasible; data serving a legal obligation, the resolution of an appeal, or the protection of a third party's lawful interests (for example evidence of a violation that a victim needs in order to make a report) shall be retained on a lawful basis, for a limited period and under access control. A deletion request is not a tool for destroying evidence: a violator cannot use the right of erasure to delete the very evidence of their violation while it is in the handling or reporting process.

22.3. A Staff member who uses access privileges for purposes other than administration (prying into private lives, taking Members' affairs outside, retaining data after leaving a role) commits a serious violation; in such a case the Server stands with the injured Member, including by supporting a report to the authorities of unlawful conduct by that former or serving Staff member.

### Article 23. Boundaries of responsibility for events outside the Server's visibility

23.1. The Server has the technical capacity to observe and intervene only in respect of Conduct within the Server (Article 2.10). DMs, other platforms, and offline life lie outside that visibility.

23.2. For events originating in the Server but occurring outside it (DM scams, luring people to another platform, disputes taken into the offline world), the Server's responsibility is to: (a) issue proactive, periodic preventive warnings; (b) intervene as to the part of the conduct that remains within the Server; (c) support the victim under Article 23.4; (d) cooperate with the authorities under Article 13.4. The Server accepts no responsibility to guarantee safety beyond its technical reach and does not compensate loss caused by third parties beyond that reach.

23.3. The Server has jurisdiction over conduct outside the Server only within the closed list of exceptions in the CoC (conduct aimed at a Member or the Team because of their membership; conduct at an official offline event or at an event trading on the Server's name; a well-founded safety risk). Outside those exceptions, the Server does not police anyone's private life; in particular, leaked private chat content from outside the Server may be used as a ground for action only where an exception applies and the evidentiary standard in Article 5.7 is met.

23.4. Victim support package (a positive duty of the Server): where a Member is the victim of fraud, harassment or a data breach connected to the Server, the Server shall provide: guidance on reporting to the correct authority (with a list of the evidence to preserve), extraction of relevant logs within lawful limits, action against the violating account within the Server, and a report to the platform. The Server does not promise to recover money on anyone's behalf and does not promise outcomes, as those lie within the authority of the State.

### Article 24. Transactions between Members

24.1. Every sale, exchange, capital contribution, group purchase or engagement of services between Members - even where agreed in a Server channel - is a private transaction between those parties. The Server is not a party to it, does not broker, does not guarantee, does not hold funds, does not mediate as of right, and does not compensate loss. This statement shall be permanently pinned in every channel of a trading or exchange character (if any such channel is opened).

24.2. Staff are prohibited from vouching for a transaction in the name or on the standing of their role; any statement guaranteeing a Member's transaction on the strength of a role is a Staff disciplinary violation. A Staff member who transacts privately with a Member must state clearly that the transaction is personal, in accordance with STF.

24.3. The Server prohibits, and proactively removes, listings in prohibited categories (pirated accounts or courses, cracked software, "investment tips", organised group buys and money pooling, and other items under the CoC). Whether the Server has removed a listing, or has not yet done so, does not alter the private character of the transaction under 24.1.

24.4. A Member who is the victim of fraud in a private transaction is entitled to the support package in Article 23.4.

### Article 25. Financial donations

25.1. Every donation by a Member to the Server is a voluntary, unconditional, non-refundable gift, and purchases no privilege, no immunity from discipline, no feature commitment and no reciprocal obligation of the Server. This statement shall be displayed at every donation intake point. Promises as to features or roadmap (if any) are good-faith direction, not a reciprocal commitment for any donation. Detailed conditions are in [ANX-3 - Annex on Donations](https://donquaan.com/discord/donate).

25.2. The Server sets no conditions, does not suggest "donate in order to get X", and does not solicit money by DM in any circumstances (Article 6.3). The Server accepts donations only through the intake point published under Article 6.3(b); no Staff member may receive community money through a personal channel outside the published list.

25.3. Control of funds: management, publication of the accounts and reconciliation shall be carried out under the financial regulation within the Community Legal Framework, on the following mandatory principles:

a) only the Owner approves every inflow and every item of Server expenditure; no subordinate - including a co-owner - may spend on their own initiative;

b) a co-owner or a person given a task may spend only under a written, item-specific, still-valid authorisation issued by the Owner; even in an emergency, spending is possible only on the basis of a written authorisation issued in advance by the Owner - no implied emergency spending ceiling exists for any position;

c) the Server maintains an independent reconciliation bookkeeper - recording and reconciling only, with no spending authority;

d) every item of expenditure has a supporting document; the accounts are published periodically in summary form (total income, total expenditure by category), with the detail held internally for reconciliation.

25.4. The refund regime: all cases in which the Server makes a refund are laid down exhaustively in this Article; apart from the cases listed in this Article there is no further case of refund. Any other document may only cross-refer to this Article and may not create, narrow or make conditional any case of refund. A donation of 500,000 VND or more requires the donor to confirm that they are 18 or older or have guardian consent. The Server maintains a refund reserve under the financial regulation so that the obligations under this Article can always be met. The cases of refund are:

a) A donation in real money by a minor shall be refunded in full to the same method or account from which it was sent, without dispute, where a parent or guardian so requests within 90 days of the donation. A valid request shall be refunded within 72-120 hours; higher-value amounts shall be prioritised. A request made after 90 days shall not be refused automatically but shall be considered under the Owner Charter §43.3, since a transaction by a minor may be void under the Bộ luật Dân sự (the Civil Code);

b) A donation in real money shall be refunded by the Server on its own initiative, without any request being required and subject to no time limit, where the Server determines that the donor is under legal age or that the source of funds is unlawful. This case is implemented under the Annex on Server Donations §2.2 and operates independently of point a: the absence of a request by a guardian shall not extinguish the Server's obligation to refund;

c) Virtual items, virtual gifts and in-platform currency shall be refunded 100% where the giver so requests through the [Single-Window Channel](https://discord.com/channels/1342729473245577267/1343099398720065559). This case is subject to no time limit, does not depend on the age of the giver and carries no other condition, since those assets have no legal value and are not convertible into real money. The detailed procedure is laid down in the Annex on Server Donations §3.2;

d) Apart from the three cases in points a, b and c, a donation in real money shall not be refunded, save where the law provides otherwise.

25.5. The no-exception red lines on money (no model that takes money from participants - introduces an element of chance - and pays out prizes, under any name, since it may constitute gambling or the organisation of gambling under Articles 321-322 of Bộ luật Hình sự (the Penal Code); no conversion of virtual coins into money; no charitable fundraising through the Server) are set out in Article 10.2, Article 4.4 and the Framework Rules for Events; no one - including the Owner - may approve an exception, and every proposal of this kind must be refused at the idea stage.

### Article 26. Offline events

26.1. An "official offline event" is an event confirmed in writing by the operations board, with a designated person in charge, and applying the event code of conduct (including the special rules where persons under 18 attend). Only such events fall within the Server's organisational responsibility.

26.2. Any other meet-up organised by Members is a private activity; using the Server's name, logo or standing for an event that has not been officially confirmed is prohibited. Misuse of the Server's name shall be dealt with under the CoC. The Server is not responsible for spontaneous events, but conduct at a spontaneous event aimed at a Member because of their membership - or at a spontaneous event trading on the Server's name - may still be dealt with under the exceptions in Article 23.3.

---

## CHAPTER VI - TERMINATION OF MEMBERSHIP

### Article 27. Termination, consequences and appeals

27.1. Self-termination: a Member may leave the Server at any time, without reason and without notice. Data rights after leaving shall be exercised under Article 22.

27.2. Termination by the Server: the Server terminates membership (ban) or applies restrictive measures strictly within the framework and procedure of the CoC and ENF; the sanction ladder gives priority to allowing the violator to put matters right; the detail of the ladder, limitation periods and Red-tier sanctions is canon content of ENF. The applicable principle admits of no exception: every measure must be documented (the provision relied on, the evidence, the decision-maker, the time) before or within the prescribed period; an undocumented measure shall be void on appeal.

27.3. Interim protective measures (freeze, isolation, protective ban pending verification) are not a finding of fault and shall always be described as interim when announced. Applying an interim measure in the face of a serious allegation (particularly one involving child safety) is mandatory under the SOP and is not contingent on sympathies. Where the community presses for an immediate finding, the Team shall apply interim measures only; crowd pressure does not shorten the process leading to a finding.

27.4. Consequences of termination: when membership ends (whether by leaving or by ban): all roles, levels, coins or points, badges and access rights end with it and are not compensated (Article 10); donations already given are not refunded (Article 25.1, save for 25.4); obligations already accrued (confidentiality as to internal information and handover of operational assets by former Staff under Article 11.5, and responsibility for conduct already carried out) survive termination.

27.5. One-stop appeals: every appeal against a measure shall be received only through the [Single-Window Channel](https://discord.com/channels/1342729473245577267/1343099398720065559) or - where the appellant no longer has access to the Single-Window Channel - by email to [support@donquaan.com](mailto:support@donquaan.com) (Article 6.1(d)); appeals shall be resolved by a person who is not the decision-maker and who has no conflict of interest (Article 5.8), within the published time limits: 72 hours for minor measures, 7 days for serious measures. Where the Team is too thin to provide an eligible person, the matter shall be escalated to the Owner or to an unconnected designated person. Staff are prohibited from discussing a case by DM; the only valid reply outside the Single-Window Channel is a direction to the Single-Window Channel. A Member's sending of an appeal to several channels shall not be treated as an aggravating circumstance; an appeal sent outside the valid intake channels has no intake effect. The detailed procedure is in APL.

27.6. Consequences where an appeal succeeds: where the measure is annulled, the record shall be expunged, a corrective notice shall be posted wherever the measure was announced, together with an apology using the standard template. This applies even where the decision-maker was the Owner: a measure taken directly by the Owner takes immediate effect and is documented in full like any other measure; the Member enjoys the full right to appeal it under Article 27.5, the appeal is resolved by a person with no conflict of interest, and the outcome of that appeal binds the Owner as well.

27.7. A decision of permanent termination may be reconsidered only through an amnesty procedure with published criteria (time elapsed, conduct, voluntary disclosure) set out in the CoC and ENF - not through crowd campaigning and not through personal connections. Exception: Red-tier sanctions (the especially serious category of violations under ENF - for example serious doxxing, threats, and any conduct involving harm to minors) are not eligible for amnesty.

27.8. Ban evasion: returning under another account while a measure is in force (for a permanent ban: at any time before amnesty; for a Red-tier sanction: permanently) is a standalone violation; an alternate account of a person under permanent ban shall itself be permanently banned once discovered, or reported and verified to the evidentiary standard. A finding identifying a ban-evading account must meet the evidentiary standard in Article 5.7(e) and the CoC. A person who voluntarily discloses may access the amnesty procedure in 27.7 (save for Red-tier sanctions).

27.9. No retaliation: any detrimental act aimed at an appellant, a good-faith reporter, or a person who provides evidence is strictly prohibited - from anyone, including Staff and the Owner. Retaliation is a standalone violation, more serious than the underlying one. A report that the reporter knows to be false is not a good-faith report and shall be dealt with under Article 5.7(d) or the false-accusation framework of the CoC; a report that is wrong but made in good faith shall not be sanctioned.

27.10. Systematic baiting: deliberate, sustained provocation designed to induce another person to breach the rules and then to exploit their reaction is a standalone violation by the provoker, at a serious tier; for the person baited, the context of systematic provocation is a circumstance that must be considered in setting the tier (mitigation or exemption under the CoC) - but it does not automatically excuse all responsibility.

27.11. Discretion and traceability in handling: every working session concerning a violation or an appeal shall by default be conducted in writing, in a channel that retains a trace (voice shall not be used for disciplinary work); announcement of a measure (if announced) shall follow the standard template, shall not include humiliating detail about the person sanctioned, and the same degree of discretion shall apply to every Member under Article 5.3. Recording or disseminating a handling session without the consent of the parties is strictly prohibited; doing so is a standalone violation.

### Article 28. Closure, suspension or transformation of the Server

28.1. The Owner may suspend, restructure or close the Server. Save in a case of force majeure or a legal requirement, permanent closure shall be announced at least 30 days in advance on the Official Channels, together with guidance on data and on funds (if any) under the relevant instruments.

28.2. Suspension or disruption of the Server by Discord does not depend on the Owner's will; in that event, the only authenticated information shall be issued through the remaining Official Channels (Article 6.1), and Members are advised not to trust any regrouping link outside those channels.

### Article 29. Succession and delegation of operations

29.1. The Owner shall maintain a peacetime instrument of delegation, in which the identity or title of the delegate is announced in advance to the Team (and to the community to an appropriate extent). Where the Owner is unreachable for more than 72 consecutive hours through every official channel in a situation requiring a decision, interim operational authority may be given only to: (i) Staff at Head Admin level or above, or (ii) a person holding a still-valid written confirmation from the Owner. The scope of delegation is in every case the authority of a Head Admin, is interim, may not be exceeded, and excludes: transfer of ownership; dissolution; any decision on expenditure or cash flow (spending is possible only under the Owner's written, item-specific advance authorisation - Article 25.3); amendment of the Community Legal Framework; and statements accepting legal liability. The person taking up interim operations must announce that fact in the [official announcement channel](https://discord.com/channels/1342729473245577267/1529782982016110642) (Article 6.1(h)) and document it under Article 5.5; interim authority ends the moment the Owner re-establishes contact through an Official Channel.

29.2. The long-term succession scenario (force majeure affecting the Owner) shall be carried out under the succession document prepared by the Owner and lodged with a trusted person; the community shall verify every handover announcement by cross-posting on the Official Channels, and in particular on the website in Article 6.1(b).

29.3. No individual - including a delegate - may use the period of delegation to amend the Community Legal Framework in a relaxing direction, to alter the ownership structure, or to handle files concerning themselves.

---

## CHAPTER VII - AMENDMENT OF THE TERMS, EFFECT, FINAL PROVISIONS

### Article 30. Countering impersonation, fabrication and distortion - on the footing that the Owner is bound by the rules

30.1. This Article establishes objective reference points for identifying impersonating, fabricated or distorting content aimed at the Server or the Owner. It confers on the Owner no authority to act against criticism (Article 30.4).

30.2. The following baseline declarations serve as permanent reference points: (a) the list of Official Channels in Article 6.1; (b) the No-Money-Request Principle in Article 6.3; (c) every official statement by the Owner in the name of the Server appears only on an Official Channel. Any content contradicting these three declarations (message, image, audio, video - including material that looks or sounds genuine) is by default not from the Server or the Owner.

30.3. Fabricating evidence, forging the identity of the Owner or of Staff, and disseminating harmful edited material shall be dealt with at the most serious tier of the CoC (Article 5.7(d)), and the Server reserves the right to report the matter to the platform and to the authorities under the law on fake news and defamation - irrespective of whether any accompanying allegation has been answered.

30.4. Mandatory boundary: criticism, questioning and good-faith doubt about the Server or the Owner - including in harsh terms - is not a violation and shall not be dealt with under this Article. The standard sequence is: (a) legitimate questions (for example about data, or about money) are answered publicly; (b) on a first false assertion, the Server answers publicly and requests a correction - no action is taken; (c) action is taken only where the person maintains or repeats a fabricated assertion after an official answer already exists, or where the conduct involved fabrication or deceptive editing from the outset (dealt with under 30.3 without waiting for an answer). The Server shall not organise a counter-offensive in public opinion in any circumstances (calling for reviews, organised mass reporting, mobilising members to attack the accuser personally).

30.5. Allegations against the Owner: these shall be received through the private flow of the [Single-Window Channel](https://discord.com/channels/1342729473245577267/1343099398720065559) (Article 6.1(c)) or the confidential whistleblowing email address [private@donquaan.com](mailto:private@donquaan.com) (anonymous submissions accepted); the file shall be managed and handled by a Head Admin together with an independent responsible person (who is not chosen by the Owner for that case). Throughout: the Owner stands outside the file - no access to the file, no private contact with the reporter, and no participation in any stage of assessment (Article 5.2); the reporter's identity shall be protected to the highest feasible degree; public statements (if required) shall follow the principle-preserving template of the crisis SOP, neither confirming nor denying before a finding exists. Allegations bearing signs of a criminal offence shall be directed to the authorities under Article 13.7. The full regime on the Owner's constraints is in OWN.

### Article 31. Amendment of the Terms

31.1. The Owner may amend the Community Legal Framework. Every amendment must: (a) be announced publicly on the Official Channels together with a summary of changes; (b) carry a version number and an effective date; (c) preserve all previous versions for comparison.

31.2. Notice period: an ordinary (minor) amendment takes effect no earlier than 7 days after announcement; a major amendment - one affecting Members' rights - takes effect no earlier than 30 days after announcement. Exceptions taking effect upon announcement: amendments required in order to comply with the law or with the Discord Terms of Service and Community Guidelines, and emergency amendments for member safety - in which case the emergency reason must be stated in the announcement.

31.3. Non-retroactivity (Article 5.4): an amendment applies only to conduct occurring from its effective date onwards.

31.4. Continued participation in the Server after the effective date of an amendment shall be deemed acceptance of that amendment (Article 7.2). A Member who does not agree may leave the Server; leaving does not extinguish data rights under Article 22.

31.5. One-way ratchet for protective provisions: the Owner's self-binding commitments (Article 5.2, Article 27.6, Article 30.4, Article 30.5) and the no-exception safety red lines (Article 6.3, Article 8.3(e), Article 8.5, Article 10.2, Article 13.3, Article 25.5) may be amended only in a stronger or clearer direction; any amendment relaxing them must be announced prominently, justified publicly, and may take effect no earlier than 30 days afterwards (the major-amendment framework in Article 31.2).

### Article 32. Effect and interpretation

32.1. These Terms take effect on the date stated in the document control block and apply to every Member, including those who joined before the effective date (from the effective date onwards, subject to the minimum interval between the announcement date and the effective date under Article 31.2).

32.2. Severability: if any provision is declared void or unenforceable by a competent authority, the remaining provisions retain full force; the void provision shall be replaced by the lawful provision closest to its original purpose.

32.3. No waiver: the fact that the Server has not enforced, or does not enforce, a provision in a particular case does not mean that it waives the right to enforce that provision later; at the same time, under Article 5.3, enforcement must be consistent - systematically selective enforcement (systematically applying the highest tier to one person while merely warning another for the same conduct) is a violation by the enforcer, detected through the central sanctions log and periodic cross-audit under the CoC.

32.4. Language: the Vietnamese version is the authoritative text; any translation is for reference only.

32.5. Gaps and unforeseen situations: a situation for which no provision exists shall be handled under the principles in Article 5 and the order of precedence in Article 1.3, after which the instrument must be supplemented for the future. A gap shall not be used to impose retroactive sanctions.

32.6. Right to correct published errors: an obvious error in a Server notice or publication (a typographical error as to a figure, a value or a time) shall be corrected publicly at the earliest opportunity together with an acknowledgement of the error; a publication that is wrong through obvious error creates no commitment according to its erroneous content. The right of correction may not be used to withdraw a commitment that correctly expressed the original intention.

32.7. Governing law and dispute resolution: these Terms are governed by the law of Vietnam. A dispute between a Member and the Server or the Owner shall first be addressed through the [Single-Window Channel](https://discord.com/channels/1342729473245577267/1343099398720065559) and good-faith negotiation; failing that, the parties may bring the matter before the competent Vietnamese authorities in accordance with the law.

### Article 33. Provisions suspended pending a legal entity

33.1. The following activities are Suspended - and may not be implemented - until the Server has an appropriate legal entity and the instruments have been reviewed by a lawyer: paying remuneration or sharing income with Staff in any form; charging a fee for participation in any activity; commercial-scale sponsorship arrangements; promotional programmes tied to paid goods or services; and every other component marked Suspended in the related instruments. No Staff member - and no vote result - may activate a Suspended item (Article 5.10(c)).

33.2. When a legal entity is established and takes over operations: the entire Community Legal Framework shall be reviewed and reissued in the name of that entity; cash flow shall move to the entity's account; and Suspended items may be opened only by a publicly announced decision. Members shall be notified through the amendment mechanism in Article 31.

### Article 34. Final acknowledgement

34.1. By clicking to accept on joining, or by continuing to be active in the Server, a Member confirms that: they satisfy the conditions in Article 8; they have read, understood and accepted these Terms in full together with the instruments listed in Article 1.2; and they understand that the Server is a volunteer community operating according to the order of priority in Article 5.6, applied uniformly to every Member including the Owner.

34.2. Any question about these Terms shall be sent through the [Single-Window Channel](https://discord.com/channels/1342729473245577267/1343099398720065559) (Article 6.1(c) - recommended first choice) or by email to [support@donquaan.com](mailto:support@donquaan.com), following the submission standard in Article 6.9.

34.3. The operating record is the reference record. The Server maintains an operating record comprising system logs, case files, copies of official announcements and copies of the successive versions of the instruments in the Community Legal Framework, for the retention periods laid down in the Privacy Policy §14. Where there is a dispute as to what happened, the Server's operating record is the reference record against which the parties check. a) The reference record is not conclusive evidence. A Member may adduce evidence to the contrary; where a Member points to indications that the record has been altered, truncated or is missing the relevant passage, that part of the record loses its value as a reference until the Server establishes its integrity; b) A Member may request an extract of the part of the record that directly concerns them through the [Single-Window Channel](https://discord.com/channels/1342729473245577267/1343099398720065559), once per case, free of charge. The Server shall provide it within 07 working days, with third-party data redacted under the Privacy Policy §14.2; c) The Server shall not destroy, alter or allow the loss of any part of the record that is the subject of an open appeal, or of a matter of which the Server has been notified in writing that it will be taken outside. A breach of this point deprives the record of all reference value in that matter.

34.4. Exhaustion of the internal procedure before taking a matter outside. Before taking a matter arising in the Server to a third party, including a complaint to the Discord platform, a report to a competent authority, publication in the media or the commencement of proceedings, a Member shall exhaust the appeal procedure laid down in the Appeals Regulation (cite code APL), running from the time the Member knew or ought to have known of the matter. a) This Article does NOT restrict, and shall not be read as restricting, a Member's right to bring proceedings, to make a denunciation or to approach a competent authority. Any reading to the contrary is void and shall not be relied upon by the Server; b) It does not apply, that is to say the Member may go outside directly, in three cases: where there is a risk to human safety or life; where the conduct bears the indicia of a criminal offence; or where a limitation period under the law is about to expire and awaiting the internal procedure would extinguish the Member's right; c) The Server binds itself to a time limit: if the Server does not answer a valid appeal within the time limit in APL §26, the Member is deemed to have exhausted the internal procedure and need wait no longer; d) The sole consequence of bypassing the internal procedure is that the Server may refer to that fact when presenting the matter, and costs incurred by reason of the bypass shall not be borne by the Server. There is no other consequence, and the Server shall not rely on it as a ground for sanctioning the Member.

---

## List of related instruments (by reference)

The following instruments are issued together with the Community Legal Framework and fall outside the scope of this instrument: [CoC - Code of Conduct](https://donquaan.com/discord/rules); [ENF - Enforcement and Sanctions Regulation](https://donquaan.com/discord/rules/enforcement); [APL - Appeals Regulation](https://donquaan.com/discord/rules/appeals); [DIS - Disclaimer of Liability](https://donquaan.com/discord/disclaimer); [PRV - Privacy Policy](https://donquaan.com/discord/privacy); [STF - Staff Rules](https://donquaan.com/discord/rules/staff); [OWN - Owner Charter](https://donquaan.com/discord/rules/owner); [ANX-1 - Annex on Prohibited Keywords](https://donquaan.com/discord/rules/banned-words); [ANX-2 - Annex on Identity Verification](https://donquaan.com/discord/verify); [ANX-3 - Annex on Donations](https://donquaan.com/discord/donate); the Framework Rules for Events and Giveaways; the safety SOPs (self-harm, child safety, emergency takedown, communications crisis, loss of Discord or loss of the Owner account) and the Emergency Action Card. Content relating to life, to legal matters and to children may be promulgated only after approval by a suitably qualified professional.

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