If an AI tool chose your SDKs, you may not know what's in your app. The stores still expect an accurate answer, and they hold you responsible for it, not the tool. The good news is that it's a finite job: find out what's in there, look up what each piece collects, and write it down.
What each store asks for
- Apple asks for App Privacy details in App Store Connect, for new apps and updates. It covers data collected by you and by third-party code you include, and you need a public privacy policy URL.
- Google asks for the Data safety form for any app on a closed, open or production track, even one that collects nothing. Only apps on internal testing are exempt. A privacy policy is required here too.
Find out what's actually in your app
Start with package.json. Each dependency that talks to a server is a question to answer. These are the usual suspects in AI-built apps, and the kind of data each one tends to handle:
- Sign-in and databases like Supabase, Firebase or Clerk: email addresses, account IDs, and whatever your users save
- Analytics and crash reporting like PostHog, Amplitude or Sentry: usage data, device details, crash logs
- Payments like Stripe or RevenueCat: purchase history and billing details
- Notifications like OneSignal or Firebase Messaging: device tokens
- AI APIs like OpenAI or Anthropic: whatever your users type or upload
That's a starting point. Your setup decides the real answer, so check each provider's own documentation. For Android, Google points to providers' published Data safety guidance and the Play SDK Index.
“Collected” isn't quite the same on both stores
Apple counts data sent off the device in a way that you or your partners can access for longer than it takes to handle the request. Data processed only on the device, or discarded straight after the request, doesn't need declaring.
Google counts anything your app sends off the device, including through its SDKs and through webviews your app controls. Data held only briefly in memory can stay off the listing, but you still note it in the form. Sending data to a service provider working only on your behalf isn't counted as sharing.
If your app is a wrapped website, that webview line matters. Analytics scripts and trackers on your site count as your app collecting data on Google Play.
AI features need their own consent
This one catches a lot of AI-built apps. Apple's guideline 5.1.2 says you have to disclose when personal data goes to third parties, third-party AI included, and get explicit permission first. In practice that means a clear screen before the first AI request saying what gets sent and to whom, with a real choice.
Account deletion comes with it
If people can create an account in your app, both stores want a way to delete it.
- Apple requires deletion inside the app, easy to find, usually in account settings.
- Google requires an in-app path and a web link that works without reinstalling the app, and you enter that link in the Data safety form.
Deleting has to remove the data too, not just sign the person out. If you keep anything for legal or fraud reasons, say so in your privacy policy.
A short checklist
- Every dependency that talks to a server is on your list
- Each one is matched to the data it handles
- Your site's trackers are counted, if the app is a wrapper
- AI features ask first, and say what gets sent
- Your privacy policy says the same thing as your forms
- Account deletion works, and removes the data
Then keep it true. Apple lets you change your answers at any time without a new build, and expects you to when your practices change. The next time an AI tool adds an SDK for you, this list needs another look.
Sources
We check these before publishing. If something here has gone stale, tell us.
