Apple requires a privacy disclosure for all new apps and app updates both in the App Privacy section of App Store Connect and as the app manifest file. Adapty is a third-party dependency to your app, so you need to disclose how you use Adapty in relation to user data.

Apple app privacy manifest

The privacy manifest file, named PrivacyInfo.xcprivacy, describes what private data your app uses and why. You as every app owner must create a manifest file for your app. Additionally, if you’re integrating any extra SDKs, ensure the manifest files for those of them included in the SDKs that require a privacy manifest and signature list are included. When you build your app, Xcode will take all these manifest files and merge them into one.

Even though Adapty isn’t on the list of SDKs that require a privacy manifest and signature, versions 2.10.2 and higher of the Adapty SDK include it for your convenience. Make sure to update the SDK to get the manifest.

The manifest only feeds the privacy report that Xcode generates. App Review checks your answers in App Store Connect, so complete that section in full.

If you identify users with Adapty’s customerUserId, declare the user ID in your manifest file:

1. Add a dictionary to the NSPrivacyCollectedDataTypes array in your privacy information file.
2. Add the NSPrivacyCollectedDataType, NSPrivacyCollectedDataTypeLinked, and NSPrivacyCollectedDataTypeTracking keys to the dictionary.
3. Add string NSPrivacyCollectedDataTypeUserID (identifier of the UserID data type in the List of data categories and types to be reported in the manifest file) for the NSPrivacyCollectedDataType key in your NSPrivacyCollectedDataTypes dictionary.
4. Add true for the NSPrivacyCollectedDataTypeLinked key. Add false for the NSPrivacyCollectedDataTypeTracking key, unless you use the user ID for tracking as Apple defines it.
5. Use the NSPrivacyCollectedDataTypePurposeAppFunctionality and NSPrivacyCollectedDataTypePurposeAnalytics strings as the values for the NSPrivacyCollectedDataTypePurposes key in your NSPrivacyCollectedDataTypes dictionary.

If you target your paywalls to audiences with custom attributes, consider carefully what custom attributes you use and if they match the data categories and types to be reported in the manifest file. If so, repeat the steps above for every data type.

After you report all data types and categories you collect, create your app’s privacy report as described in Apple documentation.

Apple app privacy disclosure in App Store Connect

1. In App Store Connect, open your app and go to App Privacy. Click Get Started.

   

2. Select Yes, we collect data from this app and click Next.

   

Data types

The table below lists data types that Apple requires you to disclose and indicates which ones Adapty needs. This only covers Adapty. If your app collects additional data through other SDKs or your own code, select those data types as well.

✅ = Required by Adapty

👀 = May be required (see details below)

❌ = Not required by Adapty — select if your app collects this data through other means

Data type	Required	Note
Identifiers	✅	Adapty generates a device ID for each install and collects IDFV, so you have to select ‘Device ID’. If you are identifying users with a customerUserId, select ‘User ID’.
Purchases	✅	Adapty collects purchase history from users.
Usage Data	✅	Adapty records app opens and paywall and flow events on the user’s profile, so you have to select ‘Product Interaction’.
Contact Info, including name, phone number, or email address	👀	Required if you pass personal data like name, phone number, or email address using updateProfile method.
Location	❌	Adapty does not collect precise location data. Select if your app collects it.
Health & Fitness	❌	Adapty does not collect health or fitness data. Select if your app collects it.
Sensitive Info	❌	Adapty does not collect sensitive information. Select if your app collects it.
User Content	❌	Adapty does not collect user content. Select if your app collects it.
Diagnostics	❌	Adapty does not collect diagnostic data. Select if your app collects it.
Browsing History	❌	Adapty does not collect browsing history. Select if your app collects it.
Search History	❌	Adapty does not collect search history. Select if your app collects it.
Contacts	❌	Adapty does not collect contact lists. Select if your app collects it.
Financial Info	❌	Adapty does not collect financial info. Select if your app collects it.

Adapty also collects the device model, OS version, locale, time zone, App Store storefront, and user agent. These don’t match any Apple data type, so you don’t need to declare them.

Required data types

Purchases

When using Adapty, you must disclose that your app collects Purchase History.

Identifiers

When using Adapty, you must disclose the following identifiers:

• Device ID — Adapty generates a device ID for each install and collects IDFV. It also collects IDFA, unless you disable IDFA collection. You can’t turn off the per-install device ID, so declare Device ID in all cases.
• User ID — required if you identify users with customerUserId.

Usage Data

When using Adapty, you must disclose that your app collects Product Interaction. Adapty records app opens and paywall and flow events on the user’s profile.

Data usage

After saving Data types, you’ll need to indicate how the data is used:

1. Click Set up purchase history inside the Purchases block.

   

2. When Apple asks how purchase history data is used, select the following for Adapty:

   • Analytics — Adapty uses purchase history for revenue analytics, cohorts, and metrics.
   • Product Personalization — Adapty uses purchase data for audience segmentation and paywall targeting. This applies only if you target placements by audience, but selecting it is the safe default.
   • App Functionality — Adapty validates purchases, manages access levels, and tracks subscription status.

   Select additional purposes if your app uses purchase data in other ways (for example, if you send purchase events to ad platforms via Adapty integrations).

   

3. Click Next.

4. For both Device ID and User ID (if used):

   1. Click Set up user/device ID inside the User/Device ID block.

   2. When Apple asks how identifier data is used, select the following for Adapty:

      • App Functionality — Adapty uses identifiers to manage user profiles, link purchases, and track access levels.
      • Analytics — Adapty uses identifiers to count users and attribute events to them in analytics.

      If you send attribution data to third-party platforms via Adapty integrations (such as AppsFlyer or Adjust), also select Third-Party Advertising. Select additional purposes if your app uses identifiers in other ways.

   

5. Click Next.

6. For Product Interaction, when Apple asks how the data is used, select Analytics for Adapty.

Linking and tracking

For each data type, Apple also asks whether the data is linked to the user’s identity and whether it’s used for tracking. For Adapty, answer as follows:

• Linked to the user: No, if you don’t set customerUserId. The device ID is a random identifier generated for each install, and nothing in it identifies a person. If you set customerUserId, answer Yes for every Adapty data type, because the user ID links all of them to the user.
• Used for tracking: No. Adapty doesn’t use this data for tracking as Apple defines it. Answer Yes only if your app uses the data for tracking.