Play Store Data Safety Form Helper
Published October 4, 2026 · Data categories snapshot: October 2026
Google Play's Data Safety section asks you to declare every data type your app collects or shares, whether each is required or optional, and whether the data is encrypted in transit and deletable on request. Getting it wrong is one of the most common reasons apps are rejected or flagged during review. Select the data types your app handles below, answer a few questions about each one, and this tool generates the exact declarations you need to enter in Play Console -- plus warnings for combinations that commonly cause rejections.
If your app does not collect or share any user data at all, you can declare "No" in Play Console and skip the rest of this form.
How to Use This Tool
Start by confirming your app collects or shares user data, then set your security practices -- whether all data is encrypted in transit and whether users can request deletion. Next, work through each data category (Location, Personal info, Financial info, and so on) and check every data type your app handles. For each selected type, choose whether it is collected, shared, or both, pick a purpose, and mark it as required or optional. Hit "Generate Data Safety Declarations" to see a plain-text summary of every answer you need to enter in Play Console, along with any warnings about combinations that commonly trigger rejections. Copy the output and walk through the Play Console Data Safety form field by field.
Why the Data Safety Form Matters
Every app published on Google Play must complete the Data Safety section. This is not a suggestion -- it is a hard requirement. Google displays your Data Safety declarations on your app's store listing, right below the screenshots, so users see exactly what data your app collects before they install it. If you leave the section blank, Google marks your listing with a "No info available" label that discourages downloads and can trigger additional review scrutiny.
The form itself asks you to declare every data type your app handles, organized into categories like Location, Personal info, Financial info, Health and fitness, Messages, Photos and videos, Audio, Files and docs, Calendar, Contacts, App activity, Web browsing, App info and performance, and Device or other IDs. For each data type, you state whether your app collects it (the data leaves the device to your server), shares it (the data is transferred to a third party), what the purpose is, whether it is required or optional, and whether users can request its deletion.
Getting the declarations wrong has real consequences. If your Data Safety form contradicts what your app actually does -- for example, you declare "no data collected" but your app includes Firebase Analytics -- Google can reject your app update, suspend your listing, or require you to fix the form before your next release goes live. The declarations must also be consistent with your privacy policy. If your privacy policy says you collect location data but your Data Safety form says you do not, that mismatch is a review flag.
The most common mistakes are not intentional -- they come from developers who add an SDK without realizing it collects device identifiers, or who mark a data type as "not shared" when a third-party advertising SDK is transferring it to an ad network. This tool helps by surfacing warnings for the combinations that most often cause problems, so you can fix them before submitting.
Frequently Asked Questions
What is Google Play's Data Safety section?
The Data Safety section is a required part of every Google Play listing. It lets you declare what user data your app collects, shares, and how it handles that data. Google displays these declarations on your store listing so users can review your data practices before installing. You fill it out in Google Play Console under App content, and it must be consistent with your app's actual behavior and your privacy policy.
What happens if I fill out the Data Safety form incorrectly?
Google reviews your Data Safety declarations against your app's actual behavior. If there is a mismatch -- for example, your app collects advertising identifiers but you declared no data collection -- Google can reject your app update, require you to correct the form, or in severe cases suspend your listing. Inconsistencies between the Data Safety form and your privacy policy are also flagged during review.
Do I need to declare data collected by third-party SDKs?
Yes. Google's policy requires you to declare all data collected or shared by your app, including data handled by third-party libraries and SDKs. If your app includes Firebase Analytics, that SDK's data collection must appear in your Data Safety declarations. Use the SDK Disclosure Generator to identify what each SDK collects.
What is the difference between "collected" and "shared" in the Data Safety form?
Data is "collected" when it is sent from the user's device to your server or a server you control. Data is "shared" when it is transferred to a third party -- for example, sending advertising identifiers to an ad network, or sharing analytics data with a third-party service. A single data type can be both collected and shared if your app sends it to your own server and also transfers it to a third party.
Does this tool replace the Play Console Data Safety form?
No. This tool helps you prepare your answers before you enter them in Play Console. It generates a plain-text summary of your declarations and flags common issues, but you still need to enter each answer in the actual Data Safety form in Google Play Console. Google changes the form's categories and requirements periodically, so always verify your answers against the current version of the form.
How often should I update my Data Safety declarations?
Update your Data Safety declarations whenever you change what data your app collects or shares. This includes adding or removing SDKs, adding new features that collect user data, or changing how you handle existing data. Google recommends keeping your declarations current with every app update. If you update your privacy policy, review your Data Safety form to make sure they still match.