Complete the Flutter app privacy details in App Store Connect and the Data safety form in Google Play Console, and make both match what the code actually does. Apple and Google ask different questions, so one set of answers rarely fits both stores without adjustment.
Key takeaways
- Apple's App Privacy details and Google Play's Data safety form ask overlapping but not identical questions.
- Your declarations must cover data collected by your own Dart code and by every plugin and native SDK in the build.
- Answers should come from a written data inventory, not from memory or from the privacy policy alone.
- Both forms need a fresh review whenever a dependency, data flow or tracking feature changes.
What does Apple ask in App Privacy details?
Apple asks you to declare the data types your app collects, whether each type is linked to the user, and whether any of it is used for tracking. You enter these answers in App Store Connect, and they appear on your App Store product page as privacy labels.
The declaration covers collection by you and by third-party partners whose code runs inside your app. An analytics or crash reporting SDK therefore counts, even if you never wrote a line of tracking logic yourself. Apple's own explanation of the categories and definitions is the reference to check before you answer, at Apple's App privacy details page.
Tracking has a specific meaning on Apple's platform: linking data about a user with data from other companies' apps or websites for targeted advertising or measurement. If your app does not do this, do not declare tracking. If it does, the tracking prompt must be part of the app flow, and the label must say so. The same Apple page explains where the boundary sits.
What does the Google Play Data safety form ask?
The Data safety form asks which data types your app collects or shares, why it uses each type, whether data is encrypted in transit, and how users can request deletion. Google Play requires this form for apps, and the answers appear in the Data safety section of your store listing.
Google separates collection from sharing. Collection means data is transmitted off the device to you or to a service provider acting for you. Sharing means transfer to a third party for that party's own purposes. Data that is processed only on the device generally falls outside collection, which matters for Flutter apps that cache data locally. The definitions are set out in Google's help article on the Data safety section, and you should read them before filling in the form.
Where your app creates user accounts, the deletion questions need concrete answers. Describe the in-app path a user follows, and state what is deleted and what is retained for legal reasons. Vague wording such as 'on request' tends to create follow-up questions during review.
How do the two declarations differ?
The two forms cover similar ground, but Apple centres its questions on linkage and tracking, while Google centres its questions on collection, sharing and security practices. A single answer set usually needs rewording for each store, even when the underlying facts are identical.
| Criterion | App Store privacy details | Google Play Data safety form |
|---|---|---|
| Where answers appear | Privacy labels on the App Store product page | Data safety section on the Play Store listing |
| Core concept | Data linked to the user, and tracking across other companies' apps and sites | Data collected, and data shared with third parties |
| Security practices | Not the central focus of the label | Asks about encryption in transit and deletion options |
| Third-party code | Partner collection counts toward your declaration | Third-party collection counts toward your declaration under Google's definitions |
| Maintenance | Update in App Store Connect when practices change | Update in Play Console when practices change |
The practical consequence is that a checklist for one store is not a complete checklist for the other. Teams that maintain a single master inventory and map it to each form avoid most of the drift between them.
How do Flutter plugins change your answers?
Every plugin and native SDK in your build can collect data on your behalf, so your declarations must describe the combined behaviour of your code and its dependencies. Assuming a plugin is harmless because it is popular is the most common source of incomplete answers.
Privacy manifests and third-party SDKs
Apple expects commonly used third-party SDKs to ship a privacy manifest that describes the data they collect and the reasons for certain API usage. Your app has its own manifest as well, and the two should be consistent. Read Apple's privacy manifest files documentation before you rely on a vendor's claims about its SDK.
Auditing the dependency list
List every package in pubspec.yaml, along with the native dependencies pulled in through the iOS and Android build files. For each one, record what it sends off the device, to whom, and whether it can be disabled or configured. A plugin that sends nothing off the device is a different case from one that sends identifiers to a vendor's servers.
How do you complete both forms step by step?
Start from a data inventory, answer the Apple questions in App Store Connect, answer the Google questions in Play Console, and then compare both against your privacy policy and the in-app consent flow. The order matters, because answering from the store interface first tends to produce answers that describe the interface rather than the data flow.
- Build a data inventory: list each data type, its source, its purpose, where it is stored and who receives it.
- Mark which items leave the device and which are linked to an identifier or to a user account.
- Answer the App Privacy questions in App Store Connect, and confirm the tracking status against the actual code.
- Answer the Data safety questions in Play Console, including sharing, encryption in transit and deletion options.
- Compare both declarations with your privacy policy and with the consent screens the app actually shows.
- Record the build version that the answers describe, so the next release can be checked against it.
Apple's App Review Guidelines also require apps that allow account creation to offer account deletion inside the app. Check the current text of the guideline before you submit, because the wording of your deletion flow and your privacy answers must agree.
Hypothetical examples of mismatched declarations
Here are two hypothetical scenarios:
Scenario one: a fictional habit-tracking app adds a crash reporting SDK in a minor release. The developer copies the answers from the previous version and does not notice that the SDK sends device identifiers off the device. Both declarations now understate what the app does, and the inventory review step in the checklist above would have caught the change.
Scenario two: a fictional retail app offers sign-in with an email address only. The Apple answers list contact details, but the Play form marks account data as not collected, because the developer thought of the account as a login rather than as stored data. Both forms need the same correction, and the mismatch only becomes visible when the two answer sets are compared side by side.
Where does this approach fail?
The approach fails when the inventory goes stale, when third-party code changes without notice, or when a team treats the forms as a legal sign-off. The forms describe practice. They do not replace a review of the obligations that apply to that practice.
A detailed inventory takes real effort, and that effort is the main trade-off. A lighter inventory is faster to maintain but misses data that a plugin sends silently. Self-declared answers also depend on the accuracy of the people completing them, so a second reader who knows the code is worth the time. A mismatch between the two stores or between the forms and the privacy policy can delay review or lead to a rejection, and it is much cheaper to find during preparation than after submission.
Do GDPR obligations change what you declare?
Yes, where personal data of people in the EU is processed, the GDPR sets obligations on transparency and on how data may be processed, and the store forms should reflect the same facts as your privacy notice. The regulation text is the reference for those duties, and the store forms do not replace it.
The General Data Protection Regulation applies to processing in the context of an establishment in the EU, and to processing that targets people in the EU. Its principles include transparency and data minimisation. The full text is available on EUR-Lex, under Regulation (EU) 2016/679.
This article is general information and not legal or tax advice. Rui Codex provides technical implementation support for apps and integrations, not legal, tax or compliance advice. For a broader view of security and data protection engineering, see the Rui Codex security and GDPR articles.
Where your Flutter app is a product built for a client, the technical work of mapping data flows to store declarations is often part of a custom software development project. Readers planning a Flutter build can also review the Flutter app development service page for the scope of that work.
Frequently Asked Questions
Do I have to fill in both App Privacy details and the Data safety form?
Yes, if you publish on both stores, each one requires its own declaration. Apple reads the answers in App Store Connect and Google reads them in Play Console, so one form does not satisfy the other. Use the same data inventory for both, then adjust the wording to each store's definitions and keep both aligned with your privacy policy.
Does a Flutter plugin's data collection count toward my answers?
Yes, data collected by plugins and native SDKs in your build generally counts toward your declarations, because the stores ask about the app as shipped. List every dependency in pubspec.yaml and the native build files, then check each vendor's privacy documentation. If a plugin sends data off the device, record it, even if you did not write the call yourself.
Can I leave the Data safety answers blank if my app collects no data?
No, Google Play requires the Data safety form for apps, so you must complete it even when the honest answer is that no user data is collected or shared. Answer accurately about data that stays on the device and about any third-party code in the build. An inaccurate form creates a mismatch that a later review can flag, so check the answers against the current build before each release.
How often should I update these declarations?
Update them whenever data handling changes, such as a new SDK, a new data type, a change in sharing or a new tracking feature. Do not wait for the next scheduled release cycle. Treat both forms as part of the release checklist, and keep a dated record of each version's answers so that later reviews can be answered quickly.
Conclusion
Apple's App Privacy details and Google Play's Data safety form ask related questions in different ways, and both must describe what your Flutter app and its dependencies actually do. Build the data inventory first, answer each store from it, and recheck both forms whenever a plugin or data flow changes. To discuss a technical review of your app's data flows, request a project consultation at https://ruicodex.com/Contact or email info@ruicodex.com. Rui Codex is led by a founder with 200+ projects delivered, and published case studies are at https://ruicodex.com/CaseStudies.
Sources
- App privacy details - Apple Developer
- Privacy manifest files - Apple Developer Documentation
- App Review Guidelines - Apple
- Provide information for Google Play's Data safety section - Google Play Help
- Regulation (EU) 2016/679 (General Data Protection Regulation) - EUR-Lex, Publications Office of the European Union