Deleting Your Account

You own your data. You can take it with you or remove it entirely, on your terms.

Export first (usually)

Before you delete, most people want to keep the code they built. From each project:

• Export to GitHub (see Exporting to GitHub). The code sits in your GitHub account permanently.
• Your Supabase backend is in your own cloud account. Deleting your Appsanic account does not delete it.

After those two exports, you have everything.

Requesting deletion

1. Go to Account > Security > Delete account.
2. Read the summary of what will be deleted.
3. Type DELETE to confirm.
4. Re-enter your current password. If you signed up via OAuth and never set a password, this step is skipped - the confirmation email below is what authorises the deletion.
5. Click Request deletion.

We email you a confirmation link to the account address. The link is single-use and valid for 72 hours.

Deleting your account deletes its team seats too. If you're on Business, the logins you created for your team are removed with the account, and so is everything stored in it. Tell the people using those seats first, and export anything the team still needs.

Confirming deletion

Open the email, click the link, and confirm. On confirmation, we:

1. Verify the link hasn't been used, cancelled, or expired.
2. Atomically reserve the deletion so seat changes, billing changes, and new jobs cannot change underneath it.
3. Cancel any active Stripe subscription and verify that open checkouts, paid top-ups, and invoices have settled safely. We email you a cancellation receipt.
4. Hard-delete your account: the owner cascade wipes the account and its projects, conversations, prompts, stored connector tokens, and any team-seat logins created under it.
5. Delete your avatar and the account's Storage prefix. A durable cleanup outbox retries provider failures after the account is gone.
6. Sign you out of every active session and email you a final goodbye confirmation.

If a checkout is still settling, an invoice remains unpaid, or an app-store submission has reached an irreversible stage, deletion pauses without removing local data. Resolve the blocker and retry the same confirmation link.

A few minimal forensic rows survive deletion on purpose - see the retention notes below. They use one-way email hashes and operational outcomes rather than raw account content.

What is deleted

• Your account and profile.
• Any team-seat logins you created under it.
• Your projects (on our servers).
• Your prompts, conversation history, and agent outputs stored on our side.
• Any connector tokens you stored with us.
• Your payment method reference in our system (Stripe retains records for their own compliance period).
• Your credit balance.

What is not deleted (for legal and practical reasons)

• Your GitHub repository and its code. That's in your GitHub account, not ours. Only you can delete it.
• Your Supabase project and its data. Same. That's in your Supabase account.
• Your Stripe or RevenueCat records, if you set up payments. Those services keep billing data for their own tax and compliance reasons. You can ask them to delete separately.
• Financial records. Australian tax law requires us to keep invoices and transaction records for 5 years after the end of the financial year. We do.
• Minimal security logs. We keep records of sign-in and billing events for up to 7 years for our own audit compliance. These contain no personal content. Just timestamps and event types.

See our Privacy Policy for the full retention schedule.

How long the deletion takes

• Your account is inactive immediately on confirmation.
• Deletion from our primary databases completes during confirmation.
• Storage cleanup is attempted immediately and retried automatically if the provider is unavailable.
• Deletion from backups happens on the backup retention schedule (typically within 30 days). Data in backups is not accessible for new reads.

If you change your mind

If you reconsider before you confirm the email link, simply don't click it. The request expires in 72 hours and nothing happens.

If you confirm and later want to come back, there's a 30-day cooldown before that same email can be used to sign up again. This is a deliberate guardrail against a deletion being reversed too quickly (for example, by someone who briefly gained access to your inbox). Once the 30 days have passed, you can create a fresh account with the same email - it'll be a brand-new account with none of your previous data. If you need to return sooner, email contact@appsanic.com.

Deleting under privacy law

If you're exercising a right under the GDPR, CCPA, or the Australian Privacy Act (APP 12/13), this flow fulfills that right. If you prefer to issue a formal request in writing:

• Email contact@appsanic.com with "Account deletion request" in the subject.
• Include the account email.
• We respond within 30 days as required by the Privacy Act.

Exporting your data

You can take a copy of your data with you before you delete anything.

• Self-serve export. From your account you can request a full export of your data - a complete JSON file of your account and its content (projects, prompts, conversation history, and metadata). The export runs on our side and returns a single JSON file you can download.
• Email fallback. If you'd rather have us run it, or you want it in writing, email contact@appsanic.com with "Data export request" in the subject and we'll respond within 30 days with a JSON export of everything we hold about you.

(Most of your code is already in your GitHub and Supabase accounts, both of which you control. The export above covers what lives on our side: billing records, audit events, and project metadata.)

Next

Need something that's still going wrong? Read Troubleshooting.