Delete Your MB Hisab AI Account

MB Hisab AI is managed by MB Developer Apps. MB Hisab AI users can start account and data deletion from the signed-in application. Open MB Hisab AI, go to Settings, choose Delete Account/Data, read the deletion summary and enter the required confirmation text. The app separates local data deletion, cloud business-data deletion and authentication-account deletion so it does not claim that a step succeeded before the backend confirms it.

Before you delete

Account deletion may permanently remove business profiles, customers, ledger entries, sales, expenses, invoices, inventory records, imported bank transactions, reconciliation records, subscription mappings and other account-owned information. Export any records you are legally or operationally required to retain before starting deletion.

Encrypted ID-proof images associated with customers are local-only by default. Current-account deletion targets files and encryption-key metadata that belong to the signed-in account. It must not delete another Google account's records stored on the same device.

Delete from the application

  1. Sign in with the Google account whose MB Hisab AI data you want to delete.
  2. Open Settings and select Delete Account/Data.
  3. Review which local, cloud and authentication records will be affected.
  4. Enter the displayed confirmation word exactly.
  5. Submit the request and wait for the application to report the confirmed result.

Do not close the app while a deletion request is being processed. If the app reports that cloud deletion is unavailable or incomplete, local deletion may have finished without deleting the Supabase authentication account. In that case, follow the support process below rather than assuming every copy has been removed.

Request deletion through support

If you cannot sign in, the in-app flow is unavailable, or a deletion request remains incomplete, email support@mbhisabai.com from the Google email linked to the account. Use the subject MB Hisab AI account deletion request.

Include the platform you used and a short description of the problem. Do not email passwords, OTPs, UPI PINs, bank credentials, card details, Aadhaar images or customer financial records. Support may ask for limited account-verification information, but it will not ask for a Google password or banking secret.

Processing and confirmation

Deletion is account-scoped. The backend derives the account identity from a verified Supabase session and does not trust a user ID supplied in a client request. A retryable deletion workflow may continue an interrupted request without deleting another user's data or repeating completed stages.

The app or support email must give an accurate status. A local-only completion message does not mean cloud data or the authentication account was deleted. Contact support if the status remains unclear.

Some records may need limited retention where law, fraud prevention, payment reconciliation or dispute handling requires it. Support will explain the available deletion status when a request needs manual review.