By Will McCullough, DigiRune Studios ·
Who has to fill it in?
Every developer submitting to the App Store. Apple says the information is required to submit new apps and app updates, and it must cover the practices of third-party partners whose code you include. Account Holders, Admins and App Managers can enter the answers in App Store Connect.
What counts as "collecting" data?
In Apple's definition, collecting means sending data off the device in a way that lets you or your partners access it for longer than it takes to handle the request in real time. In practice:
- Processed only on the phone: not collected, nothing to declare.
- Sent to your server and thrown away right after the request: not collected.
- Stored on your server, in analytics, or by any SDK: collected, even if it is not for advertising.
- Web content: if your app loads web pages, declare what they collect; plain open-web browsing is the exception.
What about third-party SDKs?
Apple counts analytics tools, advertising networks, SDKs and other outside code you add as your third-party partners, and you must declare what they collect. In our experience, this is where most mistakes happen: a crash reporter, sign-in library or analytics package may collect device IDs or usage data you never touch yourself. Read each vendor's privacy documentation and include their collection in your answers. You are not responsible for data Apple itself collects, but data your app gets from Apple's frameworks and then collects still counts.
What does "tracking" mean?
Tracking has a narrow meaning on the label: linking data about a user or device from your app with data from other companies for targeted advertising or ad measurement, or sharing it with a data broker. Apple also counts an SDK that combines your users' data with other developers' apps for ad targeting or measurement, even if you do not use it for that. If you have no ads and no ad SDKs, the answer is often no, but check every SDK before you say so.
Linked or not linked to the user?
Apple treats collected data as linked to the user's identity unless you protect it before collection, for example by de-identifying it, and then never try to link it back or join it with other data that could identify the person. Anything that counts as personal information under privacy laws is treated as linked.
Can I leave anything out?
Only in narrow cases. Apple allows optional disclosure for data that meets every one of its criteria: not used for tracking, advertising, marketing or other purposes; collected only infrequently, outside the app's main purpose, and optional for the user; and entered by the user in a form that makes clear what is sent and shows their name or account name, with the user choosing to send it each time. If data meets some but not all of the criteria, you must declare it. Data collected on an ongoing basis after a one-time permission must always be declared.
Free-form text is a special case: you do not have to list everything a user might type in a notes field, but if you ask for a specific type of data, such as a phone number, you declare that type.
Keeping it accurate
- List every route data leaves your app by before you answer: your own server, analytics, crash reports, sign-in, email or feedback forms, file uploads and any AI service.
- Make sure your privacy policy, which Apple requires as a public URL, says the same thing as the label.
- Update the answers whenever your app or an SDK changes. Apple says you can change them at any time in App Store Connect, without submitting an app update.
Taking your app to the stores?
The DigiRune Studios Store Launch Kit is a step-by-step guide and checklist for getting through Apple App Store and Google Play review, built from the process we use for our own apps. Apple and Google make every approval decision; the kit helps you submit ready.
See the Store Launch KitSources
Store rules change. Check the official pages on the day you submit. Checked November 19, 2026.