Preparing for the App Store review—nutrition labels

For:
Marketers
Last update:

At a glance: Starting iOS 14 App developers must provide the App Store information related to their Privacy Practices when they submit an app. The App Store publishes the practices in the format of a nutrition label.

A word from our lawyers: Nothing stated here is legal advice. It is provided for your information and convenience. You should work closely with legal and other professional advisors to determine exactly how Apple policies apply to you. 

Nutrition labels and the App Store review

  • In order to generate the privacy labels, app developers must answer a questionnaire when submitting their app to App Store Connect that includes the following sections:
  • App developers:
    • Have full control over how to implement and configure the AppsFlyer software, what data to collect, and how the data is used.
    • May have very different answers to the questionnaire based on how they configure the AppsFlyer software and the data points they choose to collect.
  • According to the AppsFlyer understanding of the Apple policy, AppsFlyer doesn't track. That said, App developers must respond to the questionnaire in accordance with their specific uses and partner integrations. 
  • If you do use collected data for tracking purposes, you must implement the ATT prompt. 
  • The following assumes AppsFlyer software default configurations. App developers are responsible for ensuring that they adapt accordingly in line with their specific configurations and uses.  

Data types collected 

Data type

AppsFlyer data collection 

Remarks

Contact information

  • Name
  • Email address (including hashed)
  • Phone number (including hashed)
  • Physical address
  • Other user contact info 

No

Contact information should not be collected. However, if you have configured your app to transmit hashed emails or hashed phone numbers, respond accordingly in the App Store questionnaire.

Fitness

No

Don't collect

Financial info

  • Payment info
  • Credit info
  • Other financial info

No

Don't collect

Location info

  • Precise location
  • Coarse location


See remarks
  • Precise location: No
  • Coarse location: Yes. The IP address is collected and mapped to a coarse geographic location. 

Sensitive info

No

Don't collect

Contacts

No

Don't collect

User content

  • Emails or text messages
  • Photos or videos
  • Audio data

No

Don't collect

Browsing history

No

Don't collect

Search history

No

Don't collect

Identifiers

  • User ID
  • Device ID (IDFA)

Optional
  • User ID: App developers may set and transmit user ID (CUID) 
  • Device ID: The Advertising ID (IDFA) is collected only when accessible.

Purchases

  • Purchase history

Optional

App developers can choose to configure certain in-app purchase events to measure.

Usage data

  • Product interaction
  • Advertising data
  • Other usage data 
  • Yes
  • Optional
  • No
  • Product interactions: App launches are measured, as well as any other user interaction configured by the app developer.
  • Advertising data: is received if the app developer uses the AppsFlyer ad revenue module.

Diagnostics data

  • Crash data
  • Performance data
  • Other diagnostics data

 

  • No 
  • Yes
  • No

Launch time and/or battery levels may be received for fraud detection.

Other data 


  • Other data types
  • IDFV

Yes
  • Technical device information (for example, OS, device type, language, screen size, etc.) or network information (for example, IP address, HTTP user agent) is received by AppsFlyer.
  • AppsFlyer applies an install ID to each app install called the AF ID.
  • IDFV is collected

Data use purposes

Apple has a list of purposes from which app developers must choose, as detailed in the table that follows. You must identify the relevant purposes for each data type related to your specific use.

Data purpose

Selection based on how data from AppsFlyer will be used

Third-party advertising

Select if you share the data type with a third party for the purpose of displaying third-party ads in your app.

Developer’s advertising or marketing

Select if you use to display first-party ads in your app (including if sharing with a third party to display your ads) or for other marketing purposes.

Analytics

Yes 

Product personalization

Select if you use data for any product personalization.

App functionality

Yes

Other purposes 

Select if you use the data for any purpose not otherwise stated.

Data linked to an identity

Data types collected through AppsFlyer are typically connected to an identifier like device ID (when available), or other identifiers like customer-issued IDs when configured.

Therefore, app developers should select Yes when asked if the data is linked to an identity.

See also