Delete directly in Pile Raid.
- Finish or leave any live match. Leaving a live competitive match may count as a forfeit.
- Open Settings → Privacy & Safety → Delete account.
- Review what will be removed and what may be retained.
- Re-authenticate with the account’s current sign-in method.
- Type the confirmation shown by the app and submit once.
- Keep the non-sensitive receipt identifier if follow-up is needed.
The server refuses deletion while your account is still part of a waiting, playing or reconnecting match. This protects the other players’ result and prevents a mutable game from being erased underneath them.
Identity and player-scoped data are removed.
- Firebase Authentication account, after destructive player-data stages and session revocation complete;
- private and public profile, email/profile projection and username reservation;
- friends, invitations, blocks and account-owned social relationships;
- matchmaking ticket, presence, private hand and any inactive or stale game membership remaining after the live-game preflight;
- leaderboard and competitive-rating projections linked to the account;
- account wallet, XP, progress, inventory and achievement projection after economy integrity is settled; and
- other private user records classified for deletion by the server lifecycle manifest.
The exact cascade is server-authoritative. A browser or patched client cannot choose to skip stages. If final non-identity bookkeeping fails after Authentication is gone, the receipt says cleanupPending: true and a durable server repair job finishes it without asking a deleted account to sign in again.
Some records may remain without an active profile.
The completion receipt identifies five limited server-retained categories. Device-local data is listed separately and is not part of that receipt:
Exact retention periods and legal-hold rules remain subject to the published Privacy Policy and legal approval. Retained records must not recreate a public profile or permit new rewards after the deletion cutoff.
Cannot open the app? Delete here.
This web route supports email/password accounts when the deployment has an approved Firebase Web configuration. Google, Apple and guest accounts use provider-specific re-authentication inside Pile Raid. The form never saves your password or ID token in local storage, session storage or cookies. It stores only a random private deletion request ID in this browser's local storage for at most 30 days so a reload or lost authenticated response can be checked without claiming false success. That key is not identity proof and must not be shared.
Authenticate and delete
Signing in here creates a recent Firebase session (maximum server-accepted age: five minutes), checks getAccountDeletionStatusRT for an interrupted server request, then sends one idempotent request to deleteAccountRT. On reload or after authentication is lost, recoverAccountDeletionRT can return only none, processing or a strictly validated completion receipt for the private request ID.
No undo after authentication is gone.
- The server returns success only with
status: completed,authDeleted: true, a pseudonymous retention declaration and the exact five disclosed retained categories. - If a pre-Auth stage fails safely, the response is partial and retryable; it is not displayed as success.
- A retry reuses the same private request ID in browser local storage so completed stages are not duplicated.
- If
cleanupPendingis true, Authentication is already gone and the server—not the deleted client—owns final repair. - On success, credentials and Firebase tokens are discarded. The private recovery key remains only in this browser for at most 30 days so the completion response can be recovered; never share it.
- Creating a new account later does not automatically restore the deleted profile, purchases or username.
Deletion should not depend on reinstalling.
If you cannot authenticate, have only a Google/Apple/guest account, are a parent or guardian acting for a younger player, or receive a partial receipt, use the approved Support channel. Support may verify identity or authority, but will never ask for a password.