You can find the complete breakdown of the data which is natively collected by Batch in this guide.
To help you fill in the App Privacy details the information required by Apple, we sorted this data using categories provided by Apple in their documentation: developer.apple.com/app-store/app-privacy-details/#data-type.
Data type | Data use | Linked to user’s identity | Used for tracking purpose |
Location |
|
|
|
Coarse Location* | Product Personalization
Analytics
Developer’s Advertising or Marketing | Yes | No |
Precise location ** | Product Personalization
Analytics
Developer’s Advertising or Marketing | Yes | No |
Identifiers |
|
|
|
User ID *** | Product Personalization
Developer’s Advertising or Marketing | Yes | No |
Device ID **** | Product Personalization
Developer’s Advertising or Marketing | Yes | No |
Usage Data |
|
|
|
Product Interaction | Product Personalization
Analytics
Developer’s Advertising or Marketing | Yes | No |
Advertising Data | Product Personalization
Analytics
Developer’s Advertising or Marketing | Yes | No |
Other Data |
|
|
|
Other Data Types | Product Personalization
Analytics
Developer’s Advertising or Marketing | Yes | No |
* Batch uses IP geolocation to guess the city of your users, it doesn't rely directly on location data coming from the device or the app itself.
** Precise location is only shared with Batch if it's enabled in your app, and explicitly sent to Batch. Batch doesn't collect it by default, even if users share their precise location with the app. More information is in our documentation.
*** Declare User ID if you set a Custom User ID linked to a user account (usually, when users log in to the app).
**** IDFA and IDFV collection can be disabled, more information in our documentation.
For example, this is what will be filled for "Coarse location":
⚠️ This information relates to the data natively collected by Batch. If you decide to send other custom data to Batch, or you send other data to other tools, you will also have to declare it to Apple.