If your Android app lets people create an account, Google Play generally expects those people to be able to delete that account. The requirement is about user control, not about making deletion hard to find.
This is one of the more practical policy areas because the fix is usually visible in the app. It is also one of the easiest to get wrong in a subtle way: the app has a delete button, but it only deactivates the account, or the web deletion link is broken, or the Data safety form does not match what actually happens.
When the requirement applies
The requirement generally applies to apps that allow users to create an account inside the app. If users can sign up, they should have a clear way to delete the account and the associated data.
If your app only uses a sign-in provider for authentication but does not create its own account record, the situation can be different. The Play Console and Google's policy pages are the source of truth for your app. Do not assume that "login with Google" automatically means you are exempt.
What the flow should include
A compliant account deletion flow usually has these pieces:
- An in-app path. The option should be reachable from within the app, not only by emailing support.
- A clear description. Tell the user what will be deleted and what may be retained, and why.
- Confirmation. Deletion should be deliberate, with a confirmation step that explains the consequences.
- Actual deletion or anonymization. The account and associated personal data should be deleted, or handled in a way that matches your disclosed retention policy.
- A web request option. Google generally expects a publicly accessible web page where users can request account deletion without reinstalling the app. That link is provided in Play Console.
- Consistency with Data safety. Your Data safety answers should describe the same collection, sharing, and deletion practices.
The exact wording and placement can vary, but the user should not have to hunt through a support FAQ to find the option.
What does not count
These are common near-misses:
- A "deactivate" or "pause" button that keeps the account and data.
- A "contact support to delete" instruction with no in-app path.
- A web link that requires the user to log in with an account they are trying to delete.
- A form that says "we will review your request" but never deletes anything.
- A privacy policy that mentions deletion but no working mechanism.
- A Data safety form that says data is deleted when it is only hidden.
If the user cannot actually delete the account and the associated data, the flow is not doing the job.
The web deletion link
The web page should be public and reachable without the app. It should explain:
- what will be deleted;
- what may be retained, and for how long;
- how the user can request deletion;
- how they will be notified when it is done.
Put the same URL in the Play Console where account deletion details are requested. Test the link in a private browser window, without being signed in, to make sure it works.
Retention and legal exceptions
Some data may need to be retained for legal, tax, fraud-prevention, or security reasons. That can be legitimate, but it should be disclosed clearly. "We keep everything forever" is not a deletion policy; "we delete your profile and content, and retain transaction records for the period required by tax law" is.
Keep the explanation short and specific. Users do not need a legal treatise, but they do need to know what stays and why.
A quick checklist
- Users can find the deletion option in the app.
- The option deletes the account, not just the login session.
- The flow explains what is deleted and what is retained.
- There is a confirmation step.
- A public web deletion request page exists and works.
- The web link is entered in Play Console.
- The privacy policy describes the same process.
- The Data safety form matches the actual behavior.
- Deletion requests are actually processed.
The short version
If your app lets people create an account, give them a clear way to delete it. Provide an in-app path, a public web request page, a confirmation step, and an honest description of what is deleted or retained. Make sure the Data safety form and privacy policy tell the same story.
Next: the Google Play data safety form, explained, or does your app need a privacy policy?.
Our team’s note
If this answered the question but your situation still feels messy, send us the screenshot or the rejection email. Some things are easier to solve in a two-minute conversation than another article.