Skip to content
Log inAdd to Discord
Menu

Draft, pending legal review. Unpublished until a lawyer has reviewed this page and C.B. approves it in writing. The text is the v2 draft and is not a public policy yet.

Terms of Service

Effective date: [date] · Last updated: [date] ·

Effective date: [Effective date] Last updated: [Last updated date] Website: {{DOMAIN}}

1. Agreement to these Terms

These Terms of Service ("Terms") are an agreement between you and {{LEGAL_NAME}} ("we," "us," or "our"), the operator of GuildMarshal. GuildMarshal includes the GuildMarshal Discord bot (the "Bot") and the GuildMarshal officer website (the "Website"), together the "Service." The Website is for guild Officers, GMs, and GuildMarshal Admins. Members use the Service through the Bot in Discord.

By adding the Bot to a Discord server, signing in to the Website, using a GuildMarshal command, or otherwise using the Service, you agree to these Terms and to our Privacy Policy. If you do not agree, do not use the Service.

If you use the Service on behalf of a guild or other group, you confirm that you have the authority to accept these Terms for that group. [COUNSEL REVIEW — whether a guild, which is usually an informal group, can be bound this way, or whether each officer accepts individually.]

2. Eligibility and minimum age

You must be at least 13 years old, or the minimum age required in your country to use online services without parental consent if that age is higher (for example, up to 16 in some countries in the European Economic Area) [VERIFY / COUNSEL REVIEW]. You must also meet the minimum age set by Discord and by the publisher of any game you use the Service for.

If you are under the age of majority where you live, you may use the Service only with the involvement of a parent or legal guardian who agrees to these Terms. A paid subscription may only be bought by an adult or with a parent's or guardian's consent. [COUNSEL REVIEW]

We may suspend or delete accounts that we reasonably believe belong to someone under the minimum age.

3. What the Service does

GuildMarshal helps online game guilds organize on Discord. It currently supports World of Warcraft. We may add other games, and when we do, these Terms apply to them too (see Section 7 for game-specific rules). In its current version, the Service lets guilds:

  • link Discord server roles to GuildMarshal permission levels (Member, Officer, and GM);
  • keep character lists and raid rosters;
  • create raid events and collect signups;
  • record attendance, including voice-channel presence when an officer takes attendance (see Section 11);
  • assign members to roster positions;
  • manage soft reserves and wishlists;
  • record loot council decisions and loot history (the Service does not run a DKP system);
  • keep an append-only audit log of officer actions; and
  • let Officers and GMs export attendance records as CSV files.

Members use the Bot's Discord commands to sign up, manage their characters, and control their data. The Website is only for Officers, GMs, and GuildMarshal Admins.

Features may change, be added, or be removed. Section 10 explains what happens if we remove a major paid feature. [C.B. DECIDE — whether to label the Service "beta" or "early access" in the product itself.]

4. Your Discord account and sign-in

Officers, GMs, and GuildMarshal Admins sign in to the Website with their Discord account through Discord OAuth. We ask Discord only for the identify, guilds, and guilds.members.read scopes. We do not receive or store your Discord password. Members don't sign in to the Website. If a member tries, they are turned away and no session is created.

You are responsible for your Discord account's security and for activity that happens through it. If you think someone has accessed GuildMarshal through your account without permission, tell us at {{CONTACT_EMAIL}} and secure your Discord account. Signed-in Website sessions last 7 days. Activity on the Website extends a session back to 7 days, at most once an hour. You can log out of every session at once from the Website.

Your GuildMarshal permission level in a guild (Member, Officer, or GM) comes from the Discord roles that guild's leaders have mapped in GuildMarshal. If your Discord roles change, your GuildMarshal access may change too.

5. Adding the Bot to a Discord server

Only someone with the Discord permissions needed to add a bot to a server may add the Bot. The Bot asks for a limited set of permissions and does not ask for Administrator or Manage Roles. It uses only the Discord Guilds and GuildVoiceStates gateway intents. It does not request message content or the privileged server-members intent. [VERIFY — confirm the final permission list and intents before publication.]

Whoever adds the Bot, and the guild's GM and Officers, are responsible for:

  • deciding to use GuildMarshal for their guild;
  • setting up role mappings correctly;
  • telling guild members that GuildMarshal is in use, including that voice-channel presence is recorded when attendance is taken (the Service also shows its own notice; see Section 11); and
  • following Discord's rules for server owners and moderators.

You can remove the Bot from your server at any time through Discord. Section 10B explains what happens to guild data after removal.

6. Guild Officers and GMs

Guild data in GuildMarshal (rosters, events, signups, attendance, assignments, soft reserves, wishlists, loot decisions, loot history, officer notes, and the audit log) is created and managed by each guild's Officers and GMs. For that data:

  • Officers and GMs decide what is recorded about their members and how it is used inside their guild.
  • Officers and GMs are responsible for using the data fairly and lawfully, including any attendance CSV they export. Once a file is exported, it is outside GuildMarshal and outside our control.
  • We provide the tools and process guild data on the guild's behalf, under these Terms and the Privacy Policy.
  • Paying doesn't change this. The guild's payer (Section 10) gets no extra rights over other members' data.

[COUNSEL REVIEW — FLAG: This section treats guild Officers/GMs as the "controller" (or "business") of their own guild data and the Operator as a "processor" (or "service provider"). Counsel should decide (a) whether this split holds up when guilds are informal, unincorporated groups of individuals; (b) whether the "household/personal activity" exemption under GDPR could apply to guilds; (c) whether a data processing addendum is needed; and (d) how member rights requests are routed between the guild and the Operator.]

Officers and GMs must not use GuildMarshal to harass, shame, or discriminate against guild members, including through loot decisions, attendance records, officer notes, or audit log entries.

7. Discord, game publishers, and other third parties

Not affiliated. GuildMarshal is an independent project. World of Warcraft is a trademark of Blizzard Entertainment. GuildMarshal is not affiliated with or endorsed by Blizzard. GuildMarshal is also not affiliated with, endorsed by, or sponsored by Discord Inc. Discord is a trademark of Discord Inc. When we add support for another game, we will add a matching notice for that game's publisher. Other names are the property of their owners. [COUNSEL REVIEW — trademark notice wording and any Blizzard fan-content or API terms that apply.]

Their rules still apply. When you use GuildMarshal you must keep following:

  • Discord's Terms of Service, Community Guidelines, and Developer Terms of Service and Developer Policy, as they apply to you; and
  • the end user license agreement, terms of use, and community policies of the publisher of each game you use GuildMarshal for. For World of Warcraft, that means Blizzard's.

Nothing in GuildMarshal permits anything those rules prohibit. GuildMarshal does not interact with any game client and is not a game modification, automation tool, or "bot" inside any game. [VERIFY]

Third-party availability. The Service depends on Discord and, for payments, on our payment provider. If those providers change their platforms, limit our access, or have an outage, parts of the Service may stop working (see Section 12).

8. Acceptable use

You agree not to:

  1. break any law or any rule described in Section 7;
  2. use the Service to harass, threaten, dox, or abuse anyone;
  3. post or store content that is unlawful, hateful, sexually explicit involving minors, or that infringes someone else's rights;
  4. collect or store other people's personal data in GuildMarshal beyond what guild organization needs (for example, no legal names, home addresses, contact details, or sensitive personal information in free-text fields or officer notes);
  5. try to access guilds, data, or accounts you are not authorized to access, including by abusing role mappings;
  6. probe, scan, or test the Service's security without our written permission [C.B. DECIDE — whether to offer a responsible-disclosure contact];
  7. disrupt, overload, or interfere with the Service or Discord;
  8. scrape, copy, or resell the Service or its data, or reverse engineer it except where the law allows; or
  9. use the Service for real-money trading of in-game items or currency, or for selling game accounts or services that a game publisher's policies prohibit.

We may remove content, limit features, or suspend access if we reasonably believe you have broken this Section.

8A. Reporting content and takedowns

If you believe content in GuildMarshal is unlawful, infringes your rights (including copyright), or breaks these Terms, email {{CONTACT_EMAIL}} with a description of the content, the guild or server it is in, and why you are reporting it. We may remove or restrict content, or limit an account or guild's access, when we receive a valid legal complaint, an intellectual-property notice, or an order from a public authority, or when content puts people or the Service at risk. Where reasonable, we will tell the affected guild or user what we did and why, and give them a way to respond. [COUNSEL REVIEW — designated DMCA agent if hosted in or serving the U.S.; EU Digital Services Act notice-and-action requirements.]

9. Your content and guild data

"Content" means anything you or your guild put into the Service, such as character names, event notes, signup comments, wishlists, loot notes, officer notes, and role settings.

You keep whatever rights you have in your Content. You give us a non-exclusive, worldwide, royalty-free permission to host, store, copy, process, and display your Content only as needed to run, secure, and improve the Service and as described in the Privacy Policy. This permission ends when the Content is deleted from the Service, except for copies kept for the periods described in Sections 10A and 10B and in the Privacy Policy (for example, backups and legal holds). [COUNSEL REVIEW]

You confirm that you have the right to put your Content into the Service.

9A. Our license to you

While you follow these Terms, we give you a limited, personal, non-exclusive, non-transferable, revocable right to use the Service for organizing your guild. The Bot, the Website, and their software, design, and branding belong to us or our licensors. These Terms don't give you any ownership of them. This right ends when your access ends under Section 13.

10. Fees, subscriptions, and payment

[C.B. DECIDE — prices, plan limits, and launch date. Billing isn't built yet. Until it launches, the Service is free and no one is billed.]

One subscription per guild. Paid plans are sold per guild. Each paid plan covers one Discord server and the guild that uses it. It can't be moved to another server, split between servers, shared, or resold.

One named payer. Each paid guild has one named payer. The payer agrees to the price, is responsible for all charges, and is the only person who can upgrade, downgrade, or cancel the plan. If the payer leaves the guild or wants to hand billing over, the guild's GM can ask us to move the payer role to another eligible guild member. That person must accept these Terms and set up their own payment method. Until the handover is complete, the existing payer stays responsible for charges.

Free and promotional access. We may give some guilds free or discounted access, including promotional, trial or partner access. It can be for a set period or with no end date, at our discretion. That access belongs to the guild and can't be transferred. If we end access that has no end date, we'll give at least [30] days' notice, and the guild can then subscribe or move to the free plan. Free and promotional guilds follow the inactivity rules in Section 10B.

How payments work. Payments are handled by Discord, through its in-app purchases, or by [payment processor]. Their terms also apply to your purchase. We never receive or store your full card details. We only receive confirmation that a payment went through. Prices and any taxes are shown before you buy. The payer gets a receipt from the payment provider. [COUNSEL REVIEW — Discord monetization and developer policy requirements.]

Auto-renewal. Paid plans renew automatically at the end of each billing period, for the same length of period, at the price in effect at renewal, until the payer cancels. We show the renewal date and price before purchase and in [billing settings]. We send a reminder before each annual renewal [and before a monthly renewal after any price change]. If prices change, we give at least [30] days' notice before the new price applies to your next renewal. The payer can cancel any time to stop the next renewal. [COUNSEL REVIEW — U.S. state automatic-renewal laws and EU/UK consumer rules.]

Failed payments and chargebacks. If a renewal payment fails, we tell the payer and retry for [7] days. If payment still fails, or if a payment is reversed or charged back, paid features stop and the guild becomes read-only under the same timeline as a cancellation (Section 10A). Paying the balance restores full access. We may suspend accounts involved in repeated fraudulent chargebacks.

EU/UK 14-day withdrawal right. If you are a consumer in the European Union or the United Kingdom, you can withdraw from a purchase within 14 days, without giving a reason, by telling us at {{CONTACT_EMAIL}} or using [withdrawal form link]. If you ask us to start your paid plan straight away, you agree that if you withdraw, you pay for the part of the service already provided. Where the law allows, you lose the right to withdraw once the service has been fully provided. [COUNSEL REVIEW — required wording and model withdrawal form.]

Refunds. Except where the law (including the withdrawal right above) or the payment provider's rules say otherwise, payments are not refundable, and we don't refund partial billing periods when you cancel. If you bought through Discord, Discord's refund rules also apply. [C.B. DECIDE — optional goodwill refund window, e.g., 7 days for a first purchase.]

If we remove a major paid feature. We may improve or change features. If we remove a major paid feature during your billing period, the payer may cancel and get a pro-rated refund for the unused part of that period.

10A. Cancellation and the read-only period

When a paid plan ends, because the payer cancels or because of non-payment (Section 10):

  1. The plan stays fully active until the end of the period already paid for.
  2. Then the guild becomes read-only for 90 days. Officers can view and export data but can't make changes. Members can still use /privacy.
  3. We send the payer a Discord direct message around day 60 and day 83 of the read-only period.
  4. On day 90, the guild's data is deleted from the live Service.
  5. The host expires backup copies within 30 days after that.

Resubscribing during the 90 days restores full access with data intact. If the guild qualifies for the free plan, it moves to the free plan instead of becoming read-only. [C.B. DECIDE — confirm the free-plan fallback.]

10B. Data retention and deletion

Retention is fixed by GuildMarshal policy. The periods in this Section and in the Privacy Policy apply to every guild. Officers, GMs, and server owners can't change, lengthen, or turn them off.

Bot removed. If the Bot is removed from the server, guild data stays available for 90 days. It is then hidden, not erased. It is permanently deleted 30 days after it is hidden. Re-adding the Bot during those 30 hidden days restores the data. Re-adding the Bot during the first 90 days keeps the data available. There is no separate control that deletes the guild immediately. The host expires backup copies within 30 days after permanent deletion.

Inactive guilds. This applies to every guild, including free and promotional guilds.

  • A guild is inactive when, for 180 days, there have been no officer-plus Website logins (Officer, GM, or GuildMarshal Admin), no slash commands or button presses on the Bot, and no event signups. Voice attendance snapshots and automatic posts by the scheduler do not count as activity.
  • At day 150 and day 173 of inactivity, we send a warning Discord direct message to the guild's GM(s). If no GM role is mapped, it goes to the Discord server owner.
  • At day 180, the guild becomes read-only.
  • If an officer logs in to the Website, or anyone uses a Bot command, during days 180–210, the guild is reactivated automatically.
  • At day 210, the guild's data is permanently deleted. The host expires backup copies within 30 days after that.

Members who leave. When a member leaves the guild, their data is anonymized 90 days after they leave.

History. Attendance and signup records older than 12 months are anonymized. Guild totals stay accurate.

Sessions and refused logins. Website sessions last 7 days. Activity extends a session back to 7 days, at most once an hour. Expired Website sessions are deleted 1 day after they expire. Records of refused login attempts are deleted after 30 days.

Audit log. To keep a reliable record of officer actions, the audit log is append-only. Entries are not deleted when other data is. Instead, the Discord IDs in audit log entries are anonymized after 24 months, and immediately when a member uses /privacy delete. Anonymized entries may be kept after the rest of a guild's data is deleted. [COUNSEL REVIEW — confirm that keeping anonymized audit entries is consistent with the deletion commitments.]

The Privacy Policy explains in detail what we keep and for how long. If the Privacy Policy and this Section ever disagree, the shorter retention period applies. [COUNSEL REVIEW]

11. Privacy, member data controls, and voice attendance

Our Privacy Policy explains what data we collect, how we use it, how long we keep it, and how to request deletion. By using the Service you confirm you have read it.

Member controls in Discord. Any member can use these Bot commands:

  • /privacy export to get a copy of their own GuildMarshal data, sent privately to them;
  • /privacy delete to have their data anonymized (the default) or fully erased. It always asks for confirmation first; and
  • /privacy opt-out to keep their name off member-visible lists, Discord roster posts, and signup posts. Opting out does not stop attendance recording. The member still counts in attendance totals, and Officers, GMs, and the Discord server owner still see their Discord name and character name marked "Opted out" in on-screen officer views. Officer-only exports (export summaries and both CSVs) leave out the Discord name and Discord ID and show only the character name with opted_out = yes. GuildMarshal stores the opt-out flag to enforce it, and the member can check and reverse their own status at any time. To stop recording entirely, the member can use /privacy delete, or, in the EU/UK, object under GDPR Article 21 as described in the Privacy Policy.

Officers, GMs, and GuildMarshal Admins can carry out a deletion for a member who asks.

Voice attendance. When an Officer takes attendance, GuildMarshal records which members are in the guild's voice channel at that moment. It does not record, listen to, or store any audio. The channel sees a one-line notice that attendance was recorded. Each member sees a one-time notice explaining attendance tracking the first time they link a character, and officers see it the first time they sign in. Members can use /privacy opt-out at any time.

12. Availability, maintenance, and shutdown

Before launch. Until we announce general availability, the Service is in early access, and we may need to reset data. We'll give at least [7] days' notice of any planned reset through the channels in Section 20A, so officers can export what they need. After general availability, we keep and delete data only as described in Sections 10A, 10B, and the Privacy Policy.

Maintenance. We may interrupt the Service for maintenance or updates. We announce planned maintenance in advance where reasonably possible and try to schedule it outside common raid times.

Outages. The Service depends on Discord and other providers. We are not responsible for outages or changes caused by Discord, our hosting or payment providers, or events beyond our reasonable control. We will work to restore service promptly. [C.B. DECIDE — whether to offer service credits for long outages on paid plans.]

Changes and shutdown. We may change, suspend, or stop parts of the Service. If we plan to shut down the Service entirely, we'll give at least 30 days' notice so guilds can export their data, and we'll refund prepaid fees for any period after the shutdown date.

13. Suspension and termination

By you. You can stop using the Service at any time. Officers and GMs can log out of the Website and revoke GuildMarshal's access in their Discord settings (Authorized Apps). Members can stop using the Bot's commands and use /privacy delete. Server owners and admins can remove the Bot from their server. Removing the Bot does not cancel a paid plan; the payer must cancel it (Section 10). What happens to data afterward is described in Sections 10A and 10B.

By us. We may suspend or end your access, or a guild's access, if you break these Terms, if a payment fails or is charged back (Section 10), if the law requires it, if Discord or a game publisher requires it, or if continuing would create risk or harm to others or to us. Where reasonable, we will tell you why and give you a chance to fix the problem or export your data. If we end a paid plan without cause, we refund the unused part of the period.

Sections that by their nature should continue after termination (including Sections 9, 10A, 10B, 14, 15, 16, 17, and 18) continue to apply.

14. Disclaimers

[COUNSEL REVIEW — disclaimer language must be checked against consumer-protection law in each market where the Service is offered. Some jurisdictions (e.g., the EU, UK, and Australia) do not allow some or all of these disclaimers for consumers.]

TO THE FULLEST EXTENT ALLOWED BY LAW, THE SERVICE IS PROVIDED "AS IS" AND "AS AVAILABLE," WITHOUT WARRANTIES OF ANY KIND, WHETHER EXPRESS, IMPLIED, OR STATUTORY, INCLUDING ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND NON-INFRINGEMENT.

We do not promise that the Service will be uninterrupted, error-free, or secure, that data (including attendance, loot history, or audit logs) will be accurate or complete, or that the Service will work with any particular version of Discord or any game.

Loot decisions, attendance standing, and roster spots are decisions made by your guild, not by us. We are not responsible for disputes between guild members or between guilds.

15. Limitation of liability

[COUNSEL REVIEW — cap amount, carve-outs, and enforceability must be decided by counsel. Most jurisdictions do not allow limiting liability for death or personal injury caused by negligence, fraud, or gross negligence/willful misconduct, and some limit these clauses for consumers entirely.]

TO THE FULLEST EXTENT ALLOWED BY LAW:

  1. {{LEGAL_NAME}} AND ITS OWNERS, CONTRIBUTORS, AND SUPPLIERS WILL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY, OR PUNITIVE DAMAGES, OR FOR ANY LOSS OF PROFITS, GOODWILL, IN-GAME ITEMS, GUILD STANDING, OR OPPORTUNITY, ARISING OUT OF OR RELATED TO THE SERVICE OR THESE TERMS, EVEN IF WE WERE TOLD SUCH DAMAGES WERE POSSIBLE.
  2. OUR TOTAL LIABILITY FOR ALL CLAIMS RELATED TO THE SERVICE OR THESE TERMS WILL NOT BE MORE THAN THE GREATER OF (A) THE AMOUNT PAID FOR THE AFFECTED GUILD'S PLAN IN THE 12 MONTHS BEFORE THE EVENT GIVING RISE TO THE CLAIM, OR (B) USD $[amount]. FOR GUILDS ON THE FREE PLAN, (B) APPLIES. [COUNSEL REVIEW]
  3. These limits apply to any theory of liability (contract, tort, negligence, strict liability, or otherwise) and even if a limited remedy fails of its essential purpose.

Nothing in these Terms limits liability that cannot be limited under applicable law, limits our obligations under Sections 10A and 10B, or limits any rights you have as a consumer that cannot be waived.

16. Indemnity

[COUNSEL REVIEW — consider whether to keep this for consumer users, or limit it to Officers/GMs and server owners who install the Bot.]

To the extent allowed by law, you agree to defend and hold harmless {{LEGAL_NAME}} from claims, losses, and costs (including reasonable legal fees) arising from your breach of these Terms, your Content, or, if you are an Officer or GM, your guild's use of guild data, including exported CSV files.

17. Governing law and disputes

These Terms are governed by the laws of [governing law / jurisdiction], without regard to conflict-of-laws rules. Any dispute will be resolved in the courts located in [venue / jurisdiction], unless the law of your country of residence gives you the right to bring claims in your local courts or gives you stronger consumer protections.

[COUNSEL REVIEW — choice of law, venue, whether to include an informal-resolution step, arbitration and class-action waiver (U.S.), EU/UK consumer protections that override choice of law, and any required EU online-dispute-resolution information.]

Before filing a claim, please contact us at {{CONTACT_EMAIL}} so we can try to resolve the issue informally (see Section 20A). [C.B. DECIDE — informal resolution period, e.g., 30 days.]

18. Changes to these Terms

We may update these Terms from time to time. When we do, we will change the "Last updated" date above. If a change is material, we will give at least [30] days' notice before it takes effect, through the channels in Section 20A [C.B. DECIDE — notice period, e.g., 14 or 30 days]. Changes apply going forward only. If you keep using the Service after changes take effect, you accept the updated Terms. If you do not agree, stop using the Service and remove the Bot. A payer who does not agree to a material change may cancel and get a pro-rated refund for the unused part of the current period.

19. General

  • Entire agreement. These Terms and the Privacy Policy are the whole agreement between you and us about the Service.
  • Severability. If a court finds part of these Terms unenforceable, the rest stays in effect.
  • No waiver. Not enforcing a provision is not a waiver of it.
  • Assignment. You may not transfer these Terms, or a paid plan, without our consent (except a payer handover under Section 10). We may transfer them in connection with a reorganization, sale, or transfer of the Service, with notice to you. [COUNSEL REVIEW]
  • No third-party beneficiaries, except as stated in these Terms.
  • Language. If these Terms are translated, the English version controls to the extent allowed by law.

20. Contact

{{LEGAL_NAME}} Email: {{CONTACT_EMAIL}} Postal address: [postal address — if required] [COUNSEL REVIEW — some jurisdictions require a physical address or legal notice details] Website: {{DOMAIN}}

20A. Notices and complaints

How we contact you. We send notices about the Service, billing, retention, and changes to these Terms by one or more of: a Discord direct message to the guild's GM and payer, a message from the Bot in the guild's configured channel, or a notice on the Website. Billing receipts come from the payment provider. We do not send marketing messages without giving you a way to opt out.

How you contact us. Send notices, complaints, withdrawal requests, and takedown reports to {{CONTACT_EMAIL}}. Include your Discord username, the server or guild involved, and, for billing issues, your receipt or order details.

Complaint response time. We acknowledge complaints within [5] business days and aim to give a full response within [21] days. This does not affect your right to go to court or to any consumer dispute body available to you.

Open items for this draft (internal — remove before publication)

For counsel

  1. Guild Officers/GMs as controllers of their own guild data; Operator as processor; whether a guild can accept Terms "on behalf of" a group; need for a DPA (Sections 1, 6).
  2. Minimum age wording; minors and paid plans (Section 2).
  3. Auto-renewal disclosures, the EU/UK withdrawal wording and form, refund policy, and Discord monetization rules (Section 10).
  4. Keeping anonymized audit log entries after deletion (Section 10B).
  5. Takedown process: DMCA agent, EU DSA (Section 8A).
  6. Disclaimer of warranties enforceability for consumers by market (Section 14).
  7. Limitation of liability cap and carve-outs (Section 15).
  8. Indemnity — keep, narrow, or drop (Section 16).
  9. Governing law, venue, arbitration/class waiver, consumer overrides (Section 17).
  10. Trademark/non-affiliation wording; Blizzard fan-content or developer terms; Discord Developer Terms obligations (Section 7).

For C.B.

  1. Fill placeholders: {{LEGAL_NAME}}, {{CONTACT_EMAIL}}, [governing law / jurisdiction], [Effective date], [pricing page], [payment processor].
  2. Prices and plan limits; optional goodwill refund window; free-plan fallback after cancellation (Sections 10, 10A).
  3. Pre-launch reset notice period; outage credits (Section 12).
  4. "Beta"/"early access" labelling (Section 3); responsible-disclosure contact (Section 8); Terms-change notice period (Section 18); informal-dispute period (Section 17).

For engineering [VERIFY]

  1. Final Bot permission list and intents; confirm no Message Content or Server Members intent (Section 5).
  2. OAuth scopes, especially guilds.members.read (Section 4).
  3. Soft reserves, wishlists, loot council, loot history: shipped or not (Section 3).
  4. Retention in the cleanup job matches Section 10B and is not editable per guild. The job does not read stored retention_* columns. Bot removal hides guild data 90 days after the Bot is removed and permanently deletes it 30 days later, restoring it if the Bot is re-added during those 30 days. The inactivity rule is built (day 150 and 173 DMs, read-only at 180, reactivation during 180–210, deletion at 210). Not built yet: the cancellation read-only period. Backup expiry is handled by the host, not by the app.
  5. Confirm the Service never interacts with any game client (Section 7).