What the two forms are
Google Play’s Data safety form is in Play Console under App content. You list every type of user data your app collects or shares, why, whether it is encrypted in transit and whether users can ask for it to be deleted. Google shows the answers as the Data safety section on your store listing.
Apple’s App Privacy details, the “nutrition label”, are in App Store Connect. For each data type you say whether it is linked to the user’s identity, whether it is used for tracking and for which purposes. Apple shows the result on your App Store page.
Both stores expect the same truth, described with different categories. That is why the tool gives you two separate summaries.
Collected, shared and ephemeral: Google’s definitions
- Collected means the data is sent off the user’s device, by your code or by any library or SDK in the app. Data that is processed only on the device does not count, which is why
shared_preferences,local_author a photo picked but never uploaded add nothing. - Shared means the data is transferred to a third party. Sending it to a service provider that processes it on your behalf and on your instructions is not sharing, and neither are transfers for legal reasons, transfers the user starts and expects, or fully anonymised data.
- Processed ephemerally means the data is held only in memory and kept no longer than needed to serve the request. You still declare it as collected, but you can mark it as ephemeral. Data used for advertising or to build a profile can never be ephemeral.
The exact wording is in Google’s Data safety help article. Apple defines collect slightly differently, as data sent off the device and kept longer than needed to serve the request in real time, and adds its own rules forlinked to the user and tracking on its App privacy details page.
SDK data counts as your data
Both stores make you responsible for what third-party code does. If Crashlytics uploads stack traces, AdMob reads the advertising ID or RevenueCat stores purchase history, your app collects that data, even if you never look at it. Google’s Play SDK Index and the vendors’ own disclosure pages are where you check, which is what each card in the tool links to.
Common mistakes
- “No data collected” with Firebase in the app. Analytics, Crashlytics and Cloud Messaging all send identifiers and diagnostics. A form that says no data while those SDKs are present is wrong.
- Forms that do not match the privacy policy. The policy, the Data safety form and Apple’s labels must describe the same data. Reviewers compare them.
- Not updating after adding an SDK. A new ads, analytics or payments SDK means new answers in both consoles before you release the update.
- An “invalid Data safety form” rejection. Google may find, for example, that your app sends the advertising ID or location while the form does not mention it. Apps that stay out of line can have updates blocked or be removed. Fix the form, then resubmit.
- Forgetting your own backend. Email addresses, profile names and user posts on your server are data you collect, whatever SDKs you use.
How to use the tool
- Paste your whole
pubspec.yaml, or tick packages from the list. Onlydependenciesare read; dev dependencies never ship in the app. - Tick what your own backend stores: email, name, phone, user content, location or purchases.
- Read each package card. Items marked “only if” depend on how you configured the SDK, for example Crashlytics user IDs or RevenueCat customer attributes.
- Read the third-party services group and add what each vendor’s own disclosure lists, then check any packages marked “not recognised”, such as your own local packages.
- Copy the checklist and work through Play Console and App Store Connect. Then write a privacy policy that says the same thing.
Limits
- It is not legal advice, and it cannot see your code. It only knows what each vendor documents for the SDK by default and the options they describe.
- SDK behaviour changes between versions and with configuration. Every package shows the date its sources were checked; read the linked docs for the version you ship.
- Where a vendor publishes guidance for only one store, the tool says so, and some packages say “check the SDK’s docs” rather than guess.
- Permissions are listed only where the package documents them.
For what the policy itself must contain, see app privacy policy requirements for the App Store and Google Play.
Questions
Does my app need a Data safety form if it collects nothing?
Yes. Every app on Google Play must complete the form, even if the answer is that it collects and shares no user data. Apple asks the same question in App Store Connect.
Is Firebase data “shared” with Google?
Usually not, for most Firebase products: Firebase processes the data for you as a service provider, and Google’s definition says that is not sharing. Ads SDKs and features such as Google Analytics data sharing settings are different, which is why the tool marks them “check”.
Do I declare data that never leaves the device?
No. Location used only on the device, photos that are never uploaded and biometric checks do not count as collected. They still need permission prompts with clear usage descriptions.
Is my pubspec sent anywhere?
Your pubspec and answers are not saved or sent. The tool is JavaScript running in this page. The only request it makes is to pub.dev’s public API, with the names of packages that aren’t in our own lists, so it can read their descriptions.
Shipping a Flutter app and want the store forms right the first time? I’m Muhammad Naeem, a Flutter developer with 10+ apps live on the stores. Tell me about your project.