How to delete your Whizi account, and exactly what is removed

The short answer

Delete your Whizi account under Settings, in the mobile app or on the website, using the two-step confirmation flow. If you cannot get into the account, follow the instructions at whizi.io/account-deletion or contact support instead.

Two things are worth doing before you confirm, because neither can be done afterwards:

Do this first	Why
Export your data	Settings, under Account, has Export Data. It returns your account as one downloadable JSON file.
Cancel a store subscription	Deleting the account does not cancel Apple App Store or Google Play billing. That has to be cancelled with the store.

The terms of service put the second point plainly: "Deleting the App or your Whizi account does not cancel store billing. You must use the applicable store's subscription-management settings to cancel."

Exactly what deletion removes

The privacy policy lists the current deletion flow item by item, and this is the whole list rather than a summary of it:

• The live Whizi account record
• Synchronized chats and messages
• Uploaded and generated media stored under the user account
• Saved mobile memory
• Referral records
• Mobile entitlement and usage state
• Rate-limit state
• Push tokens
• The Clerk authentication account, which is the sign-in itself
• The local chat cache on the device completing deletion

All of it is subject to the limited retention described in the next section. The local cache matters more than it sounds: on mobile, Whizi may keep a cache of up to 40 recent conversations on the device, and that cache is not a separate cloud backup. It is cleared as part of a successful in-app deletion, and it can also be removed by clearing app storage or uninstalling the app. If you completed deletion on one device and a second device still holds a cache, clearing storage there is the direct fix.

Deleting the whole account is not the only lever. Individual conversations and uploaded files can be deleted on their own, and uploaded attachments and generated media are configured to expire after up to 30 days regardless. The retention table for everything else is on what Whizi does with your data.

What survives deletion, and why

An honest answer here is more useful than a clean one, so here is every carve-out the policy names.

What can remain	For how long	Why
Provider caches at OpenRouter and routed model providers	Varies by provider and endpoint	Whizi cannot instantly remove a provider cache that has already been created
Cloudflare D1 point-in-time recovery history	Up to 30 days before aging out	Protected recovery history covering deleted database records
AI-output reports	As long as reasonably needed	Stored separately from chat history for safety and security review
Limited account, transaction, security, tax, fraud-prevention or dispute records	As legally or operationally required	Legal and operational obligations
Payment processor records at Apple, Google, RevenueCat and Stripe	Periods required by law or their compliance obligations	Transaction, receipt, tax, fraud, chargeback and dispute records

One clarification that answers the question people usually mean by this: "Whizi does not keep deleted chat content or uploaded or generated media merely because a payment record must be retained." A retained invoice is not a retained conversation.

An AI-output report is the exception worth understanding, because it is the only category the policy says may outlive the account by design. A report may contain a bounded excerpt of the reported output plus related account or technical identifiers, and reports may remain after account deletion only for as long as reasonably needed for safety, fraud prevention, dispute resolution, or legal obligations.

Export your data before you delete

Export Data sits in Settings under Account, and the export endpoint is described in the code as the access counterpart to account deletion. It returns the account as a single downloadable JSON file.

In the export	Not in the export
Chats and messages	Quota counters
Memory	Rate windows
Projects and their file metadata	Push tokens
Media, as metadata plus a signed URL
Share links
Subscription
Referral profile

The three omissions are deliberate: they are transient bookkeeping rather than content, and they are the same categories deletion wipes anyway. Media is exported as metadata plus a signed URL rather than inlined bytes, which is what keeps the file readable JSON instead of an unopenable blob, so download anything you actually want to keep while those links still resolve.

Export is rate limited to 5 requests per minute. If a first attempt fails, the toast is "Failed to export your data. Please try again." and the underlying error is "Export request failed ({status})." with the HTTP status filled in.

Deleting guest data when you never made an account

Whizi on mobile can be used without an account, which creates an anonymous device-bound guest profile that needs no name or email address. That profile holds real chats, so it has its own deletion path.

Select Delete guest data in Settings and confirm the deletion twice. It removes the anonymous guest profile, Whizi chats and messages, uploaded and generated media, saved memory, entitlement and usage state, guest identity links, and the local guest data on the device completing deletion, subject to the same limited retention.

Export works for guest sessions too, which is the point worth knowing before a device is wiped or handed on: a guest holds chats and memory that exist nowhere else, so exporting first is the only way to keep them.

If deletion fails

The failure surface is short. In Settings, a failed deletion shows "Your account could not be deleted. Please try again, or contact support." The raw error behind it is "Account deletion failed ({status})." with the HTTP status filled in.

Retrying is the first move. If it fails again, the contact route is the same one the policy names for people locked out of their account: support at whizi.io/support, or the instructions at whizi.io/account-deletion.

Whizi does not publish a completion time for deletion, and there is no stated "within X days" figure to quote. The only related number the policy commits to is the Cloudflare D1 recovery history of up to 30 days before deleted records age out.

Deleting is not cancelling

These are two separate actions and doing one does not do the other. The terms of service state it directly: "Account deletion and subscription cancellation are separate."

Cancelling stops billing and ends access at the end of the paid term while the account and its contents stay put. Deletion removes the account and its contents. If you subscribed through Apple or Google, deletion also leaves that subscription renewing until you cancel it with the store. The order that avoids both mistakes is cancel first, confirm the cancellation, then delete. See billing and cancellation for where to cancel by how you signed up.