This page explains how account deletion works in Gulak, why some accounts are blocked from deleting immediately, and what happens to your data after you confirm the request.
The app checks for active committee membership before it sends a deletion request. If a committee is still in progress, the user must resolve that first.
Deleting your account removes your active access, clears saved login state on the device, and stops the app from restoring the account on future launches.
Some records are kept for compliance, payments, audit trails, and dispute handling. That is normal for financial and committee-based applications.
A live committee depends on its current organizer and members. If an account disappears while the committee is still active, it can break payments, turn handling, and accountability.
That is why deletion is blocked when the account is tied to an active or in-progress committee.
Open Profile or Security Settings.
Tap Delete Account in the Danger Zone.
Enter your password to confirm your identity.
Read the warning and confirm the final deletion dialog.
If there are no blocking committee obligations, deletion succeeds and the app signs you out.
Deletion is applied at once on the backend and the device is signed out with local auth data removed.
Users cannot delete while they are tied to an active or in-progress committee, which protects live committee operations.
Only the records needed for compliance, disputes, and payments are retained after deletion.
The product follows a soft-delete approach with local cleanup, then retains only the records required by policy or law.
If you see a committee-related block, leave or transfer the committee role first. Once the account no longer affects an active committee, you can try the deletion flow again.
Review the steps