Google Play Account Deletion Policy for TWA Apps

Google Play enforces strict user data control guidelines to ensure transparency and privacy across all Android applications. One of the most critical requirements for developers is the User Data policy regarding account deletion. This policy dictates that any app listed on the Google Play Store that allows users to create an account must also provide a clear and easily accessible method to delete that account and all associated personal data.

For developers converting a Progressive Web App (PWA) into an Android app using a Trusted Web Activity (TWA), complying with this policy requires specific attention. Because a TWA is essentially a web application wrapped inside a native Android container, you must ensure that both your in-app web interface and your external web resources align with Google Play requirements to prevent sudden store rejections or policy violation warnings.

Understanding Google Play Account Deletion Rules

The Google Play account deletion policy is designed to give users complete control over their personal information. If your TWA app permits account creation via email registration, social logins, or third-party OAuth, you must adhere to two absolute requirements:

• In-App Deletion Path: Users must be able to discover and initiate the account deletion process from directly within the app settings or profile menu.
• Web-Based Deletion Path: You must provide a publicly accessible website link where users can request account deletion without having to open or reinstall your Android app.

It is important to note that simply providing a support email address or phone number to initiate deletion does not satisfy Google Play guidelines. The process must either be automated, or provide a clear, structured form that guides the user through the deletion request. Additionally, when an account is deleted, all associated personal and sensitive user data must also be wiped from your servers, unless you are legally required to retain specific financial or transaction histories.

Implementing the In-App Deletion Path Inside a TWA

Because your TWA app directly loads your PWA web app, implementing the in-app deletion path requires updates to your web application's user interface. You must design an intuitive setting inside your user profile or settings page that allows users to permanently delete their account.

When planning this interface, avoid relying on native Android dialogs or custom bridges, as a TWA should handle all operations on the web layer. Standard HTML and CSS forms are perfectly sufficient. Consider implementing the following flow within your web application:

First, place a highly visible button labeled "Delete Account" or "Close Account" inside your account settings panel. Do not bury this option deep within nested submenus. Second, implement a confirmation dialog that clearly explains what data will be permanently removed (for example, profiles, photos, and saved configurations). Finally, require user confirmation by asking them to re-enter their password or type a specific phrase before submitting the deletion request to your backend server.

Once the backend process is complete, clear all local cookies, IndexedDB records, and LocalStorage data within the client browser, then redirect the user back to your app's main registration or login screen.

Creating the Public Web-Based Deletion Portal

The web-based deletion path is a unique requirement that often catches web developers off guard. Google Play requires this link so that users who have already uninstalled your Android app can still exercise their right to delete their personal data without being forced to download the app again.

This link must be a standard, public URL that can be accessed from any desktop or mobile browser. You are required to submit this specific URL inside the Google Play Console, and it will be displayed publicly on your app's store listing. When constructing this portal, you have two primary implementation options:

The first option is a standard web login portal. If your PWA is fully responsive, you can point the link to your web app's standard login page, which immediately redirects the user to the account settings deletion interface after successful authentication.

The second option is a manual request form. If your application relies solely on app-specific storage, or if a user cannot log in via the web browser easily, you can host a simple, secure form where the user submits their registered email address, username, and a deletion request. You can then verify the request via a confirmation link sent to their email before deleting the account manually from your database.

Filling Out the Data Safety Form in Google Play Console

Once your in-app deletion flow and public web portal are active, you must update your app configuration in the Google Play Console. This step is mandatory, and your app updates will be blocked if the form is incomplete or inaccurate.

To configure your deletion settings, log into your Google Play Console account (which requires a one-off 25 USD developer registration fee). Navigate to the "App Content" section and locate the "Data Safety" form. Within the Data Safety wizard, you will be prompted to answer questions about your data collection practices and user options.

You must answer "Yes" to the question asking whether your app allows users to create an account. Once answered, a sub-section will appear where you must provide the exact URL of your public web-based deletion portal. You must also specify whether your deletion process deletes all user data immediately or if you support a temporary account deactivation feature alongside permanent deletion.

Compliance Checklist for TWA Account Deletion

Use the following checklist to verify that your TWA application complies with all Google Play account deletion rules before you submit your app build for review:

By implementing a robust account deletion path within your PWA and linking it correctly in your Google Play Console profile, you ensure your TWA app remains fully compliant with the latest security and privacy regulations, paving the way for a smooth publishing and update process.