Apple App Privacy

What to indicate in Apple App Privacy when using Adapty SDK

Starting December 8, 2020, Apple requires a privacy disclosure for all new apps and app updates. Adapty is a third-party dependency to your app, therefore you’ll need to properly disclose the ways you are using Adapty in regards to user's data.

Data Types

✅ = Required
👀 = May be required (see details below)
❌ = Not required

Data Type Required Comment
Identifiers

If you are identifying users with a customerUserId, select 'User ID'.

Adapty collects IDFA, so you have to select 'Device ID'.

Purchases Adapty collects purchase history from users.
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.
Usage Data 👀 If you are using analytics SDK's such as Amplitude, Mixpanel, AppMetrica, or Firebase, this may be required.
Location Adapty does not collect precise location data.
Health & Fitness Adapty does not collect health or fitness data from users.
Sensitive Info Adapty does not collect sensitive information.
User Content Adapty does not collect content from users.
Diagnostics Adapty does not collect device diagnostic information.
Browsing History Adapty does not collect browsing history from users.
Search History Adapty does not collect search history from users.
Contacts Adapty does not collect contact lists from users.
Financial Info Adapty does not collect financial info from users.

Required Data Types

Purchases

When using Adapty, you must disclose that your app collects ‘Purchases’ information.

1. Purchase History

You should select at least the following options for 'Purchase History':

  • Selecting ‘Analytics’ ensures compliance for Adapty's dashboard features including Profiles/CRM and Charts.
  • Selecting ‘App Functionality’ ensures compliance for Adapty's receipt validation in order to prevent fraud.

📘

If you are using Adapty for any of the other options listed, such as collecting data for Third-Party Advertising, you will need to select those options as well.

After selecting the options for Purchase History, click ‘Next’.

2. Purchase History Linked to Identity

Apple will then ask if you are linking purchase history to a user’s identity. If you don't set customerUserId, and don't have a way to identify individual users, you can select ‘No’.

If you are using customerUserId that can be tied to a user’s email address or phone number, you should select ‘Yes’.

3. Purchase History User Tracking

Finally, to indicate if purchase history data will be used for tracking purposes, you will need to read Apple’s examples and determine if your app meets their definitions of tracking.

Adapty, as a third-party, doesn't use purchase history to track users across different apps for advertising.

Identifiers

If you are identifying users with customerUserId, you'll need to select 'User ID'.

Adapty collects IDFA, so you'll need to select 'Device ID'.

After making your selections, you'll need to indicate how the data is used similar to the Purchases section.

After making your privacy selections, Apple will show a preview of your app's privacy section. If you have chosen Purchases and Identifiers as described above, your app's privacy details should look something like this:


Did this page help you?