Google Play · Data Safety
Keeping your Data Safety form and your privacy policy in agreement
Google Play's Data Safety section is a form you fill in the Console; your privacy policy is a document you publish. They describe the same thing in two formats, and a mismatch between them is one of the more common rejection reasons after a missing URL.
Where the two disagree in practice
The form says you collect location; the policy never mentions it. The policy discloses a third-party analytics SDK; the form's "shared with third parties" toggle is off. Each SDK you add after launch is a policy update and a form update, and it is easy to remember one and not the other.
Why this is a form, not free text
Play Console structures Data Safety as fixed categories — location, financial info, messages, and so on — each with its own sharing and purpose fields. Your policy is prose. The mismatch this guide is about is between what the form's checkboxes say and what your prose actually discloses.
The order that avoids the mismatch
Answer what your app actually does once, in one place, and derive both the form answers and the policy language from it — rather than writing the policy from memory and the form from a different memory weeks later.
Apple has the same problem, with a different form
App Privacy details in App Store Connect ask the same underlying questions in Apple's own vocabulary. An app on both stores usually keeps three documents in sync by hand: two forms and one policy.
What to check before you submit
- Every data type the form lists as collected is mentioned in the policy.
- Every third-party SDK you ship (analytics, ads, crash reporting) is disclosed in both.
- Data shared with third parties matches in both places, not just what is collected.
- The form and the policy were both updated the last time you added an SDK.
Questions
- Does Google actually compare the two, or is this a theoretical risk?
- Both automated checks and manual review compare a Data Safety declaration against what the app and its policy actually say. A mismatch is a documented, common rejection reason.
- Can Lanpage fill in the Data Safety form for me?
- Lanpage derives suggested answers to both Google's and Apple's forms from the same facts you already answered about your app, so you copy consistent values into each console instead of re-deriving them by hand.
- What if I genuinely do not know what an SDK collects?
- Check the SDK's own documentation before guessing. A field left open with a stated reason is safer than a wrong answer on a form you signed.
One set of answers, not two
Answer the wizard once and read off consistent suggestions for both Play's Data Safety form and Apple's App Privacy details.
Free. No card.
We help you publish and maintain your legal and support pages. We are not a law firm and we do not guarantee regulatory compliance.