Build With RevenueCat

Build a customized mobile subscription business with RevenueCat. We do the heavy lifting of normalizing subscribers from any source and maintain a single source of truth for subscription status, so you can get back to building your app.

RevenueCat is a powerful, secure, reliable, and free to use in-app purchase server with global support. All you need to get started is an API key.

Get Started    REST API Endpoints

Apple App Privacy

How to fill out the questionnaire

Starting December 8, 2020, Apple requires a privacy disclosure for all new apps and app updates. As RevenueCat is a third-party to your app, you’ll need to ensure you are properly disclosing to your users the ways you are using RevenueCat in regards to their data.

Data Types

✅ = Required when using RevenueCat
💡 = May be required when using RevenueCat
❌ = Not required when using RevenueCat

Data Type

Required?

Contact Info, including name or email address

💡 If you use subscriber attributes to collect identifiable contact information including name, email address, or phone number

Health & Fitness

❌ RevenueCat does not collect health or fitness data from users

Financial Info

❌ RevenueCat does not collect payment information from users

Location

❌ RevenueCat does not collect precise or coarse location data, only locale and currency code

Sensitive Info

❌ RevenueCat does not collect sensitive information including racial or ethnic data, political opinions, or biometric data from users

Contacts

❌ RevenueCat does not collect address books or contact lists from users

Browsing History

❌ RevenueCat does not collect browsing history from users

Search History

❌ RevenueCat does not collect search history from users

Identifiers

💡 If you are identifying users with a custom app user ID, you will need to select 'User ID'

💡 If you are using integrations that utilize an advertising identifier, like IDFA, you will need to select 'Device ID'

Purchases

✅ RevenueCat collects purchase history from users

Usage Data

💡 If you are using analytics SDK's such as Mixpanel, Firebase, or Amplitude, this may be required

Diagnostics

❌ RevenueCat does not collect device diagnostic information

Required Data Types

Type: Purchases

If you are using RevenueCat, you must disclose that your app collects ‘Purchases’ information from the App Privacy tab in App Store Connect.

1. Purchase History Usage

At the bare minimum, you must select the following options for 'Purchase History':

All RevenueCat users must select these two options.

  • Selecting ‘Analytics’ ensures compliance for RevenueCat’s dashboard features including Customer History, Charts, and Experiments.
  • Selecting ‘App Functionality’ ensures compliance for RevenueCat’s receipt validation in order to prevent fraud, as well as enabling features via Entitlements.

📘

Additional Selections

If you are using RevenueCat 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 these options for Purchase History, click ‘Next’.

2. Purchase History Linked to Identity

Apple will now ask if you are linking purchase history to a user’s identity. If you are using RevenueCat’s anonymous app user ID’s, and do not have a way to identify individual users, you can select ‘No’.

If you are using an app user ID that can be tied to a user’s email address or other contact information via your own server or other third-parties, 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.

RevenueCat, as a third-party, does not inherently use purchase history to track users across different apps for advertising. If you are using integrations or other SDK’s that do this, you may need to disclose that here.

Type: Identifiers

If you selected 'Yes' to linking purchase history to a user's identity, you will likely need to disclose which user identifiers you use in your app.

If you are identifying users with a custom app user ID, you will need to select 'User ID'.

If you are using integrations that utilize an advertising identifier, like IDFA, you will need to select 'Device ID'.

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

What's Next

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 privacy details should look something like this:

If you're ready to submit your app to App Review, head over to our Launch Checklist doc for more information about preparing your app for submission.

Updated 4 months ago


Apple App Privacy


How to fill out the questionnaire

Suggested Edits are limited on API Reference Pages

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