Account Deletion

# Account Deletion Operations Checklist

This checklist describes the account deletion flow in LepasJudol: Stop Gamble Addictive. Deletion is initiated by the user in the app and removes the app's Firebase account data and local Firestore persistence. The process requires an internet connection and can resume after an interruption.

## User flow

1. Open Profile in the app and choose Hapus Akun.

2. Read the permanent deletion confirmation and choose Hapus Permanen to continue.

3. Keep the app online until it returns to onboarding. If deletion fails, the app stays in recovery and offers Coba Lagi.

If the device is offline, the app records a pending deletion but does not delete the remote records. Reconnect, then retry in the app or reopen it to resume the pending deletion.

The app creates anonymous Firebase Authentication accounts. It does not associate an account with the support address, [gyaaufau@gmail.com](mailto:gyaaufau@gmail.com). An email address alone therefore cannot identify which anonymous account to delete.

## What the flow removes

For the current Firebase Authentication UID, the app:

- Deletes the Firestore document in users containing the alias, streak start, best streak, relapse count, and account timestamps.

- Deletes the Firestore document in devices containing the device identifier and device record.

- Deletes the Firestore document in leaderboard containing the alias and streak statistics.

- Deletes the Firebase Authentication account.

- Clears local Firestore persistence and the saved deletion marker.

The deletion confirmation tells the user that the account cannot be restored. Reinstalling the app by itself does not perform this deletion.

## Operator checklist for a reported failure

- Ask whether the user still has access to the app and its anonymous account session. Do not treat the support email as an account identifier.

- If the user can access the app, direct them to Profile → Hapus Akun and ask them to keep the app online. A failed attempt can be retried with Coba Lagi; a pending deletion also resumes when the app starts again.

- If the user cannot access the app, do not guess which record belongs to them or clear a pending deletion marker. The app has no email-based account recovery or email-triggered deletion path. Escalate for an authorized, verified account-identification process before any manual action.

- Do not tell the user deletion completed while the app reports an error or recovery state.

## Completion checks

When an authorized operator can verify the backend, confirm that the UID has no documents in users, devices, or leaderboard, and that its Firebase Authentication account is gone. Confirm the app completed local cleanup and removed its pending deletion marker. If a stage failed, reconnect and resume from the saved stage rather than repeating already-completed steps manually.

Firebase provider logs or backups may follow provider retention timelines after the app's deletion succeeds. This checklist covers deletion from the app's active records and local persistence; it does not promise immediate removal from every provider system.