Operator and contact
KDK Games is the owner-confirmed operator copy. Contact game@mandiwars.com for support or privacy requests; the owner confirms that the mailbox works and is monitored. Privacy/grievance contact: Karan Gandhi. Correspondence address: 12/a, Prerna Kutir Bunglows, Behind Sarthi Hotel, Vastrapur, Ahmedabad, 380054, India. No company-registration classification is inferred. India-first is the accepted launch scope; worldwide availability requires the applicable review.
Account requests and verification
Open Account rights / delete account from the Google sign-in screen or inside the game. Fresh Google verification opens an independent account:rights session for 15 minutes, without issuing a gameplay token or creating/linking a different account. Existing restricted players can request rights without successful gameplay authentication. The v28 app also makes the supplied Terms and Privacy notices readable before Google sign-in, including closed-registration paths.
Alternatively, email game@mandiwars.com for access, correction, deletion or a privacy concern, including after uninstalling; reinstalling is not required. Supply the account email and request, with the trader/business name only if it helps locate records. A proportionate account-control check may be necessary. Do not send passwords, Google proof tokens, payment details or government ID. An acknowledgement/request receipt is not completed erasure. The owner confirmed Karan Gandhi as the request handler, with acknowledgement within 48 hours and completion of a verified deletion request within 30 days after verification. These are approved operating commitments, not evidence that the current code can close every progressed/shared account. Proportionate verification, the staffed end-to-end procedure and remaining closeout acceptance are still open.
Removal and retention commitments
The owner has adopted the following commitments. Automated retention approval remains a separate disabled-by-default gate; publishing this notice does not enable that automation. On completed deletion, remove account sign-in credentials, the owned Google binding, unnecessary profile and relationship data, and sent direct/crew message bodies and their cosmetic receipts. Revoke account sessions/devices and prevent restoration of the erased identity. A report copy is subject to the separate case-evidence rule below. This is not a blanket scrub of arbitrary text in every receipt.
Some records remain linked to pseudonymous player/account IDs: fictional asset balances and ownership, ledger/financial receipts, audit and hold records, request/suppression references and signed restore-suppression evidence. The untouched-starter path can retain the original fictional wallet and debt without a grant, repayment, forgiveness or transfer. Original financial proof bytes are preserved; identifying fields in mixed onboard/profile receipts have their existing redaction exception. These retained references are not fully anonymous. Progressed debt, loans and accepted shared obligations still require reviewed closeout; that implementation is pending. Fictional borrowing is not a real debt owed by the player or a blanket legal retention exception.
- Necessary restricted pseudonymous game ledger/receipt evidence: 180 days after account closure, to investigate fraud and preserve other players' accepted outcomes. Do not publish the erased profile through historical readers. Keep only the necessary subset and preserve original financial proof bytes while retained; expiry must use verified checkpoints/readers rather than deleting evidence solely because it is old.
- A reported-content copy: only restricted evidence for a specific moderation or security case, for 180 days after that case closes. Remove unrelated personal text.
- Necessary security logs: 180 days from the event. Short-lived aggregate load counters without account identifiers retain their existing shorter bounds. Confirm provider-side processing and retention separately.
- Account-data backups: rotate within 30 days. Apply signed suppression before a restore can accept access; keep suppression for at least the period in which a usable older copy exists. Source-code release archives contain no player data and have a separate lifetime.
- A documented legal hold is separate from these normal limits. Review its necessity at least every 30 days and remove the held data when the hold ends. Holds must not become an indefinite default.
These are owner-selected operator limits, not a statement that every category or exception is required by law. Accounting consistency alone is not a legal retention exception. The 180-day game content horizon and 12-year game career are separate gameplay specifications. The operator must explain the necessary retained subset, access limits and expiry to the requester. Neither the selected schedule nor the 48-hour/30-day commitments establish universal code completion, tested expiry or provider backup/restore acceptance.
Signed suppression must be preserved and applied to a restored database before account access reopens so old identities, provider bindings and credentials do not return. A new moderator restore cannot revive a suppressed actor. The logical restore tests do not establish a physical backup/restore drill or key-custody acceptance. A later permitted registration/onboarding creates a distinct account and starter kit, not access to the retired account's retained assets; the retired row still counts against finite registration capacity.
Review and changes
This notice is not a legal compliance statement or Play approval. The operator must complete the remaining retention/fulfilment implementation and operational acceptance described above. The owner confirms review for the India release; worldwide distribution requires separate applicable review. Worldwide distribution remains subject to professional review. Material changes in processing need corresponding reviewed notices and declarations. Contact Karan Gandhi through game@mandiwars.com or the postal address above with privacy or grievance concerns. No final statutory complaint route, forum or timing rule is invented here.