Delete your Mahvo identity Draft

Draft for owner/lawyer review. Proposed page: https://mahvo.app/delete-account. Seller/controller: [Company name] LLC. This draft explains the request process; a published page alone does not perform deletion.

Delete from the app

Open Mahvo Settings and find Delete identity. Read the confirmation carefully and complete the authentication requested by the app. Keep the app open until the service confirms completion. If it reports an error, follow the retry instructions or contact support. Do not assume deletion finished because the app closed or was removed. The final release navigation and completion journey must be verified before this page is treated as final instructions.

Ask for help or request deletion online

Use [VERIFIED DELETION REQUEST FORM OR SUPPORT CONTACT TO BE INSERTED]. Identify the app identity you want deleted using the minimum information needed for verification. Do not send recovery words, unlock codes, passwords, private keys, complete sealed links or unrelated conversations. The operator must provide a working request channel, safe identity verification and an acknowledgement process; this draft has no live submission form. Proposed help page: https://mahvo.app/support.

What deletion covers

The intended request covers the Mahvo identity and its associated service data, with applicable transaction, security and legal retention exceptions. [INSERT VERIFIED DATA CATEGORIES DELETED, EXCEPTIONS, RETENTION PERIODS AND BACKUP LIFECYCLE.] Exact server deletion, linked records and backups still require final operational verification. No unsupported immediate-all-data promise is made.

Source review shows that the normal authenticated server deletion path hard-deletes the account and cascades its payment rows if the required schema is applied and the operation succeeds. It also retains a deletion-receipt token hash with a 24-hour validity window; that window does not prove physical erasure at 24 hours. The retirement-enabled path retains retirement proofs and a signed certificate containing the account subject, device identifier and public signing key, without a source-defined expiry in the inspected path. These exceptions do not justify retaining other data indefinitely. Actual deployment, successful deletion, retention schedules, backups, provider records and local billing-journal erasure remain unverified and must be reconciled before publication.

Security has identified a source-defined whole-identity deletion path: after exact-identity confirmation and private cleanup, it removes that identity’s local metadata and journal directory, including the billing journal, while preserving other identities. This is not per-purchase expiry or deletion on lock/background, and actual execution and external backup/provider effects remain unverified. Retained server retirement proofs support offline linked-device deletion verification and replay after a lost acknowledgement; they remain linked security metadata, not anonymous records.

Recipient-held saved or captured copies may remain. Uninstalling Mahvo is not a server deletion request. Deleting an identity does not itself cancel an Apple or Google subscription; manage it through the store account used to buy it. If partial-data deletion requests are supported, the published page must explain the tested route and limits.

Privacy policy: https://mahvo.app/privacy. Support: https://mahvo.app/support. URLs are proposed until Web verifies deployment. This page and the policy must agree with App Privacy and Data safety before submission.