Option 1 — in the game (7-day grace period)

1. Open Settings.
2. Open Account.
3. Press Open next to Privacy.
4. Press Delete account.
5. On the confirmation page, hold Hold to delete for 2 seconds. Let go to stop.

You must be signed in to online play; if you are not, the panel says "Sign in to online play first".

The request waits 7 days. During those days the panel shows "Deletion pending: N days left" and a Cancel deletion button. Signing in again also cancels the deletion and the game tells you. After 7 days the purge runs and the account cannot be restored.

Option 2 — by email (no 7-day wait)

Write to godsiege.support@gmail.com with the subject "Account deletion". Please include:

• your recovery code — the best identifier — or your player name;
• the country you played from;
• roughly when you started playing, and your clan name if you have one.

Do not send a password (there is none) or payment details. We may ask for proof only the account owner has. We answer within 30 days and start the same purge as soon as we can identify the account. An email request does not wait 7 days.

If you lost your recovery code and never set a player name, write to us anyway and give as much as you remember; we will tell you what else can identify the account.

What is deleted, and when

In the game: the purge runs 7 days after the request, unless you cancel it. By email: the purge starts as soon as we identify the account (no 7-day wait), and we answer within 30 days.

The purge deletes:

• the account row and its random account id;
• the village and its save;
• sign-in sessions;
• country and age band;
• the chat profile, notes you posted on clan-war or island marks, all your chat lines in our database and in Nakama, and your ended mutes;
• chat reports about you are deleted; in reports you filed, the evidence about the other player stays but your comment and id are removed;
• your block list;
• analytics events and the server-side analytics switch;
• network and device link rows, and your device hash on the account;
• push tokens and notification switches;
• the recovery code hash and the Play Games link hash;
• your clan membership — you leave your clan; the clan stays and its leadership passes to another member;
• the Nakama user.

The deletion request log keeps the account id and request ticket only as SHA-256 hashes, plus the request/grace/done dates, the status and a random tombstone id.

This purge happens on our server; it does not delete files on your phone. Clear the app's data or uninstall the game to remove server-session.json, device-id.txt, analytics-switch.json and the other local files.

What is kept, and why

Purchases — 5 years

iap_purchases (Google Play order id, product, offer, price, gems, purchase-token hash, refund/test state, pass dates) stays under a random tombstone id for 5 years (1825 days), then a daily job deletes it. Reason: tax, refunds and accounting.

Money ledger — kept indefinitely for accounting

transaction_log and lucbao_ledger money rows stay under the tombstone indefinitely. The purchase-retention job does not remove these rows today. Reason: accounting.

War and island history — kept indefinitely for game fairness

War members, attacks, results, chest claims, island battles and weekly clan points stay under the tombstone. The village save copy is cleared, and the battle army/result and island snapshot/command/stream fields are cleared where the purge can; war-member base snapshots and war-attack command/stream rows can remain. These rows carry a random tombstone, not your account id. Reason: the other clan's game history and fair results.

Battle replays — kept indefinitely for game history

Battle id, replay/offense text, content version and date. Replays contain layout, troops and commands, no account id or name. Reason: game history.

Deletion request log — kept indefinitely as proof

A SHA-256 hash of the account id, a SHA-256 hash of the ticket, the request/grace/done dates, the status and the tombstone id. Reason: proof that we carried out the request and to avoid repeat requests.

Operator audit log — kept indefinitely for legal and audit

Admin name, action, tombstone id/ticket hash and old/new values.

Job history — kept indefinitely for operations

Job kind/scope, tombstone ref, status and last error. Reason: operations and debugging.

Anti-cheat review rows — kept indefinitely for fairness

Kind, war/island reference, clan ids and detail with tombstone ids.

Banned device — kept for anti-abuse

The keyed device-fingerprint hash and the device-block row stay after account deletion. A device is blocked only after 3 banned accounts used it. Reason: a banned person cannot reset a device block by deleting the account.

Backups — at most 30 days

Copies made before the deletion expire on their own within 30 days. If a backup is ever restored, the operator must re-apply the deletion before the game reopens; this is a manual step, not automated code.

Technical logs — until rotation

Error codes, routes, status, account id and, for purchases, the order id and a short token-hash prefix. No raw IP is written by the game server. Kept for a short operational period and rotated on the host.

More information

Read the full privacy policy. Questions: godsiege.support@gmail.com or godsiege.support@gmail.com.