Starting December 8, 2020, Apple requires a privacy disclosure for all new apps and app updates. You must complete the privacy questionnaire in the App Privacy section of App Store Connect. Apple’s official instructions are available here.

As OneSignal is a third-party service, it is your responsibility to accurately disclose what data you collect and how it’s used through OneSignal.

By default, OneSignal collects select in-app purchase data (Consumable) and usage data such as session activity and notification clicks. If you collect additional information via Data Tags, Outcomes, or custom integrations, you must disclose that as well.

Data types and their relevance to OneSignal

Use the following table to determine which data types you must disclose when using OneSignal:

✅ = Required when using OneSignal
💡 = May be required, depending on configuration
❌ = Not required when using OneSignal

Data TypeRequired?
Contact Info💡 If you collect personal identifiers (e.g., name, email) using Data Tags or Outcomes
Health & Fitness💡 If you collect health data via custom tags or Outcomes
Financial Info💡 If you collect financial data through tags or Outcomes
Location💡 Only if your app requests and collects location data, and sends it to OneSignal
Sensitive Info💡 If you collect sensitive user data (e.g., race, politics, biometrics) via tags or Outcomes
Contacts💡 If you upload address books or contacts via Data Tags
User Content💡 If you collect user-generated content through OneSignal
Browsing History❌ Not collected
Search History❌ Not collected
Identifiers✅ OneSignal assigns a unique OneSignal ID for each user (not linked to identity by default).
💡 If you link other IDs (e.g., email, alias), disclosure requirements may change.
Purchases✅ Consumable in-app purchase events are collected
Usage Data✅ Session counts, durations, and notification interactions are collected
Diagnostics💡 OneSignal does not collect crash or energy logs, but does collect metadata like device type, OS, network state, etc.

Required data disclosures in App Store Connect

Type: Purchases

If your app includes in-app purchases, you must report collection of ‘Purchases’ data.

Select Purchases data type

Purchase History

Mark ‘Analytics’ as a minimum. This enables OneSignal to provide dashboard features like Segments and Outcomes.

Select usage purpose for Purchases

If you use OneSignal for other purposes (e.g., personalization or app functionality), be sure to select those as well.

Linked to user identity?

If you’re only using OneSignal’s anonymous IDs and don’t associate them with identifiable users, you can select ‘No’.

If you link user data (e.g., email or name) via your backend or third-party tools, select ‘Yes’.

Indicate if purchase history is linked to user identity

Used for tracking?

OneSignal does not track users across other apps. Select ‘No’ unless you use third-party tools or integrations that perform tracking.

Indicate if purchase data is used for tracking

After saving, you should see a summary like:

Privacy summary showing Purchases

Type: Usage Data – Product Interaction

You must disclose collection of ‘Product Interaction’ under Usage Data.

Select Product Interaction data type

Product Interaction

Select ‘Analytics’ to reflect how OneSignal uses this data in Segments and Outcomes.

Select usage purpose for Product Interaction

If you use this data for other purposes, such as app functionality or personalization, include those as well.

Linked to user identity?

Same guidance as with Purchases — if anonymous, select ‘No’. If linked via user ID or contact info, select ‘Yes’.

Indicate if product interaction is linked to user identity

Used for tracking?

OneSignal does not use this data for tracking across apps. Select ‘No’ unless other SDKs or integrations do.

Indicate if product interaction data is used for tracking

You should then see this summary:

Privacy summary showing Product Interaction

Final review

After completing all sections, Apple will show a preview of your app’s privacy disclosure. If you correctly selected Purchases and Usage Data, it should resemble the following:

Final privacy details summary in App Store Connect

Ongoing compliance

If your data collection practices change — for example, if you add new tags, link identifiers, or update your SDK version — return to App Store Connect and update your disclosures accordingly.