App Privacy details / Data safety section
The store questionnaire about what data your app collects, printed on your listing as a privacy 'nutrition label' shoppers can read.
See it
What it is
Both stores make you fill in a questionnaire about what your app collects, and then print the answers on your listing as a scannable summary. Same idea, two different forms, and the categories do not line up. Apple's App Privacy details (the 'privacy nutrition label') asks you to sort each data type into three buckets: used to track you across other companies' apps and sites, linked to your identity, or not linked to you. Those words are Apple's own vocabulary. Google's Data safety section does not use them. It asks whether each type is collected or shared, the purpose, whether collection is optional, whether data is encrypted in transit, and whether users can request deletion. Filling one form does not fill the other; you answer both from the same audit but map them separately.
The answers must cover code you did not write. Your analytics SDK, ad network, crash reporter, and attribution library all collect on your behalf and all belong in the declaration. Apple layers on two related requirements that are conditional, not universal: a privacy manifest (PrivacyInfo.xcprivacy) with declared reasons when your code, or a bundled SDK, uses one of the required-reason APIs such as file timestamps, disk space, or UserDefaults, and stricter treatment for SDKs on Apple's published commonly-used list, which have to ship their own manifest and signature. An app that touches none of those APIs and bundles none of those SDKs is not obliged to invent a manifest. Google requires the Data safety form to be current at every release plus a reachable privacy policy URL.
Gotcha: this is a legally meaningful statement, not marketing copy. If the label says 'no data collected' while Firebase is quietly shipping device identifiers, you get rejected, or removed later after a store audit or a user report. The safe process is to audit the network calls and SDK list first, write the declaration from that, then make your privacy policy match word for word.
Ask AI for it
Audit this codebase and produce a filled-in privacy declaration for both stores. List every third-party SDK and every outbound network call, and for each one name the data types collected and the stated purpose. Then output two separate tables, because the two forms ask different questions. Table one maps to Apple's App Privacy categories: used to track, linked to the user, or not linked to the user, plus purpose. Table two maps to Google Play's Data safety categories: collected versus shared, purpose, whether collection is optional, encryption in transit, and deletion request support. Do not reuse Apple's wording in the Google table. Then flag any mismatch with the existing privacy policy text, and list which of my own API uses or bundled SDKs actually trigger a privacy manifest or required-reason declaration, saying which API or SDK triggers each one.