Skip to main content

Privacy Manifests and Data Safety Forms for AI-Built Apps

By the OnlineAppCreator editorial team4 min read

Short answer

Apple requires a privacy manifest (PrivacyInfo.xcprivacy) declaring collected data, tracking domains and the use of required reason APIs, plus privacy nutrition labels in App Store Connect. Google Play requires the Data safety form. For AI-built apps, the reliable method is to have the coding agent produce a complete inventory of data flows, SDKs and APIs from the code, then have a responsible person verify it and fill in the declarations.

On this page
  1. What Apple requires
  2. What Google requires
  3. The inventory method
  4. Mistakes we see repeatedly
  5. Getting declarations right the first time

Privacy declarations are where AI-built apps are most likely to be inaccurate without anyone noticing. A coding agent adds an analytics package to measure a funnel, a crash reporter to debug a release build, or a third-party login to save time. Each addition can change what the app collects and with whom it shares data. Nobody updates the declarations, and the mismatch surfaces later as a rejection, a policy warning or a complaint. The fix is a repeatable inventory process, and the agent that introduced the complexity is also the best tool to document it.

What Apple requires

Apple has two related requirements. The privacy manifest is a file named PrivacyInfo.xcprivacy inside the app and inside third-party SDKs. It declares whether the app tracks users, which domains are used for tracking, which types of data are collected and for what purposes, and which required reason APIs the code uses, with an approved reason for each. Required reason APIs include categories such as file timestamp APIs, system boot time, disk space, active keyboards and UserDefaults. Apple enforces these declarations at upload, and builds that use such APIs without a declared reason can be rejected. SDKs on Apple's list of commonly used third-party SDKs must include their own manifests and signatures.

The privacy nutrition labels are answers you give in App Store Connect about data types, linkage to the user's identity and tracking. They are shown on your App Store page. Xcode can generate a privacy report from all manifests in the app, which is a useful starting point for the labels.

What Google requires

Google Play's Data safety form in the Play Console asks which data types are collected or shared, for what purposes, whether collection is optional, whether data is encrypted in transit and whether users can request deletion. Apps that let users create accounts must also provide account deletion inside the app and through a web resource. Google expects the form to reflect the app's behavior including third-party libraries, and it can act on discrepancies.

RequirementStoreWhere it livesInput from the code inventory
Privacy manifestAppleIn the app bundle and each SDKRequired reason APIs, collected data, tracking domains
Privacy nutrition labelsAppleApp Store ConnectData types, linkage, tracking
Permission purpose stringsAppleInfo.plistEvery permission with its real purpose
Data safety formGooglePlay ConsoleCollected and shared data, encryption, deletion
Sensitive permission declarationsGooglePlay ConsolePermissions in the merged release manifest

The inventory method

  1. Ask the agent for a full data map. For example: "List every network request the app makes, the endpoint, the fields sent and whether they contain personal data. List every third-party SDK, its version and its documented data collection. List every permission and every required reason API used, including in dependencies."
  2. Check dependencies, not just your code. Ask the agent to look at the resolved dependency graph and at the privacy manifests shipped with SDKs. On Android, inspect the merged release manifest.
  3. Map to categories. Have the agent map each item to Apple's data types and Google's data categories, with purpose and whether data is linked to the user.
  4. Verify as a human. A product owner or privacy contact confirms each line against the actual behavior and the privacy policy.
  5. Write the manifest and fill in the forms. The agent writes PrivacyInfo.xcprivacy; a person enters labels and the Data safety form.
  6. Make it a pull request rule. Any new SDK, endpoint or permission must update the data map in the same pull request.

Mistakes we see repeatedly

Declaring "no data collected" while a crash reporter sends device identifiers. Forgetting that a backend-as-a-service SDK collects usage data. Treating data sent to your own AI provider as "not shared" without checking the provider's terms. Missing purpose strings for photo library or camera access added late in development. Privacy policies written once by a generator and never updated. Each of these is easy to fix before submission and costly after a rejection or a complaint.

AI features add a specific question: what user content goes to a model provider? If prompts may contain personal data, reduce it before it leaves your system. Tools like Textwash Pro anonymize text with local machine learning before it reaches an AI system, which simplifies both your declarations and your GDPR position. Our article on GDPR compliance for AI-built apps covers the legal side.

Getting declarations right the first time

Treat privacy declarations like code: versioned, reviewed and updated with every release that changes data flows. When a reviewer asks a question, the data map lets you answer in minutes instead of days.

The privacy section is one of the most frequent reasons first submissions go back and forth. AppSubmitter.io supports teams with privacy labels, the Data safety form and the rest of the publishing process, including responses to reviewer questions, until the app is live. For the wider set of pre-submission checks, see the App Store submission checklist for Claude Code and Codex projects.

Frequently asked questions

Does a web app wrapped in a native shell need a privacy manifest?

Yes. The native app is what Apple reviews, so it needs a privacy manifest covering the wrapper's APIs and SDKs, and the labels must also reflect data collected by the web content.

Can an AI agent fill in the Data safety form for me?

It can prepare the answers from the code, but a responsible person should verify them and submit the form, because you are accountable for the accuracy of the declaration.

What happens if a required reason API is missing from the manifest?

Apple can reject the build at upload or during review. Declare each required reason API with an approved reason, including uses inside dependencies.

Want this done right, the first time?

OnlineAppCreator takes products from idea to operation. Tell us where you stand and get a concrete plan in a free 15-minute call.