In-app account deletion: Apple and Google requirements

Both app stores require apps that let users create an account to let them delete it, inside the app, for real. It is one of the most common reasons an otherwise finished app gets rejected. This page explains what Apple and Google require, how grace periods, data export and subscriptions fit in, and what to test so the deletion flow passes review and actually works.

Who it’s for

  • Mobile developers adding account deletion before a store submission
  • Teams rejected under App Store guideline 5.1.1(v) or Google Play's account deletion policy
  • Product and legal owners deciding how deletion, retention and export should behave
  • QA leads writing the test cases for account lifecycle

Updated 2026-10-25.

What Apple requires

App Store Review Guideline 5.1.1(v) says that apps supporting account creation must also let users initiate account deletion from within the app. In practice Apple expects:

  • A deletion option that is easy to find, usually in Account or Settings, not buried behind a support chat.
  • Deletion of the account and the associated personal data, not a temporary deactivation or a "disable" switch.
  • Confirmation steps are fine, including re-authentication, as long as the user can complete deletion without leaving the app.
  • Pointing the user to a website is allowed only in limited cases, for example when the account is managed by a third-party service or in highly regulated industries. Even then, the in-app path has to make deletion straightforward.
  • If you must keep some data for legal reasons (tax records, fraud prevention), you can say so, but you cannot keep everything "just in case".

Apple's guidance has details on what counts and on handling legal requirements. Read the current text before finalizing your flow.

What Google Play requires

Google Play's User Data policy has a dedicated account deletion requirement for apps that allow account creation:

  • An in-app path to delete the account.
  • A web link where users can request deletion without reinstalling the app, declared in the Data safety form so it appears on the store listing.
  • Deletion of the associated data as well, unless you must retain some of it for legitimate reasons such as security or regulatory compliance, which you disclose.
  • If you offer partial data deletion (for example, delete activity history but keep the account), you can declare that too, but it does not replace account deletion.

The web link matters for people who already uninstalled the app. It can lead to a signed-in page or a request form, as long as deletion happens.

Grace periods and reactivation

Both stores accept a short grace period during which the account is scheduled for deletion and the user can cancel by signing in again, as long as:

  • The user is told clearly how long the period is.
  • The account is actually deleted at the end of it without further action.
  • Signing in during the period explains that deletion is pending and how to cancel it.

A grace period is reasonable because accidental deletion is common. What is not acceptable is a "deleted" state that keeps everything forever.

Subscriptions and purchases

Deleting an account does not cancel App Store or Google Play subscriptions. Those are managed by the store, tied to the Apple ID or Google account, and keep renewing. Your deletion flow should:

  • Detect active subscriptions and tell the user to cancel in the App Store or Play Store, with a link to the store's subscription management screen.
  • Explain whether remaining paid time is lost when the account is gone.
  • Keep the purchase records you need for refunds and tax, and disclose that.

Teams are often surprised when a user deletes their account, keeps getting charged, and leaves a one-star review. The warning screen prevents that.

Data export

Neither store requires data export as part of deletion, but privacy laws such as the GDPR give users a right to a copy of their data, and offering export before deletion reduces support tickets and regret. A simple "Download your data" option that emails a file within a reasonable time is enough for most apps. Offer it on the deletion confirmation screen.

Designing the flow

  1. Put "Delete account" in Account or Settings, visible without scrolling through unrelated items.
  2. Show a confirmation screen that explains what is deleted, what is retained and why, the grace period if any, and the subscription warning.
  3. Require re-authentication (password, biometrics or a fresh Sign in with Apple or Google token) to prevent deletion from a stolen unlocked phone.
  4. Delete server-side: user record, profile, content, tokens, push registrations, and data in third-party services (email marketing, analytics user IDs, payment customer records where allowed).
  5. Sign the user out on every device and invalidate refresh tokens.
  6. Send one confirmation email, then stop all emails and notifications.
  7. Make the web deletion link work for signed-out users.

What to test

  • Find "Delete account" from the home screen in under a minute without using search.
  • The confirmation screen states what is deleted, retention exceptions, grace period and the subscription warning.
  • Re-authentication is required and the wrong password is rejected.
  • After deletion: the app signs out, logging in with the same credentials fails with a clear message, and signing up again with the same email creates a fresh account with no old data.
  • Content created by the account is gone or anonymized where other users could see it (comments, shared items).
  • Push notifications and marketing emails stop.
  • The web deletion link from the store listing works while signed out of the app.
  • Social and Sign in with Apple accounts: deletion also revokes the token (Apple expects apps to revoke Sign in with Apple tokens when an account is deleted).
  • Grace period: signing in during the period explains deletion is pending and allows cancellation; after the period, login fails.

Example finding

Title: "Delete account" only deactivates; login works again immediately
Requirement at risk: App Store 5.1.1(v), Google Play account deletion policy
Environment: iPhone 14, iOS 18.1, build 3.4.0 (120), test account

Steps to reproduce:
1. Settings > Account > Delete account.
2. Confirm and re-enter the password.
3. On the login screen, sign in with the same email and password.

Expected: Login fails with a message that the account was deleted (or is
scheduled for deletion with a stated date).
Actual: Login succeeds and all data (profile, 14 saved items) is still there.
No email about deletion was received.

Severity: High (likely rejection; not real deletion)
Evidence: recording of steps 1-3, screenshot of the restored account.

How an AI beta tester helps

betatest.ing's Store readiness tests include an account deletion check. On your uploaded build, running on a real iPhone or Android emulator or device, it looks for the deletion entry point and times how long it takes to find, reads the confirmation screen for the required explanations, completes deletion with a throwaway account, then tries to log in again and signs up again with the same email to confirm the data is gone. Each gap is a finding with steps, severity and an annotated screenshot, with a recording of the full flow, and the report says whether the flow looks like real deletion or deactivation. Use a disposable test account for this task, never a customer's.

The test task

What you send your AI beta tester. It works out the steps and tests like a real user.

Test the account deletion flow in my app [UPLOADED BUILD OR STORE LINK]. It is [WHAT THE APP DOES]. Sign up for a brand-new account with a throwaway email [THROWAWAY EMAIL ADDRESS], add a little data (profile name, one or two items), then find the delete account option starting from the home screen and note how long it takes and how many taps. Read the confirmation screen: does it say what is deleted, what is kept and why, whether there is a grace period, and warn about store subscriptions? Complete the deletion. Then try to log in with the same credentials, sign up again with the same email, and check whether any old data reappears. Also open the account deletion web link from the store listing [DELETION WEB LINK OR 'none'] while signed out and report whether it works. Do not delete the saved shared test account. Log each gap as a finding with steps to reproduce, severity and an annotated screenshot, record the full deletion flow, and end with a report that says whether this looks like real deletion or deactivation, with the top fixes.

Fill in your details

Here, or later in the chat with your tester.

  • [UPLOADED BUILD OR STORE LINK] "the uploaded .ipa/.apk" or a public store link
  • [WHAT THE APP DOES] One sentence about the app and its users
  • [THROWAWAY EMAIL ADDRESS] An inbox you control that can be deleted, never a customer's
  • [DELETION WEB LINK OR 'none'] The deletion request URL you declared in Google Play's Data safety form, or none

What the AI beta tester checks

  • Delete account entry point found from the home screen, taps and time counted
  • Confirmation screen explains deletion, retention, grace period and subscriptions
  • Re-authentication required before deletion
  • Login with the deleted credentials fails with a clear message
  • Re-signup with the same email starts with no old data
  • User content no longer visible where others could see it
  • Web deletion request link works while signed out
  • Grace-period behavior on sign-in, where offered
  • Confirmation email received, then no further notifications

What you get

  • Findings with steps to reproduce, severity and annotated screenshots
  • A recording of the full deletion flow
  • A verdict on whether the flow is real deletion or deactivation
  • A report with the top fixes before store review

How to run it with betatest.ing

  1. Add your app as a project in betatest.ing and upload the build or paste a public store link.
  2. Create a throwaway email inbox for the test; do not reuse the shared test login.
  3. Send the account deletion task; the tester signs up, deletes and verifies on a real device or emulator.
  4. Fix the gaps, re-run on the new build and keep the task as a regression check for each release.

Tips

  • Put deletion where users expect it: Settings > Account, visible without scrolling far.
  • Warn about store subscriptions and link to the store's subscription management screen.
  • Revoke Sign in with Apple and social tokens as part of deletion.
  • Offer data export on the confirmation screen; it reduces regret and support load.
  • Keep the web deletion link working forever, including after a rebrand or domain change.

In-app account deletion requirement: FAQ

Does my app need account deletion if users sign up?

Yes. Apple's guideline 5.1.1(v) and Google Play's User Data policy both require apps that support account creation to let users delete the account, inside the app. Google also requires a web link to request deletion.

Is deactivating the account enough?

No. Both stores expect the account and associated personal data to be deleted. A grace period before deletion is fine if the user is told about it and deletion really happens afterwards.

Can I send users to a web page or support email to delete?

Apple allows it only in limited cases, such as third-party managed accounts or highly regulated industries, and even then the path must be straightforward. For most apps the deletion flow should live in the app. Google requires a web link in addition to, not instead of, the in-app option.

What data can I keep after deletion?

Data you must retain for legal or security reasons, such as tax records or fraud signals, as long as you disclose it. Keeping behavioral data, content or marketing profiles 'in case the user comes back' is not what the policies have in mind.

Does deleting the account cancel the subscription?

No. App Store and Google Play subscriptions are tied to the user's Apple ID or Google account and keep renewing. Tell users to cancel in the store before deleting, and link to the store's subscription settings.

How long can a grace period be?

Neither store publishes a fixed number. Keep it short, state the exact period on the confirmation screen, let the user cancel by signing in, and make sure deletion happens automatically when it ends.

Do I need to offer data export?

The stores do not require it, but privacy laws such as the GDPR give users a right to a copy of their data, and offering export before deletion is good practice that reduces support tickets.

Can an AI beta tester test account deletion safely?

Yes, with a throwaway account. It signs up, adds data, deletes, then tries to log in and re-register to confirm the data is gone, and reports each gap with steps and screenshots. Never run this with a real customer account.

Related beta testing guides

  • App Store rejection reasons — Most App Store rejections are not about taste. They cite a small set of guidelines: the app crashed, a login had no demo account, a purchase bypassed in-app purchase, a social login lacked Sign in with Apple, or there was no way to delete an account. This guide lists the common rejection reasons by guideline number, what reviewers actually check, and a review-readiness task your AI beta tester can run on the build before you press Submit.
  • Google Play rejection reasons — Google Play rejections tend to be about declarations more than design: a Data safety form that does not match what the app collects, a missing account deletion link, an undeclared sensitive permission or an outdated target API level. This guide lists the common rejection and removal reasons, what to fix for each, and a Play policy check your AI beta tester can run on the build before you submit it for review.
  • Sign in with Apple requirement — If your iOS app offers Google, Facebook or any other third-party login, App Store guideline 4.8 expects Sign in with Apple or an equivalent privacy-focused option too. This guide explains when the rule applies and when it does not, the parts of the flow that break most often (Hide My Email, missing names, revoked credentials, account linking), and a test task your AI beta tester can run on a real iPhone.
  • Login testing — Login looks simple until a user is locked out at the worst moment. This page lists what to test in login, logout and password reset flows, the safe limits for testing them, and a ready-to-run task for your AI beta tester.
  • Mobile app pre-launch checklist — Launching a mobile app means passing two store reviews, surviving real devices and keeping users on day one. This checklist walks through everything to verify before you submit, from builds and beta testers to store policies, in-app purchases, crashes and the listing itself, with links to detailed guides for each step and a full pre-launch task your AI beta tester can run.
  • Free tool: Beta testing checklist generator — An interactive checklist for websites, SaaS, mobile apps, stores and extensions. Progress saved, Markdown export.

More in by test type