Understand how to accurately disclose your use of OneSignal in your iOS app to comply with Apple’s App Privacy requirements. Learn which data types OneSignal collects and how to report them in App Store Connect.
Data Type | Required? |
---|---|
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. |
Select Purchases data type
Select usage purpose for Purchases
Indicate if purchase history is linked to user identity
Indicate if purchase data is used for tracking
Privacy summary showing Purchases
Select Product Interaction data type
Select usage purpose for Product Interaction
Indicate if product interaction is linked to user identity
Indicate if product interaction data is used for tracking
Privacy summary showing Product Interaction
Final privacy details summary in App Store Connect