Answering the App Store Connect Privacy Questions

As part of the App Store Connect submission process, you will need to fill out Apple’s Privacy Practices Questionnaire where you will provide information about your app’s privacy practices, including the practices of third-party partners like Branch whose SDK code you integrate into your app.

Answering the App Store Connect Privacy Questions

You must select answers from the options presented in App Store Connect. Please keep in mind:

  • Branch’s SDKs are fully configurable by you, both in the data we collect on your behalf and how you use that data. Accordingly, you should identify all possible data collections and uses, even if not outlined here or even if certain data will be collected and used only in limited situations.
  • Your answers should follow the Apple App Store Review Guidelines and any applicable laws.
  • You are solely responsible for keeping your responses accurate and up to date. If your practices change, update your responses in App Store Connect.

Data Collection by Branch’s SDKs

You’ll need to confirm the types of data that you and/or your third-party partners including Branch collect from your app before answering the questions in App Store Connect.

Branch has provided a list of data types below that our services collect as further disclosed in our Privacy Policy. However, you will need to compare them to your custom configuration of the Branch SDKs and the data collection practices in your app to confirm whether your answers are accurate. Please also refer to Best Practices On How to Avoid Sending Branch PII.

  1. Contact Info: No
  2. Health & Fitness: No
  3. Financial Information: No
  4. Location: No
  5. Sensitive Information: No
  6. Social Information: No
  7. Contacts: No
  8. User Content: No
  9. Browsing History: Yes, Branch collects this data on your behalf
  10. Search History: No
  11. Identifiers: Yes, Branch collects this data on your behalf
  12. Purchases: Optional, Branch can collect this data on your behalf
  13. Usage Data: Optional, Branch can collect this data on your behalf
  14. Diagnostics: No
  15. Other Data: Yes; Branch collects this data on your behalf (e.g. device metadata features such as screen size and operating system version)

Data Use by Branch’s SDKs

You will need to have a clear understanding of how each data type is used by you and your third-party partners including Branch. Branch provides deep linking and attribution analytics services.

  1. Third-Party Advertising: No
  2. Developer’s Advertising: Yes
  3. Analytics: Yes
  4. Product Personalization: Yes
  5. App Functionality: Yes
  6. Other Purposes: None

Data Linked to the User

You’ll need to identify whether each data type is linked to a user’s account, device, or identity by you and/or your third-party partners. Data collected from an app is usually linked to the user’s account, device, or identity, unless specific privacy protections are put in place before collection to de-identify or anonymize it.

Please note, in using our services, Branch may provide the ability for you to associate the data it collects on your behalf with the resettable cookie and advertising identifiers. What associations the customer is capable of making (e.g. to a customer account or an identifiable individual) is unique to the customer and at its own discretion.


You’ll need to understand whether you and/or your third-party partners including Branch use data from your app to track users and, if so, which data is used for this purpose.

Branch collects user data to provide deep linking and attribution analytics services for app downloads and installs.

Privacy Links

You will have the ability to add links on your product page to your app’s privacy policy and your privacy choices documentation.

To learn more about Branch’s privacy practices and end user options, please see Branch’s Privacy Policy accessible here.

Updated 7 days ago

Answering the App Store Connect Privacy Questions

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.