Free tool, no account

What do I answer on Apple's privacy questions?

Every app has to fill in App Privacy in App Store Connect before it can ship, and the wording is vague enough that most developers guess. Tick what your app actually collects and this page writes your answers for you, including whether you need the tracking pop-up. You almost certainly do not.

Short answer

If analytics is the only thing you added, you tick two boxes: Identifiers (a random id per install) and Usage Data (sessions and the events you track). Both go in the Data Not Linked to You box, the purpose is Analytics, and Used for Tracking is No.

That means no App Tracking Transparency pop-up. Build your own answers below, then copy them into App Store Connect.

What this covers: the data an analytics SDK collects, using AppGlance as the example, which is what the switches start on. You answer the questionnaire once for the whole app, so if you also ship ads, crash reporting, a login system or a second analytics tool, add their data types to whatever you get here. This is guidance from developers who fill this form in, not legal advice.

The three boxes Apple asks about

Your App Store page shows the answers in three groups. Almost all of the confusion comes from mixing up the first two, so here is what each one actually means, and where a normal analytics setup lands.

Data Used to Track You

Your data gets joined with data other companies collected, to target ads, or gets sold to a data broker. This is the one that triggers the pop-up.

✓ Empty for analytics

Data Linked to You

Data that sits next to a real identity: an account, an email address, a name. Only applies if you choose to send one.

✓ Empty by default

Data Not Linked to You

Collected, but there is no name on it. A random install id and what happened in the app.

← Your two ticks go here

Being in the third box is the goal. It is the shortest thing you can say while still saying "yes, we collect something", which is the honest answer for any app with analytics.

Build your answers

Switch on whatever your app does. The card on the right is a preview of how your App Store page will read, and it updates as you go.

Start from a common setup:

The exact ticks, in order

Open App Store Connect next to this and work down the list. Anything not mentioned here stays un-ticked.

Paste it into a ticket, a checklist, or your privacy policy notes.

Three common setups, side by side

Most apps look like one of these. Find yours, and you have your answer without touching a switch. Each card is the real preview, generated from the same rules as the tool above.

Notice what happens in the third card: as soon as one email address is attached, the middle section fills up and the bottom section empties out. Nothing was added to what the app collects; it just stopped being anonymous.

The default answer, written out

An app that uses privacy-first analytics and nothing else collects two things. Identifiers, then User ID, which is a random id made up for that install and has nothing to do with the advertising identifier. And Usage Data, then Product Interaction, which is sessions, screens and the events you track. Both go under Data Not Linked to You, the purpose is Analytics, and used for tracking is No. Data Used to Track You: None. That is the whole label. Add Purchases, then Purchase History if you track purchase events.

If you attach a name or an email

The moment an install carries an email address, a name, or your own account id, everything about that install is tied to a person. Apple does not treat this as "some of it is linked". The whole set moves into Data Linked to You: Contact Info shows up there, and the User ID and Usage Data rows move up with it, which is why the preview above empties the bottom section completely when you turn identification on.

It is still not tracking and it still needs no pop-up. Being linked to a person and being used for tracking are two different questions, and Apple asks them separately.

Two rules if you do it: only send details the person actually gave your app, and give them a way to be forgotten. In AppGlance that is a delete button on the user's page, which erases every event and label for that install.

Why there is no tracking pop-up

The "Ask App Not to Track" dialog is required for tracking, and Apple's definition of that word is much narrower than the everyday one. It means joining your data with data collected by other companies' apps or websites in order to target or measure ads, or handing user data to a data broker. Counting what happens inside your own app and keeping it to yourself is not tracking.

1 Do you collect any data at all? Say yes and be honest. Sessions and events are data. Yes

2 Is it linked to a person's identity? Only if you attach an email, a name, or your own account id. Either answer is fine. Usually no

3 Do you use it to track? No ad identifiers, no data brokers, nothing joined with other companies' data. No

✓ No ATT prompt required Question three is the only one that decides this. Your answer to question two does not change it.

Three questions, asked in this order. Answer "no" to the third and the pop-up is not required, whatever you answered to the second.

Two things catch people out. An ad SDK anywhere in the app usually flips the tracking answer to yes for the whole app, not just for that SDK. So does sharing your analytics with an ad network to build audiences. If you ship ads, your label is a different conversation from this page.

A country map is not location data

A map of your users by country looks like location data, and usually is not. It depends entirely on how the map gets built, and there are only two ways to do it.

From the region setting AppGlance's default

The country the user picked in Settings, next to their language and date format.

The device already knows itNothing is measured or looked up.

The SDK reads "NO" or "DE"A two-letter code, the same one your app uses to format dates.

Nothing appears on your labelA language preference is not location data, so there is no extra tick.

From the IP address AppGlance, if you opt in

The server guesses the country from the network address the request came from.

The server sees an IP addressIn the EU an IP address counts as personal data.

It gets looked up in a databaseThis produces a rough physical location.

Location goes on your labelA different answer, and a longer one.

Same map on screen, different answer on the form. Ask your analytics vendor which of the two they do, because the tick depends on it and nobody puts it on the pricing page. AppGlance ships on the left and lets you move to the right per app, the wizard rewrites your label answers when you do.

The same answers, for Google Play

If you ship the same app on Android you fill in Data safety in the Play Console, which asks almost the same questions in a different order and with different words. The good news is that your answers carry over. Here they are translated.

One difference worth knowing. Google asks two extra things Apple does not: whether data is encrypted in transit (yes, everything goes over HTTPS) and whether users can request deletion (yes, if your analytics has a per-user delete, which AppGlance does). Google also asks whether each item is required or optional; analytics data collected automatically counts as required.

The privacy manifest, which is a different thing

Since 2024 Apple also wants a privacy manifest, a file called PrivacyInfo.xcprivacy inside your build. It lists the data types you collect and your reasons for calling certain Apple APIs, things like UserDefaults. Third-party SDKs on Apple's "commonly used" list have to ship a manifest and a signature of their own.

This is separate from the questionnaire on this page. The manifest is a file you ship; App Privacy is a form you fill in. A well-behaved SDK brings its own manifest so you only have to declare what your own app does, which is how AppGlance handles it.

Want these answers generated from your real setup?

The dashboard's Setup tab shows this same preview for your actual app, and the SDK ships its own privacy manifest.

Start free Read the quickstart

Written August 2026 against Apple's current App Privacy questionnaire and Google's current Data safety form. Apple's and Google's own definitions are the authority and they change, so when in doubt read the App Privacy details page in App Store Connect. Guidance, not legal advice.