Google Play Data safety and account deletion: what the policy asks of your app

Which apps must offer account deletion on Google Play?

Any app that lets users create an account from within the app, even if some features work without one. Accounts created and operated offline are not app accounts under the policy, permanently private apps and enterprise device management apps are exempt, and non-mobile apps do not have to start deletion from inside the app.

What must the in-app path and the web link do?

Inside the app, the path must be intuitive and prominent, for example within account settings. Outside it, you must provide a web link resource where users can request deletion of their account and associated data. The link must work, must reference the app or developer name as it appears on your Play listing, and must make the deletion request prominent and easy to find, with a support flow users can start.

When you delete an account on request, you must also delete the user data associated with it; 'temporary account deactivation, disabling, or freezing the app account does not qualify as account deletion'. You can also let users delete some data without deleting the account, and show them that you do.

What may an app keep after it deletes an account?

Google accepts that an app 'may need to retain certain data for legitimate reasons such as security, fraud prevention or regulatory compliance', but 'you must clearly inform users about your data retention practices'. The privacy policy itself must cover your data retention and deletion policy and give a privacy point of contact.

What goes into the Data safety form?

All developers with an app published on Google Play must complete it, across closed, open and production tracks; apps active only on internal testing are exempt. 'Collect' means transmitting data off the user's device; 'sharing' means transferring it to a third party. Data processed only on the device, transfers to service providers or for legal purposes, user-initiated transfers with prominent disclosure, and fully anonymised data have their own exemptions.

The form covers data handled by any third-party libraries or SDKs in your app, whether data is encrypted in transit, and whether users can request deletion. A privacy policy is required to complete it. Google says 'you are accountable for the information you provide', and apps that don't comply face enforcement such as blocked updates or removal.

When does an app need a prominent disclosure before asking for data?

When data use may not be within the user's reasonable expectation, such as collection in the background. The disclosure must be inside the app, not only in the store description, a website, the privacy policy or the terms; it must come immediately before the consent or permission request; and consent must take an affirmative action such as a tap or a tick. Moving away from the screen is not consent.

You are responsible for the SDKs you include, which must not sell personal and sensitive user data from your app, and the same requirements apply to third-party AI integrations.

Which permissions draw extra review?

Photos and videos: apps targeting Android 13 or later may request READ_MEDIA_IMAGES or READ_MEDIA_VIDEO only if their core functionality needs broad access to the user's media; others had to remove the permissions, with full compliance from 28 May 2025. Apps with custom pickers must submit a declaration explaining why the Android Photo Picker is not enough.

Contacts: Google announced a similar declaration for READ_CONTACTS on 15 April 2026. Play Console prompts apps to declare or remove it from September 2026, and compliance becomes mandatory on 27 January 2027 for apps targeting Android 17 (API level 37) and above.

What else blocks a first release in 2026?

Personal developer accounts created after 13 November 2023 must run a closed test with at least 12 testers opted in for at least 14 consecutive days before they can apply for production access. From 31 August 2026, new apps and updates must target Android 16 (API level 36); an extension to 1 November 2026 can be requested.

If parts of the app need a login, give reviewers the details, and use the 'Any other instructions' field for a one-time password or multi-factor sign-in. You must also declare whether the app contains ads, complete the content rating questionnaire (unrated apps may be removed) and declare the target age group.

Does Google take a cut when an app sells physical services?

No. Google Play's billing system is required for digital goods and services sold in the app, but not for payments that are primarily for physical goods or physical services, such as 'transportation services, cleaning services, airfare, gym memberships, food delivery'. Peer-to-peer payments and credit card or utility bill payments are also outside it.