How to Prepare App Store Privacy Nutrition Labels
To fill in App Store privacy labels, first build an inventory of all the data your app collects. That includes data collected by its third-party SDKs, not only by your own code. For each data item, record why you collect it, whether it is linked to the user's identity and whether it is used for tracking. Then map each row to Apple's data types and purposes, and use that inventory to answer the privacy questions in App Store Connect.
The labels are only as accurate as your inventory. Most of the work happens before you open the form.
This guide covers the practical preparation. It is not legal advice. If you are unsure about your obligations under privacy law, ask a qualified adviser.
What do App Store privacy labels actually ask?
The privacy section in App Store Connect asks a set of questions about each kind of data your app collects. Apple groups data into categories such as contact information, health and fitness, financial information, location, user content, identifiers, usage data and diagnostics. Each category contains more specific data types.
For each data type you declare, Apple asks:
- What purpose the data serves, such as app functionality, analytics, product personalisation or third-party advertising.
- Whether the data is linked to the user's identity.
- Whether the data is used to track the user across apps and websites owned by other companies.
Your answers appear on the product page as a summary that users read before downloading. Check Apple's current developer documentation for the full list of categories, types and definitions, because these can change.
Why start with a data inventory and not the form?
The form asks yes-or-no questions one category at a time. Answering from memory tends to miss data collected by SDKs, by your backend and by features added since the last release.
An inventory gives you one place to:
- See every data item, its source and its destination.
- Agree on answers with developers, product owners and whoever manages your SDK vendors.
- Update the labels when a release changes what the app collects.
- Reuse the same facts for Google Play. Our guide to preparing Google Play Data Safety answers uses the same groundwork.
How do you build the inventory?
Work through each source of data in turn.
Your own app code. Go through every screen and feature. Note form fields, uploads, location requests, contacts access, camera and microphone use, and anything stored on your servers. Your mobile app user flows make a useful checklist here.
Your backend. List what the server logs or stores when the app calls it. That can include IP-derived location, account identifiers and request history.
Third-party SDKs. List every SDK in the build: analytics, crash reporting, advertising, payments, login, push notifications and attribution. For each one, read the vendor's privacy documentation and check which features you have switched on. Our guide on evaluating third-party mobile app SDKs explains how to review vendors before you add them.
Permissions. Compare the permissions the app requests with the data you have listed. A permission with no matching row usually means something is missing. See designing mobile app permission requests for related decisions.
Analytics events. If you have a tracking plan, go through each event and its properties. Event properties often contain identifiers or user content that nobody thought to declare.
What should the inventory template look like?
Use one row per data item per source. The worked example below is illustrative and describes a hypothetical booking app.
| Data item | Source | Apple category and type | Purpose | Linked to user | Used for tracking | Optional for user |
|---|---|---|---|---|---|---|
| Email address | Sign-up form | Contact info: email address | App functionality | Yes | No | No |
| Precise location | Map screen | Location: precise location | App functionality | Yes | No | Yes |
| Crash logs | Crash reporting SDK | Diagnostics: crash data | App functionality | No | No | No |
| Screen views | Analytics SDK | Usage data: product interaction | Analytics | Yes | No | No |
| Device advertising identifier | Advertising SDK | Identifiers: device ID | Third-party advertising | Yes | Yes | Yes |
| Booking history | Backend | User content: other user content | App functionality | Yes | No | No |
Add columns for the owner who confirmed each row, the date it was last checked and a link to the SDK documentation you relied on. These make the next review faster.
How do you decide "linked" and "tracking" correctly?
These two columns cause most of the uncertainty.
Linked to the user. Data counts as linked when it is connected to an account, a user ID or anything else that identifies the person. Data sent with a persistent identifier is often linked even if you never store a name. Apple treats data as unlinked only when direct identifiers are removed before collection, and you must not link it back to the person afterwards.
Tracking. Apple defines tracking as linking data collected from your app about a user or device with data from other companies, for targeted advertising or advertising measurement, or sharing that data with a data broker. Advertising and attribution SDKs are the usual source. If your app tracks, Apple also requires you to ask the user's permission through its App Tracking Transparency framework. Your label and your permission request need to match.
When you are unsure, ask the SDK vendor in writing and keep the reply with the inventory.
How do you enter the answers in App Store Connect?
Once the inventory is agreed, filling in the form is mostly copying.
- Open the app's privacy section in App Store Connect.
- State whether the app collects data. If any row in your inventory involves collection, the answer is yes.
- Select every data type that appears in your inventory.
- For each type, select every purpose, and answer the linked and tracking questions from your columns.
- Review the preview of the product page summary, and compare it with your inventory row by row.
- Publish the answers before you submit the build for review.
Keep a copy of the final answers alongside the inventory so you can see what changed at the next release.
When should you update the labels?
Review the inventory whenever a release:
- Adds or removes an SDK, or upgrades one in a way that changes what it collects.
- Adds a feature that collects new data or uses a new permission.
- Changes the purpose of existing data, for example starting to use usage data for personalisation.
- Changes your backend logging or retention.
Add a privacy check to your release checklist, as you would for the Google Play release checklist. Plan it as part of routine app maintenance after launch.
What common mistakes should you avoid?
Declaring only your own code. SDKs collect data on your behalf, and their collection belongs on your label.
Relying on default SDK settings. Check which features are switched on in your build, not what the vendor's marketing page describes.
Marking data as unlinked because you never see names. Persistent identifiers can make data linked.
Leaving out data users choose to provide. Data a user enters by choice is still collected. Apple allows a narrow exception for some infrequent, user-initiated data, so check its criteria before you leave anything out.
Letting labels and Data Safety answers drift apart. Answer both from the same inventory so the two stores tell the same story.
Treating the label as a one-off task. It goes stale with the first release that changes collection.
When does this approach not apply?
If your app genuinely collects no data, the inventory is still useful because it shows how you reached that answer. It will be very short.
This guide also does not cover your privacy policy wording, consent requirements under specific laws or contracts with vendors. Those need input from a qualified adviser.
What questions do founders often ask?
Who should own the privacy inventory?
Give it to one person, usually the product owner, with developers confirming the technical rows. Shared ownership with no named lead tends to leave rows unchecked.
Do I need to declare data that only stays on the device?
No. Apple's guidance says data processed only on the device is not collected and does not need to be declared. Anything you derive from it and send off the device counts separately. Record such items in the inventory anyway, with a note explaining why they are not declared.
Can the same inventory serve Android and iOS?
Yes, with one row per platform where the SDKs or features differ. Google Play uses its own categories, so add a column for the Data Safety mapping.
Can you help prepare labels for our app?
We prepare store submissions as part of app launch work. See our services or contact us to discuss your app.