Review draft. Details marked “to be confirmed” have not been approved.
To be confirmed — DRAFT FOR REVIEW — NOT LEGAL ADVICE. Not effective or approved for publication.
Wardenreach terms of play — draft
To be confirmed — Draft refreshed 16 November 2026 for Task 25, against base 86df71b and the public deletion flow. The planned closed test disables new purchases; optional real receipt verification now exists but must be configured and reviewed before sale. Operator: [DECISION D01 — legal entity, address and support contact]. Effective/version date: [DECISION D15 — insert after approval and lawful presentation/acceptance]. The code does not currently record acceptance of a terms/privacy version; this document does not create that mechanism.
1. Eligibility and your account
To be confirmed — [DECISION D03; LEGAL CHECK D02/D03 — settle permitted ages/countries, capacity to contract and any parent/guardian process before release. No age-verification feature is implemented.]
You can begin with a guest account. Keep your device and account access token safe, and keep any transfer code and password private. Using a transfer code/password on another device replaces the account token and signs the previous token out for future authenticated requests. Do not access or claim someone else's account without permission.
To be confirmed — A guest town can become inaccessible if its token is lost and no recovery method has been set. Support may need to verify ownership before helping. We will not ask you to publish your password, token or real payment details in chat or tickets. [DECISION D08/D20 — approve recovery and ownership-verification procedures; do not promise recovery the code cannot provide.]
2. Permission to play
Proposed clause for review: we give eligible players personal permission to use the game for entertainment, subject to these terms and applicable law. The game, software and our original assets remain protected by the rights of their owners.
To be confirmed — [LEGAL CHECK D14 — confirm ownership/licences, allowed streaming/screenshots, platform EULA requirements and any transfer/resale restrictions. Do not use this draft to remove statutory software rights or claim ownership of players' unrelated material.]
3. Fair play and community conduct
Do not cheat, exploit a bug to obtain rewards, bypass security or limits, impersonate others, steal accounts, harass people, threaten harm, or post unlawful content. Do not share another person's private information without authority. Use support/reporting tools for problems; do not abuse them to flood staff or other players.
Names, chat, map notes, alliance information and player reports are subject to server checks, word filtering and moderation. Reporting or blocking does not guarantee that all copies disappear. Alliance officers have game permissions over lower ranks; that does not give them access to other players' account credentials or private support cases.
To be confirmed — [DECISION D10; LEGAL CHECK D02/D10 — approve detailed community standards, report/appeal channels and any applicable online-safety/moderation duties. The existing filters and bans alone do not establish compliance.]
4. Player content and privacy
You keep the rights you have in your messages and other content. Proposed permission for review: you allow us to store, transmit, display and moderate the content as necessary to operate the features you choose, such as alliance chat or support. This permission is limited to those purposes; it does not create a separate advertising or resale licence.
To be confirmed — [LEGAL CHECK D14 — approve scope, duration, deletion exceptions and third-party rights for this permission.] Public game content may be seen or copied by other players. Do not put sensitive information into a public name or map note. Private messages are stored server-side and are not end-to-end encrypted.
To be confirmed — The privacy policy draft describes current data handling and unresolved choices. Agreeing to terms must not be used as blanket consent to optional analytics. [DECISION D04/D15/D19 — approve the actual notices/choice and acceptance flows.]
5. Game rules, events and virtual goods
The server's validated state decides online game results. Building, research, troop and hero progression, alliances, battles, rankings, VIP and reward passes operate under the current rules and time windows. In-game map positions are fictional. Disconnections can delay displayed changes.
To be confirmed — Virtual resources and items are game benefits, not a bank account or a promise of cash redemption. [LEGAL CHECK D13/D14 — settle any ownership/transfer/value wording and local treatment before real purchases; nothing here overrides consumer remedies.]
To be confirmed — The game includes random hero recruitment with configured weights and a pity counter. [DECISION D03/D13 — review required probability disclosures, age/rating protections and treatment of random rewards in intended markets before monetisation.]
To be confirmed — Timed event passes have free and optional paid tracks, server-controlled points/claims and final chests. Current event-pass code settles earned unclaimed rewards through game mail when the pass ends, on subsequent server processing/access; it is not a promise of instant delivery while the service is offline. Basic daily passes have their own rules. [DECISION D13/D16 — approve clear product/window/missed-claim descriptions and continuity/remedy policy; do not generalise timed-pass expiry behavior to every reward.]
6. Purchases, spending controls and reversals
To be confirmed — The planned closed test has checkout disabled and displays “coming soon”; it does not issue free purchases. Optional Google Play/Apple receipt verification is implemented for a later configured paid release. [DECISION D13/D25 — confirm products, regional prices, store disclosures and remedies before enabling sale.] Do not enter real payment details in our chat, support or web forms.
The server applies a configurable per-player daily spending limit using recorded prices and real UTC days. Refunded/charged-back receipts still count toward the day's gross limit; an admin may set an override. This server-side allowance uses recorded prices and cannot guarantee a platform checkout is prevented before a charge. Already-paid verified orders still need delivery/reconciliation when checkout is paused.
An authorised admin can record one full recorded refund or chargeback, with an audit reason. The server reclaims available fungible goods up to what was granted, revokes related entitlements, withdraws unclaimed linked gifts and flags the account. Buildings, completed progress and free rewards are not rewound. Goods already spent, or gifts already claimed by allies, become recorded unrecovered game quantities. Balances do not go negative, future earnings are not silently garnished and this record is not a monetary debt or permission to charge you. New purchases pause pending staff review; ordinary play continues. Admin review can waive those unrecovered quantities with a reason.
To be confirmed — [LEGAL CHECK D12 — review fairness and notice/appeal requirements for reclaiming fungible goods, gift treatment, limits and account flags before adoption. A chargeback label is not automatic proof of wrongdoing.] Recording a reversal here does not transfer real funds or replace payment-provider/consumer remedies.
To be confirmed — [DECISION D13 — real-money sales, provider receipts, subscriptions/renewal, cancellation, taxes, delivery, refunds and regional store terms require a separate approved implementation and disclosure before launch. Do not insert “all purchases are non-refundable”. Statutory rights are preserved.]
7. Support, suspension and appeals
To be confirmed — Current support endpoints let you open/reply to your own tickets. Staff can read/reply and add internal notes; only admins close tickets. Default limits are three open tickets and five new tickets per UTC day, with up to 200 messages per ticket. Closing does not restore the daily allowance. The public support page supplies the configured contact and a no-app deletion route. [DECISION D01/D20/D25 — verify Claude's game screens and supply monitored contact details and realistic service expectations].
To be confirmed — The server can restrict chat or access for recorded moderation reasons, and pause purchases after a reversal. Proposed process for review: explain material restrictions where appropriate, permit a meaningful human review route and correct mistakes. [DECISION D10/D12/D16 — approve grounds, urgency exceptions, proportionality, notices and appeals; these proposed safeguards are not all implemented.]
8. Changes, outages and ending play
To be confirmed — We may need maintenance or changes to keep the game working. [DECISION D16; LEGAL CHECK D16 — define justified change/closure grounds, notice, ongoing paid commitments and remedies before adopting any right to change or discontinue service. Do not reserve unrestricted cancellation of promised benefits.]
You can stop playing or request account deletion through Settings or the public account deletion page. A Settings code is short-lived and single-use; a no-app request requires independent ownership verification and admin confirmation. Deletion removes the main town but retains the records and copies explained in the privacy draft. Continuing afterwards starts a new guest account. Deletion does not waive applicable rights or automatically resolve a payment dispute. Offline saves/preferences and other people's screenshots are separate.
9. Responsibility and resolving a concern
To be confirmed — Please contact [DECISION D01 — support/privacy contact] about a problem. [DECISION D20 — set complaint escalation and response procedures]. We do not use this draft to exclude responsibility for matters that applicable law does not allow us to exclude, or to remove rights relating to faulty/misdescribed digital content.
To be confirmed — [LEGAL CHECK D17 — counsel must draft any justified liability provisions, governing law, venue, dispute procedure and mandatory regional protections after the operator/markets are known. No mandatory arbitration, class-action waiver, blanket indemnity, broad “as is” exclusion or arbitrary monetary liability cap is adopted by this draft.]
10. Updates and review
To be confirmed — [DECISION D15 — establish version storage, presentation, acceptance where required and proportionate notice of changes. No retroactive agreement is asserted.] Before publication, resolve the consolidated decision register, validate the implementation and replace all marked placeholders with approved text. These terms do not themselves implement missing protections.
Task 12 review addition: fairplay evidence
To be confirmed — The server uses command limits, validation and optional ordered requests, and retains activity/flow evidence for staff review of suspected scripting or coordinated accounts. A flag is not proof and causes no automatic ban. Staff can clear it with an audited reason or use existing reviewed moderation actions. [DECISION D22 / LEGAL CHECK — approve prohibited-conduct wording, reasonable restrictions, accessibility treatment, human decision/appeal process and privacy disclosures before publication.] The current implementation does not collect a general device identifier and cannot reliably establish that accounts share an owner.
Task 23 addition for legal review: integrity and support
To be confirmed — DRAFT FOR REVIEW — NOT LEGAL ADVICE. Optional platform integrity checks help staff review possible modified-app use. Unavailable or failed checks alone do not automatically ban an account, and do not prevent delivery of an already-paid purchase. An integrity result is not proof of human play or ownership. Any enforcement and appeal terms still need the proportionate human-review decisions in D16/D23; this draft grants no unrestricted sanction power.
Players use the existing support-ticket channel. Staff can read and reply, internal staff notes are not displayed in the game's thread, and only administrators can close tickets. No guaranteed response time is added. Data-rights requests and legal disclosure of internal material remain subject to the privacy review, not solely to what this screen displays.