Why every app needs one

The Data safety section on a store listing is how users learn what an app collects before installing. Even if you collect nothing, you must still submit the form under App content in Play Console and state that clearly.

The form, your privacy policy and the app's behaviour must agree. If review finds a mismatch, typical outcomes are required edits, blocked updates and, in serious cases, account consequences. This is part of listing quality, not paperwork.

Step 1: inventory what the app collects

Do not fill from memory. List what your own code collects and what each SDK collects. Typical sources: sign-in data, location, contacts, photos and files, device identifiers, crash logs, usage analytics, advertising IDs and payment info.

SourceCommon data typesEasy to miss
Your codeEmail, name, location, filesUser IDs in server logs
Analytics SDKDevice ID, events, session timeCollection enabled by default
Ads SDKAd ID, coarse locationSharing initiated by the SDK
Crash/performanceCrash logs, device infoUser data inside logs
Payments/loginPayment ID, third-party accountServer-side processing still counts
txt
Data type       Source        Collected  Shared  Purpose            Optional
Email address   Sign-up form  yes        no      Account management no
Crash logs      Crashlytics   yes        no      Analytics          no
Device ID       Ads SDK       yes        yes     Advertising        yes
Approx location —             no         —       —                  —

Also useful in this topic cluster:

Step 2: four questions per data type

  1. Collected? Data leaves the device and is processed by you or a provider
  2. Shared? Transferred to a third party; some service-provider processing is exempt per Google's definitions, so check them
  3. Purpose? App functionality, analytics, advertising, account management, security — choose actual purposes
  4. Optional or required? Whether users can decline to provide it

When unsure, declare conservatively and truthfully. Most review problems are not 'you collect data' but 'you collect it and did not say so'.

Step 3: security practices and deletion

You also declare whether data is encrypted in transit, whether users can request deletion and whether you follow certain commitments. Encryption in transit normally means HTTPS; fix any plaintext endpoints before ticking the box.

Apps with account creation must offer in-app account deletion and a web link for deletion requests. The link must work and explain how to request deletion, what is removed and what is retained. Mirror it in the privacy policy.

Consistency with the privacy policy

The policy must be a public HTTPS page covering every data type and purpose in the form, with contact details. Typical mismatches: the policy claims no personal data while an SDK collects device IDs, or the form declares location while the policy never mentions it.

Re-check the form every time you add or remove an SDK or ship a release. Make it a permanent item in your publish checklist.

If the form is flagged

  • Check every data type named in the notice, not only one
  • SDK updates often add collection; re-audit after dependency upgrades
  • Save changes and submit a new app version so Console re-evaluates
  • For deletion requirements, make the entry point work before updating the form

Xunda cannot appeal on your behalf and does not promise approvals. Verify account status before buying and run this reconciliation before listing.

Related reading:

Related

Related desks