Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

Google Play says my Data safety form does not match my app

Short answer

The Data safety form must describe everything the app collects or shares, including data sent by third-party libraries and SDKs. Google does not check the form's accuracy at submission, but it can take action when behaviour and declaration differ. Find what the app really sends, correct the form and the privacy policy together, then resubmit.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • Play Console says my declared data practices do not match the app.
  • An update is blocked until I fix the Data safety section.
  • I answered 'no data collected', but the app has analytics, ads or login.
  • My developer filled in the form and I do not know what the answers were.
  • My privacy policy and the form tell different stories.

Why does this happen?

  1. Everything leaving the device counts

    Google defines collection as transmitting data off the user's device, including data sent by third-party libraries and SDKs. Data processed only on the device, or end-to-end encrypted so that you cannot read it, generally does not need to be disclosed.

  2. SDKs collect data the owner never thinks about

    Google states that collection and sharing by SDKs in your app must be reflected in your form, and you are responsible for third-party code complying with Play policies. It points to the SDK providers' own Data safety information and the Google Play SDK Index.

  3. The form is self-declared, but not unchecked

    You alone are responsible for complete and accurate declarations, and Google's review does not verify the form's accuracy. If Google finds a discrepancy between your app's behaviour and your declaration, it may take enforcement action.

  4. Apps with no data collection still need the form

    Apps that collect no user data must still complete the form and link a privacy policy. A privacy policy is required to complete the form.

  5. The app changed, the form did not

    A new feature, a new login option or a new analytics tool changes what is sent. If the form is left as it was, a mismatch is created by an update. Google states that if you misrepresented data you must correct the form, and apps that do not become compliant may face enforcement such as blocked updates or removal.

What can I do about it today?

  1. Read the exact message in Play ConsoleNote which data types or which practice it says is mismatched. Do not answer from memory.
  2. Get a list of every service the app talks toAsk your developer for the analytics, crash reporting, ads, login, payment and push services in the app, and what each receives.
  3. Open the current form and compareFor each data type, check collected or not, shared or not, required or optional, and purpose.
  4. Fix the form and the privacy policy togetherThe policy text and the form should say the same thing. Leaving one old causes the next flag.
  5. Do not tick 'no data collected' to passIf the app sends anything off the device, it is a wrong answer, and Google says it may take enforcement action.
  6. Keep a copy of the answers you submitA dated record helps the next update and any reply to Google.

When should I bring someone in?

  • You cannot tell what the SDKs in the app send.
  • The app also exists on the App Store and its privacy answers need to match.
  • Your update is blocked and you need the answers checked before you resubmit.

How do I handle it?

  1. List what the app actually sendsI inspect the app's dependencies and watch its network traffic in a test build, to produce a list of data types and destinations.
  2. Check each SDK against its own documentationFor each third-party library, I read the provider's published data information and note anything that applies to your app.
  3. Draft the answersI write a draft of each Data safety answer and the matching privacy-policy lines. You, or your adviser, approve them.
  4. Test the claimAfter the changes, I run the app again and confirm that nothing leaves the device that the form does not say.
  5. Add a check before each releaseA short checklist: did a dependency, permission or service change? If yes, the form is reviewed before upload.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Does Google check my answers when I submit?

Google states its review does not verify the accuracy of the form. It may take enforcement action if it later finds a discrepancy.

What happens if I do not fix it?

Google says apps that do not become compliant may face enforcement, such as blocked updates or removal from Google Play.

Do I need the form for an internal test build?

Google lists apps active only on internal testing tracks as exempt. Closed, open and production tracks are covered.

Is this the same as the Apple privacy questions?

They are separate forms with different wording. Answers should still agree, since the app does the same thing on both.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.