App privacy label builder

Say what your app actually contains — an analytics SDK, crash reporting, ads, an account system — and get the data types you will most likely need to declare in App Store Connect, grouped the way Apple groups them, with the reason for each.

Why this is hard to fill in

Apple asks what data your app collects, and most developers answer for the code they wrote. But the form is about everything the binary does, including the SDKs you added and forgot. An analytics library collects a device identifier whether or not you call it; an ad network collects far more than that, and turns on tracking, which is a separate and heavier declaration. The gap between what you think your app collects and what it actually collects is where most incorrect labels come from.

Tracking is the answer that matters

Marking data as used for tracking means it is linked to third-party data for advertising or shared with a data broker, and it obliges you to ask for permission through App Tracking Transparency. Most analytics and crash SDKs do not require it. Most ad and attribution SDKs do. Getting this one wrong is the mistake with real consequences, so the tool calls it out separately rather than burying it in a list.

Where the mappings come from

Each entry here reflects what the SDK vendor documents about its own collection, as of the date shown against it. Vendors change what they collect, sometimes in a minor version, and your configuration changes it too: an analytics SDK with identifier collection switched off declares less than the same SDK with defaults. That is why this is a starting checklist and not an answer.

FAQ

Can I submit this as my answer?

No. Take it into App Store Connect as a checklist, confirm each line against the SDK's current documentation and your own build, and answer for the app you actually shipped.

My SDK is not listed.

Then check its privacy documentation directly. The list covers the common ones rather than pretending to be exhaustive.

What if I collect nothing myself?

You may still need to declare. If a third-party SDK in your binary collects it, it counts as collected by your app.

Is anything sent anywhere?

No. The decision table ships with the page and the logic runs in your browser.

Built by the GO AI team. All free tools