What your Google Play account-deletion web page needs
Give people a working way to request account deletion after uninstalling the app, and connect that page to the process behind it.
By The Draftbit team · Updated
Sources checked
This guide is for Google Play phone and tablet apps enabling account creation in the app or directing people to an external account-creation flow, subject to policy exceptions.
Your in-app Delete account button works, but Play Console also wants a URL. That page serves people who no longer have the app. It needs to let them request deletion without reinstalling it.
Google’s account-deletion requirements call for a working, discoverable request route that names the app or developer as shown in the listing. A privacy policy can host it if the deletion section is prominent and actually leads to a request.
Build the page around the request
This is an outline to adapt to your real process, not a ready-made privacy policy:
| Page element | What to put there |
|---|---|
| Heading | ”Request deletion of your [app name] account” with your real app name |
| Request action | A working form, deletion link, or clearly explained support email route |
| Identity check | The information needed to identify and safely verify the account |
| Deletion scope | The account and associated data you’ll delete |
| Retained information | What remains, why, and your applicable retention periods |
| What happens next | Expected processing time and how the user gets confirmation or help |
Google permits a support email or form for this web route. Apple’s in-app rules differ, so keep the two stores’ deletion requirements separate.
We’d make the request action visible near the top. A visitor shouldn’t have to search a long policy to find out how to contact you.
Connect the request to deletion
Choose who receives requests, how they verify account ownership, and how they trigger backend deletion. Include data held by service providers and explain legitimate retention. If subscription cancellation or another step is needed, explain it and provide a support route.
The page must describe what you’ve implemented. A polished template doesn’t delete an account, and a form that sends to an unmonitored inbox leaves the user stuck.
Test it after uninstalling the app
Use a disposable account with sample data. Uninstall the app, open the deletion URL in a browser, and complete the request through the available web or support route. Confirm that identity verification can finish without reinstalling and that the request reaches the responsible person or system.
Follow it through to deletion and confirmation. Repeat on a mobile browser and check the exact URL entered in Data safety under App content. Save the form and complete any required review submission.
The in-app route is still required for covered phone and tablet apps. Google’s documented exemptions include permanently private and enterprise device-management apps; offline-only accounts are outside its app-account definition. Check those conditions before deciding the requirement doesn’t apply to you.
Official sources
We checked these instructions against the sources below. The console layout may change, and your review decision may call for different steps.
- Google account deletion requirements Checked 22 September 2026