Maliaty account deletion
This page can be read in a browser without installing Maliaty.
Use the approved support address below. Opening your email app does not send the message: review it and press Send yourself. Ownership must be verified before deletion. In-app deletion still needs separate server activation and production verification.
Deletion request support address
Email subject: Maliaty account deletion request
If the link does not open an email app, copy the address, open your email app or webmail, enter the subject shown and your account email, then send the message yourself. Do not include passwords or verification codes as proof of identity.
Account ownership must be verified before deletion. A typed address or an email alone does not prove ownership or delete the account.
How to request deletion and verify ownership
- Read the deletion scope and remaining-data notice, then prepare text below. Include no password, API key, verification code or financial information.
- Open the prepared message in your email app or send it manually to the approved support address, including your account email and the deletion request subject. Support receives it only after you send it yourself.
- Ownership must be verified before deletion; a typed address or sender address alone is not sufficient. Support will provide appropriate verification steps. This page asks for no password or code; the operational verification procedure still needs separate approval.
- After server activation, verification and starting deletion, account writes and sync are blocked. Emailing alone does not pause synchronization. Cloud-data removal and sign-in-account removal have separate progress states. Partial failures remain pending and retryable; submitting a request is not completion.
What the reviewed deletion flow removes after activation
- The Maliaty sign-in account.
- The cloud profile and stored photo, transactions and recurring schedules, budgets, goals, recorded subscriptions, notifications and all descendants under that account's cloud data path.
- Associated cloud-assistant usage quota records, if present. This does not establish deletion of records or copies retained by an external provider.
- Only reliably owned local records, chat history, pending sync entries and account-specific settings when cleanup executes inside the app. A web request alone cannot wipe or prove cleanup on other devices.
What may remain
- CSV/PDF exports, shared or external copies and data on other devices: no verified remote-erasure mechanism exists.
- Unknown-owner legacy records, categories referenced by another account and shared local storage. Unknown data is not assigned to your account by guessing.
- Database recovery archives, creation files, legacy databases/backups, sync caches and residual storage pages. Deleting records does not guarantee erasing every trace from a device.
- Receipt/photo temporary files and system notifications without reliable ownership.
- Crash, service and provider logs or backups: scope and retention periods remain under review.
- Limited technical request records and locks needed for retries and preventing old sync from recreating data. Retention and access need approval.
Timing and request status
Processing deadlines and retention periods for remaining data are not yet approved. No deletion date is promised for exports, archives or external copies. Retention periods and reasons still need separate approval; sending email does not guarantee a deletion date. Confirmed progress, pending work and data without a verified deletion mechanism will be identified separately; no complete-erasure promise is made.
Prepare your deletion request email
This page prepares an email and only attempts to open your email app. Review it and press Send yourself in that app. Include no password, verification code, API key or financial information. Fields stay in page memory only.
Privacy
See the privacy policy and deletion scope. The policy's remaining text still needs review before launch; this draft does not adopt old unverified retention promises.