OOmnistu

Blog / Startup Guides

Startup Guides

Google Play Data safety form and User Data policy: what an app team has to build and declare

Plan Google Play data declarations, privacy disclosures, SDK reviews and deletion flows using the platform's published policies.

OOmnistu
Reviewed 2026-11-16 · 10 min read

Google Play asks every app team two connected things: a Data safety form that shows users what the app collects, shares and protects, and compliance with the User Data policy that sets rules for the app itself. This article reads both Google pages and turns them into build and planning points. For publishing steps see our Play release tracks article, and for Apple's equivalent see our privacy labels article (the pages say the two platforms' categories differ).

Data safety form, step by step (read 15 Nov 2026)

What it is. Google says the Data safety section shows users, before install, whether and how an app collects, shares and protects data. Developers declare practices in a form in Play Console, and Google reviews it as part of app review. Google also says its review is not designed to verify that the declarations are accurate or complete, that only the developer has the information, and that the developer alone is responsible for them. When Google becomes aware of a discrepancy it may take enforcement action; the page's FAQ says apps that do not become compliant are subject to blocked updates or removal.

Who must complete it. All developers with an app published on Google Play, including apps on closed, open or production tracks; apps active only on internal testing are exempt, and the source also exempts system services and private apps. Apps that collect no data must still complete it and link a privacy policy. A privacy policy is required to complete the form. Google's FAQ says that what you submitted for Apple's privacy labels cannot simply be reused, because the Google form asks for additional and different information and its taxonomy may differ materially.

What counts as "collect". Transmitting data off the device, including by third-party libraries and SDKs (whether the data goes to you or to a third party) and from webviews you control; you do not declare webviews where users browse the open web. Data processed only on the device, and data sent off device but unreadable by anyone except sender and recipient because of end-to-end encryption (no intermediary, including you, can read it), need not be declared as collected. Pseudonymous data that can reasonably be re-associated with a user must be disclosed. Ephemeral processing (in memory only, no longer than needed for the real-time request) still goes in your form response but is not shown to users; Google says using data to build ad or user profiles cannot count as ephemeral.

What counts as "share". Transferring collected data to a third party: server to server, on-device transfer to another app (declare it even if nothing leaves the device), and via SDKs or controlled webviews. Not counted as sharing: transfers to a service provider processing on your behalf and on your instructions; transfers for legal purposes; transfers based on a user-initiated action the user would expect, or a prominent in-app disclosure with consent that meets Google's User Data policy; and fully anonymised data. Whether a particular transfer fits one of these exemptions is a judgement for the app owner and, for privacy law, counsel; we give no legal advice.

Optional versus required. Declare a data type "optional" only if every user, on every device and region, can choose to provide it, opt out, or opt in, and still use the app; if primary functionality needs it, declare "required".

Security and other declarations. Whether all collected data is encrypted in transit; whether users can request deletion of their data; an optional badge for committing to the Families policy (for apps with children as a target audience); an optional independent security review badge through Google's MASA programme (a lab assessment against OWASP MASVS, paid for by the developer; Google notes it may not verify the accuracy of your Data safety declarations); and an optional UPI badge for apps using India's Unified Payments Interface that have the accreditation. Do not claim a badge without meeting its conditions.

Data types and purposes. Google's page lists the categories you are asked about: location (approximate and precise, including location inferred from an IP address), personal info (name, email, user IDs, address, phone number, race and ethnicity, political or religious beliefs, sexual orientation, other), financial info (payment info, purchase history, credit score, other), health and fitness, messages (emails, SMS or MMS, other in-app messages), photos and videos, audio files, files and docs, calendar, contacts, app activity (app interactions, in-app search history, installed apps, other user-generated content, other actions), web browsing, app info and performance (crash logs, diagnostics, other), and device or other IDs (examples named: IMEI, MAC address, Firebase installation ID, advertising ID). For each type you give the purpose from: app functionality, analytics, developer communications, advertising or marketing, fraud prevention/security/compliance, personalization, account management.

Form steps. In Play Console, open App content > Data safety > Start. Answer whether the app collects or shares any listed type; if yes, confirm encryption in transit and the deletion option; select data types; answer usage and handling for each; check the store listing preview; submit (or save as a draft). Responses can be exported to CSV and imported from CSV for offline completion. Google says updates can take time to publish, with some apps subject to expanded review of up to 7 days or longer in exceptional cases, and that a changed section can take up to 7 days to reach all devices.

What Google's User Data policy asks for (as read 15 Nov 2026)

Transparency and SDKs. You must disclose how the app accesses, collects, uses, handles and shares user data, and limit use to the disclosed purposes. You must comply with applicable privacy and data protection laws. If you include third-party code such as an SDK, you must ensure it and its practices comply with Play policies; the page gives the example of making sure SDK providers do not sell personal and sensitive data, and says the same applies to third-party AI integrations.

Personal and sensitive data. Defined to include, among other things, personally identifiable information, financial and payment information, authentication information, contacts, device location, SMS and call data, health data, the list of other apps on the device, microphone and camera. If the app handles it, the policy says to: limit access, collection, use and sharing to app and service functions and purposes the user reasonably expects (ad use must follow Google's Ads policy); handle it securely, including modern cryptography such as HTTPS in transit; use runtime permission requests where available before accessing permission-gated data; and not sell it. "Sale" is defined as an exchange or transfer to a third party for monetary consideration, and a user-initiated transfer (for example a user sending a file to a third party) is not sale. Transfers to service providers and for legal reasons are allowed under the page's wording.

Prominent disclosure and consent. Where data use may not be within the user's reasonable expectation (the page's example is background collection while the user is not using the app), the in-app disclosure must: be inside the app, not only in the store description or on a website; appear in normal use without the user navigating to a menu; describe the data accessed or collected; explain how it is used or shared; not sit only in a privacy policy or terms of service; and not be bundled with unrelated disclosures. The consent request must come immediately after that disclosure, be clear, require an affirmative action such as a tap or ticking a box, not treat navigating away (back, home, tapping away) as consent, not use auto-dismissing messages, and be granted before the app collects or accesses the data. Apps relying on a legal basis other than consent, such as GDPR legitimate interest, must meet all applicable legal requirements and give appropriate disclosures, including the in-app ones this policy requires. The page gives a template sentence ("[This app] collects/transmits/syncs/stores [type of data] to enable [feature], [in what scenario]"). If an integrated SDK collects personal and sensitive data by default, Google may ask for evidence of compliance and the page says the developer must provide it within two weeks of the request (or a longer period if Google's request allows).

Specific restrictions. Never publicly disclose financial or payment data or government ID numbers; no unauthorised publishing of non-public contacts; security or anti-virus apps need a privacy policy that, with in-app disclosures, explains collection and use (we read only the start of that row); apps for children must use SDKs approved for child-directed services; persistent device identifiers (IMEI, IMSI, SIM serial) may not be linked to other personal and sensitive data or to resettable identifiers, except for telephony tied to a SIM identity and enterprise device management in device-owner mode, both with prominent disclosure. The App Set ID may be used for non-ads purposes such as analytics and fraud prevention, but not for ads personalisation or measurement, and not connected to advertising IDs or personal data for advertising purposes.

Privacy policy contents. Posted in Play Console and in the app. It must comprehensively disclose access, collection, use and sharing (not limited to what the Data safety form shows) and include: developer information with a privacy contact or inquiry mechanism; the types of personal and sensitive data and parties it is shared with; secure handling procedures; retention and deletion policy; and a clear "privacy policy" label. The entity on the store listing must appear in it, or the app must be named in it. Apps that access no personal data still need one. It must be on an active, public, non-geofenced, non-editable URL, not a PDF.

Account deletion. If the app lets users create an account, the page says users must be able to request deletion from inside the app and from an external web resource, and the web link goes in a designated Play Console field. When deleting, you must delete the associated user data; deactivating or "freezing" the account does not count. If some data must be kept for security, fraud prevention or regulatory reasons, say so clearly in the privacy policy. Broken or outdated deletion links appear on the page's "don't" list.

Consistency. The Data safety form must be kept up to date and be consistent with the privacy policy.

Planning notes (ours, not Google's)

Limits

Two Google pages. The Data safety page was mostly read in full; its FAQ, SDK table, CSV format details and payment-service answer were read only in part or not at all. The User Data page was read to the start of its EU/UK/Swiss section. Dates on the Data safety page refer to 2022 and are historical. We did not read the Ads, Families or Permissions policies here. Policies change; check before publishing. Privacy law and children's rules need counsel.

By Omnistu.

Sources

Previous
Does a small business need a mobile app? A decision guide