App Privacy Label
Every submission has to answer Apple’s privacy questionnaire, and the answers become a label on your product page. The usual mistake is answering for the code you wrote and forgetting the code you installed. Work through it here first — your answers stay in your browser.
This is not legal advice. It is a worksheet, not a determination — it cannot see your app, your SDKs or your network traffic, so every answer here is yours and depends on what you actually ship. The definitions are Apple’s and are linked; the responsibility for the declaration is yours.
Start here: the SDKs count as you
This is where most indie declarations go wrong. Data your third-party SDKs collect is data you have to declare — you added their code, so their collection is disclosed under your name.
“Third-party partners” refers to analytics tools, advertising networks, third-party SDKs, or other external vendors whose code you’ve added to your app.
— Apple, App privacy details on the App Store
Apple also warns that an SDK can use what it gathers for its own purposes, beyond what you added it for. Tick what you ship, then go and read each one’s privacy documentation — what it collects is in there, and it is not something this page can look up for you.
Categories, not products — what any particular SDK collects is in its own documentation and changes between versions, so naming vendors here would be guessing on your behalf.
What you collect
Apple’s 16 groups, with Apple’s own definitions. Include anything your third-party SDKs collect. Tick a group and two more questions open up — Apple asks about each type separately, and App Store Connect also asks how each one is used.
Contact Info
Information that identifies or reaches a person outside the app.
Health & Fitness
Health, medical and exercise data.
Financial Info
Payment details, creditworthiness and other financial information.
Location
Where the user is.
Sensitive Info
Racial or ethnic data, sexual orientation, pregnancy or childbirth information, disability, religious or philosophical beliefs, trade union membership, political opinion, genetic information, or biometric data.
Contacts
Other people's details — a contact list, address book or social graph.
User Content
Content the user creates or sends.
Browsing History
Content the user viewed that is not part of the app, such as websites.
Search History
Searches performed in the app.
Identifiers
IDs that can be used to identify the user, their account or their device.
Purchases
Purchases or purchase tendencies.
Usage Data
How the user interacts with the app.
Diagnostics
Technical data about how the app is running.
Surroundings
Scanning of the user's environment — mesh, planes, scene classification, image detection.
Body
The user's hand structure and movements, and head movement.
Other Data
Any other data types not listed above.
Your worksheet
How your answers group into the three headings the App Store shows on a product page. A type used for tracking appears under tracking and under linked or not linked — they are different questions, not a ranking.
Nothing ticked yet. Your summary builds as you work through the list above.
The 16 data types, the three product-page headings and the tracking and linked-to-identity definitions on this page are Apple’s, read from App privacy details on the App Store and the App Store’s own privacy definitions and examples, last checked on 2026-08-05. Nothing was added to Apple’s list, and where Apple’s wording is quoted it is quoted rather than paraphrased.
Apple also documents cases where disclosure is optional, and exceptions to what counts as tracking. Those are on Apple’s page and are not reproduced here — read them there rather than assuming either way from this worksheet.
Your answers are stored in this browser only. Nothing is uploaded, and this page makes no network requests of any kind.
Getting the listing itself ready? The ASO coach covers the title, subtitle and keyword field, and the release notes writer handles What’s New.