Wardenreach

Review draft. Details marked “to be confirmed” have not been approved.

To be confirmed — DRAFT FOR REVIEW — NOT LEGAL ADVICE. Do not publish as an approved notice.

Wardenreach privacy policy — draft

To be confirmed — Draft refreshed 16 November 2026 for the Task 25 closed test, against base 86df71b and the new public deletion flow. Effective date: [DECISION D01/D15 — insert only after approval]. This describes implemented server capabilities, including features whose native game integration must still be verified. The planned Android closed test disables new purchases; it does not offer free test checkout. It is not a certification of deployed behavior. The code inventory provides evidence and limitations; all D references resolve to the final decision register.

Task 12 addendum for review: the server now uses daily pseudonymous address groups for guest signups, server action times/gaps and validated value-flow metadata, and staff review flags to detect possible abuse. Flags require human review and do not automatically ban an account. Implemented windows are 7 days for signup groups/action observations, 30 days from last evidence for flags, and account lifetime for replay/quota state; audit and backups have separate schedules. These windows/purposes still require decisions D04/D06/D16/D21/D22 before publication. The inventory addendum covers access, export/deletion and limitations; no general device identifier was added.

Who is responsible

To be confirmed — Wardenreach is operated by [DECISION D01 — legal entity, trading name, postal address and privacy contact]. “We” means that operator. [LEGAL CHECK D02 — confirm applicable countries, any representative/data protection officer and relevant regulator before release.]

Information we use and why

If you play offline, your town and progress are saved on your device. Sound, graphics, language, notification choices, chat-read markers and the usage-reporting setting are also saved locally. Clearing the current online account does not clear these separate local files/preferences.

When you play online, we create a random account identifier and an access token so you can resume your town. Your device keeps the token; the server stores its hash. We keep town progress, resources, buildings, heroes, troops, research, tasks, rewards, game purchases and activity times to run the game and apply its rules. We also keep game-map locations and combat/gathering information. These coordinates describe the fictional kingdom, not your physical location.

If you set a transfer password, we keep a salted password hash and transfer code, with failed-attempt/lock information. Development account linking can send a device-derived test identifier, but that route must be disabled on the public server. Guest/transfer entry is implemented; native Google/Apple account login is separate from payment verification. Optional Google Play and Apple receipt verifiers are implemented, disabled until configured.

Social play uses your chosen name, alliance membership/rank/title, applications and invitations, help activity, chat, messages, map notes and bookmarks. We process battle and event records to resolve actions consistently and deliver rewards. Blocks, reports, moderation reasons and account restrictions help us handle abuse and support requests.

Support tickets contain your subject and message, our replies and case status. Staff may add internal notes. Your ordinary ticket view shows only your own tickets and public replies, not internal notes, staff identities or closure reasons. Please do not send passwords, access tokens, real payment details or unnecessary sensitive information.

The planned closed test has new purchases switched off and shows “coming soon”; it does not grant free test purchases. If real billing is enabled later, the store provider processes payment and our server verifies account-bound receipts. We retain product/transaction identifiers, recorded prices, granted goods, purchase status, claim records and refund/chargeback review/audit information for purchase integrity and support. Pending receipt credentials are encrypted using a separate server key ring; we do not receive your payment-card number. If a reversal cannot recover spent goods, the missing game goods are recorded for review; this is not a monetary bill or permission to charge you.

To be confirmed — The server receives your IP address or a proxy address as part of network communication and uses it for request limits. Requests include app version, platform, rules version, account credentials and the action being requested. Our own code does not keep a player IP-history column, but hosting/proxy/OS logs may have additional network information. [DECISION D05/D18 — identify actual providers, logging fields and retention.]

Optional usage and crash reporting

The “Share usage and crash reports” setting currently defaults on. While enabled and online, the client queues session starts, guided progress and Keep levels, and exception messages/stacks, and sends batches to our server. These reports are linked to your account and can contain text or paths embedded in an exception.

Switching the setting off stops new optional collection and the current client drops queued reports before sending. A report already in flight cannot be recalled; previously received records are not automatically deleted. The setting is local to the device, not an account-wide server preference. Essential gameplay, purchase, security and server performance records continue independently of this setting.

To be confirmed — [DECISION D04/D19; LEGAL CHECK D03/D04 — approve the lawful basis, default and required choice mechanism before publication. Server-authored experiment exposures and essential security/operational records are independent of the local reporting switch; approve and disclose them separately. The present switch is not proof of valid opt-in consent.]

What other people can see

Other players can see game information intended for shared play: your name/id, town's virtual position, strength/Keep, alliance and role, relevant rankings, territory and battle information. Alliance members see relevant membership, help, rally, announcement and live map-note information. Kingdom chat is visible to other players; alliance chat to members.

Private messages are visible to the participants through game features. They are filtered and stored on our server, not end-to-end encrypted. There is no normal staff conversation browser, but reported/pasted messages can reach moderators, and authorised infrastructure operators can access underlying records.

Support staff can inspect relevant account/game details, communications available through moderation tools, reports, purchases, crashes, tickets including internal notes, and dashboard information. Admins have additional powers including data export/deletion, financial actions, ticket closure and staff management. We record staff actions in an audit log. Someone who receives information may keep their own screenshots or copies.

To be confirmed — [DECISION D05 — insert the actual hosting/database, logging/monitoring, backup and support providers and their roles, locations and contracts. The reviewed custom code sends telemetry to the game server. Unity service settings are mostly disabled, but a release-build/vendor verification is still required; do not substitute a blanket “no third-party collection” promise.]

How long we keep information

These are the current technical behaviors, not approved legal retention periods:

To be confirmed — [DECISION D06/D18 — replace unresolved retention with justified periods/criteria, including backups, restore handling and legal holds. Do not claim that a tax law requires the current indefinite retention of test receipts.]

Deleting your account and asking for data

The current game lets an authenticated player request deletion in Settings by typing DELETE. The public account deletion page also accepts a short-lived, one-time code issued in authenticated Settings, or a Support request without the app. It removes the main town/account, own support tickets, several personal social records and both sides of stored private messages. It then starts a new guest town if you continue. A banned/refused account may be unable to use that ordinary route; the no-app web form remains available. It creates an unverified Support ticket, not a deletion. Support checks ownership independently; only an admin can confirm deletion. A claimed ID/email alone is never sufficient proof. If ownership cannot be verified safely, staff must explain the reviewed next steps rather than delete someone else's account.

Deletion does not immediately remove every reference. Financial records, moderation cases, audit logs and some battle/reinforcement history remain. Duel action identifiers are replaced by a linked random pseudonym; that alone does not guarantee anonymity. Other players' reports/mail/mentions, shared crash text, logs, backups, copied files and device data may also remain.

An admin can produce a JSON export, but the current product export is incomplete: it excludes, among other things, received private messages, detailed financial/audit material and some external battle records. Internal support notes are not in the ordinary export. A privacy access request may need a separate reviewed response; internal labels do not automatically determine legal disclosure rights.

To be confirmed — [DECISION D08/D20/D25 — fill the monitored contact on the public support page and approve the ownership-verification, response and delivery/redaction process. Do not ask for a bearer token or password as proof.]

Your choices and rights

To be confirmed — [LEGAL CHECK D02/D08 — confirm applicable rights and response rules by market.] Depending on applicable law and the processing basis, you may be able to request access, correction, erasure, restriction or portability, or object to processing. Where processing relies on consent, you may withdraw it. Contact [DECISION D01 — privacy contact] to exercise applicable rights or raise a concern. [DECISION D02/D20 — insert the correct regulator complaint route and response process.] Nothing here limits rights that applicable law gives you.

Legal bases, security, transfers and children

To be confirmed — [LEGAL CHECK D04 — complete and approve the purpose-by-purpose lawful-basis table in the review register. Essential service, optional reporting and retained safety/financial records must not be treated as one blanket consent. No final basis is asserted in this draft.]

To be confirmed — Credentials are hashed on the server, requests are authenticated and staff access uses separate roles. These controls do not encrypt all stored content or guarantee that incidents cannot happen. [DECISION D09 — verify production HTTPS, database/backup/device protection and operational access.] [LEGAL CHECK D02/D05 — identify actual international transfers and applicable safeguards.]

To be confirmed — No age/date-of-birth or parental-consent system is implemented in the reviewed game. [DECISION D03 — choose the audience/age policy and implement the required protections before publishing an age claim.]

To be confirmed — The game uses automated rules for rewards, combat, limits and filtering. Staff decide moderation/refund actions in the existing tools. [LEGAL CHECK D04/D10/D12 — assess the significance of automated restrictions and provide appropriate explanation/review.] There is no observed custom advertising-profile system.

Notifications and the public website

To be confirmed — If configured and you opt into device registration, we keep the notification token, platform, language, UTC offset and notice preferences to send relevant game alerts and apply quiet hours. Google Firebase receives the token and short alert content; Android only is planned for this closed test. The default server sender logs rather than contacting Firebase. [DECISION D05/D25 — approve provider terms, lock-screen privacy, native permission flow and actual enablement before use.]

The public website uses no tracking scripts or cookies. Its deletion form receives the account reference, contact email and details you choose to send. It also uses a daily keyed address hash to limit abuse, retained for about two to three UTC days; raw addresses may still exist in separately configured hosting logs. One-time deletion codes are stored only as hashes, expire after ten minutes by default, and are single-use. Unresolved web requests and their messages expire after 30 days, checked hourly; completing deletion removes contact/reference content immediately from the active database, but an action audit remains. Staff replies here are internal records; the server does not automatically email you. Website/app exports, backups and contact-mailbox copies have separate policies still to be approved.

To be confirmed — [DECISION D06/D08/D18/D20/D25 — approve these windows, monitoring/staffing, verification evidence, retained deletion audits and handling of restored backups before testers are invited.]

Changes

To be confirmed — [DECISION D15 — define publication location, version/date, notification and any required renewed choices.] We will describe material changes accurately when adopted. This draft does not retroactively authorise new uses. The remaining decisions and implementation gaps are listed together in PRIVACY-REVIEW-DECISIONS.md.

Task 23 notice addition for review: optional app integrity

To be confirmed — DRAFT FOR REVIEW — NOT LEGAL ADVICE. If enabled, Wardenreach uses Google's Play Integrity and Apple's App Attest to assess whether a connecting app is recognized and to flag evidence for staff review. A service outage is distinguished from a failed proof. These signals do not automatically ban you or stop delivery of a purchase already paid for.

We would keep the latest account-linked result, reason and time; short-lived challenge hashes/metadata; and, for App Attest, a public verification key, account-scoped key tag, counter, credential handle and environment. These are security records, not anonymous data. This implementation does not store hardware identifiers, raw integrity tokens or attestation objects, and does not introduce device-based farm tracking. Platform providers process their native requests; the Google token is also sent to Google for decoding. Credentials/results are deleted with the account; existing staff-audit, export and backup limitations apply. Staff can review flags and clear them with an audit trail. See the inventory for exact implemented lifetimes and export scope.

To be confirmed — [DECISION D23 — confirm necessity/basis, provider recipients/transfers, supported-device/accessibility treatment, notices, credential/nonce retention and human appeal process before enabling. Resolve the broader device-ID question separately; this paragraph does not authorize it.]

Task 24 addition for review: optional chat translation

To be confirmed — DRAFT FOR REVIEW — NOT LEGAL ADVICE. This feature is off until the operator makes decision D24. If enabled and you request a translation, Wardenreach sends the stored message text and target-language settings to the selected translation service: [DECISION D24 — name DeepL, Google Cloud Translation or the self-hosted LibreTranslate operator, actual locations and relevant terms]. We do not attach the sender's account, name or conversation context. Text you or another player typed can itself contain personal information; sending text is a disclosure outside the game server even without those metadata fields.

We keep your chosen language on the account and cache translated text/detected language per message and target so repeated readers do not send it again. Current visibility is checked before serving it. Cache copies are removed when the source changes, is hidden or deleted under the game's chat/account lifecycle; private messages currently have no automatic age expiry. Failed/uncertain submissions are retained as status records until that lifecycle removes them. Aggregate monthly usage and account quota counters protect cost and abuse limits. Account deletion removes its language/quota records and source-related cached copies; retained aggregates, audit/log/backup/export copies and any provider copy have separate limits. Product exports include the account language but do not separately list all derived translation/cache/quota records; rights requests need the reviewed supplemental process.

To be confirmed — [DECISION D24 — confirm purpose/basis, any choice/consent mechanism, provider contracts/subprocessors, data locations/transfers, retention/training restrictions, minors/accessibility safeguards, source-author disclosure, rights handling and the strict timeout/cost tradeoff before turning this on. Do not publish this placeholder as a completed disclosure.]