Apple App Privacy Labels: Filling Them In Correctly
Short answer: The App Privacy section in App Store Connect asks what data your app and the libraries inside it collect, whether that data is linked to the person, and whether it feeds tracking that follows people beyond your own product. To answer well, list every data type your app touches, including the ones that come from third-party software development kits, then mark each one for purpose and linkage. Do the inventory before you open the form, because most review problems come from a label that says less than the app actually does. Repeat the check whenever a release adds a new library.
Why the labels are harder than they look
Many owners treat the privacy questions as paperwork. The form, though, is a description of how your app behaves, and Apple's reviewers and customers read it as a promise. A label that leaves out analytics or crash reporting is not a small omission. It is a statement the app does not match, and that can slow an update or lead to a rejection.
The biggest trap is that most of the data does not come from your own code. An analytics kit, a crash reporter or a map widget sends information on your behalf, and those kits have their own collection rules. You have to account for them, even if you never wrote a line of their code.
Step 1: Inventory the data before the form
Create a worksheet with one row for each place the app sends or stores data. A short list is usually enough:
| Source | What it may collect | Who sees it |
|---|---|---|
| Sign-in | Email address, name, user ID | Your backend |
| Order form | Delivery address, phone number | Your backend and courier |
| Payments | Purchase history, payment identifier | Payment provider |
| Analytics kit | Device identifiers, screens viewed, app events | Analytics provider |
| Crash reporting | Device model, OS version, crash logs | Crash reporting provider |
| Map widget | Approximate location, search queries | Map provider |
Check each library's own privacy documentation, because the official list of what it collects is the only reliable source. If you cannot find it, ask the vendor in writing before you submit.
Step 2: Map each data type to Apple's categories
Apple groups data into categories such as contact info, identifiers, usage data, diagnostics, location and purchases. For every item in your worksheet, choose the matching category, then answer three questions:
- Is it collected? Anything sent off the phone counts as collected, even if you delete it moments later.
- Is it linked to the user? Linked means it can be connected to a person's account or identity. An anonymous crash log with no account attached may be unlinked, but an analytics event tied to a sign-in ID is linked.
- Is it used for tracking? Tracking means joining what your app learns with what a different company learns elsewhere, in order to target or measure advertising. Passing data to your own backend for your own use is not tracking.
Keep your answers consistent with your app's permission prompts and its privacy policy. A mismatch between the label and the policy is one of the commonest reasons for a question from review.
Step 3: A worked example
Suppose a small delivery booking app has sign-in, a booking form, a payment provider and an analytics kit. Here is how one row might look once completed:
- Contact info, email address: collected, linked to the user, used for app functionality, not used for tracking.
- Identifiers, user ID: collected, linked to the user, used for analytics and app functionality.
- Usage data, product interaction: collected, linked to the user if the analytics events carry the sign-in ID, not used for tracking.
- Diagnostics, crash data: collected, not linked if the crash reporter has no user ID attached, used for app functionality.
The exact labels depend on how each library is configured. If you change the analytics setup so that events no longer carry the user ID, the linkage answer may change too.
Step 4: Fill in the form
In App Store Connect, open your app, go to the App Privacy section and start the questionnaire. For each data type you marked as collected, enter the purpose and the linkage. Then review the summary page, which shows the public label that customers will see.
Press save only after you have read the summary, because the text customers see is the one that matters. Use plain wording where the form allows it.
Step 5: Keep it current
Every time you release a version that adds a library, changes a sign-in method, or starts collecting a new field, repeat the worksheet. Libraries are the most frequent cause of drift. An update to a crash reporter or analytics kit can add a new data type without any change in your own code.
Add a line to your release checklist: list the third-party libraries, read each one's privacy notes for recent changes, and update the label if any answer has moved.
Common mistakes
- Answering "no" because the app does not sell data. Collection and tracking are different questions. Collecting data for your own purposes still counts as collection.
- Forgetting third-party kits. The label describes everything the app ships, among them the libraries it bundles.
- Marking everything as not linked. An analytics event tied to a signed-in account is linked, whatever the vendor's marketing says.
- Leaving the label stale. A label that describes last year's app can cause trouble after an update.
Apple's privacy manifest
Apple also requires a privacy manifest for certain APIs and third-party software development kits. The privacy manifest is a file inside your app that declares the data and reasons behind particular APIs. It is not the same as the App Privacy label, but the two should describe the same app. Read Apple's documentation on privacy manifest files, and check that your vendors provide their own manifests, because a missing one can block a submission.
FAQ
Does the label have to match my privacy policy exactly?
It must not contradict it. The label is a compact summary, while the policy spells out the reasons in full. If the two disagree, fix the one that is wrong before you resubmit.
What if I do not know what a library collects?
Look for its privacy documentation first. If it is unclear, contact the vendor and request a list of data types in writing. Do not guess, because the answer becomes a public promise.
Is crash data always unlinked?
No. Crash data can become linked if you attach a user ID or account identifier to the report. Check the configuration rather than assuming the default is correct.
How often should I review the labels?
At least with every release that adds or updates a library, and once a year as a general check.
Share the sign-in method, payment provider and analytics tools in your build, and we will turn them into a finished App Privacy worksheet ready for submission: contact us.