What do I answer on Apple's App Privacy questionnaire?
Every app that ships has to fill in App Privacy in App Store Connect, and the wording is vague enough that most developers guess. Toggle what your app actually collects below and get the exact ticks — plus whether you need an ATT prompt (almost certainly not).
Scope: this covers what an analytics SDK collects — specifically AppGlance, whose defaults are what the switches start on. If you also ship ads, crash reporting, a backend with accounts, or another analytics SDK, add their data types to whatever you tick here; the questionnaire is answered once for the whole app. Guidance, not legal advice.
Your answers
Analytics.track("paywall.viewed") — anything you name. Same declaration as
sessions, as long as you keep personal data out of event names and metadata.
purchase / trial.started with a product id counts as
Purchase History in Apple's questionnaire. Turn this on if you'll send them — many apps do.
setUserProperties(["plan": "pro"]) — anything you'd like to filter users by:
plan, cohort, goal. Not identity: an anonymous install can carry plan = pro. Declare the real data
type if one fits (a plan or tier is Purchases; a health goal is Health), otherwise Other Data.
identify(email:name:)
puts a name on the install. This is the switch that changes everything: from here on the data is
linked to a person.
identify(email:) — searchable, shown on the user's page.
identify(name:) — the label on feeds and the user page.
identify(id:) — an account id from your backend, so several installs line
up with one account.
This is how the App Privacy section of your App Store page will read. Flip a switch to see it change.
Tick exactly this in App Store Connect
The default answer set, in one paragraph
An app using a privacy-first analytics SDK and nothing else collects two things: Identifiers → User ID (a random per-install UUID, not the IDFA) and Usage Data → Product Interaction (sessions, screens, the events you track). Both go under Data Not Linked to You, purpose Analytics, used for tracking No. Data Used to Track You: None. That's the whole label. Add Purchases → Purchase History if you track purchase events.
What changes if you identify users
The moment an install carries an email, a name, or your own account id, everything about that install is tied to a person. In Apple's terms that is not "some of it is linked" — the whole set moves to Data Linked to You: your Contact Info appears there, and Product Interaction and the User ID move up with it. That is why the preview above empties the "Not Linked" section entirely when you turn identification on. It is still not tracking, and still needs no ATT prompt — linked and tracked are different questions.
Only send fields the person gave your app, and give them a way to be forgotten (in AppGlance, a per-user delete on the user's page erases every event and label for that install).
Why no ATT prompt is required
App Tracking Transparency — the "Ask App Not to Track" dialog — is required for tracking, and Apple defines that narrowly: linking your data with data from other companies' apps, sites or offline properties for targeted advertising or advertising measurement, or sharing it with a data broker. Collecting usage data about your own app, and keeping it to yourself, is not tracking.
✓ The three questions in order.
Do you collect data? Yes — say so honestly. Is it linked to the user's identity? Only if you attach an email, name, or account id. Do you use it to track? No — no ad identifiers, no data brokers, no cross-company linking. Answer "No" to the third and the ATT prompt is not required, whatever your answer to the second.
Two things that catch people out: an ad SDK anywhere in the app usually flips the tracking answer to Yes for the whole app, and so does sharing your analytics with an ad network for audience building. If you ship ads, your label is a different conversation from this page.
Country is not Location
A map of your users by country looks like location data and usually isn't. There is a real difference between where the device says it is (GPS, or an IP-address lookup — Location) and which region the user chose in Settings (a locale — not Location). AppGlance reads the region setting only, which is why the country toggle above adds nothing to the label. If your analytics derives country from the IP address, that is a different answer — ask your vendor which one they do.
Privacy manifests: the other half
Since 2024 Apple also expects a privacy manifest (PrivacyInfo.xcprivacy) — a file
that declares collected data types and the reasons you call certain APIs (things like UserDefaults),
and third-party SDKs on Apple's "commonly used" list must ship a manifest and a signature. This is separate
from the questionnaire on this page: the manifest is a file in your build, App Privacy is a form you fill in
once. A well-behaved SDK ships its own manifest so you only declare your app's own usage
(how AppGlance does it).
Want these answers generated from your real setup?
The dashboard's Setup tab shows the same preview for your actual app, and the SDK ships its own privacy manifest.
Written August 2026 against Apple's current App Privacy questionnaire. Apple's definitions are the authority and they change — when in doubt, read Apple's own App Privacy details page in App Store Connect. This is guidance, not legal advice.