AppPush
WebPush
WhatsApp
Email
SMS
OTP
Apple App Store Privacy Requirements
Starting December 8, 2020, Apple will require all new apps and app updates to provide privacy information. You will need to answer app privacy questions in the "App Privacy" section of App Store Connect. Apple's guidance can be found here. Since EngageLab is a third-party for your app, you need to ensure you disclose to users how you are using EngageLab to process their data.
EngageLab only collects certain usage data (clicks and session duration) for iOS apps. If you set up and collect any other data types through tagging or results, you will need to disclose those additional data types.
When filling out your privacy details, please review the following data types.
Data Types
Data Types ✅ = Must Disclose 💡 = May Need to Disclose ❌ = Do Not Need to Disclose
| Data Type | Requirement |
|---|---|
| Contact Info | ❌ EngageLab does not collect identifiable user contact information |
| Health & Fitness | ❌ EngageLab does not collect user health or fitness data |
| Financial Info | ❌ EngageLab does not collect user financial information |
| Location | ❌ EngageLab does not collect location data |
| Sensitive Info | ❌ EngageLab does not collect user sensitive information |
| Contacts | ❌ EngageLab does not collect user address book or contact lists |
| User Content | ❌ EngageLab does not collect user-generated content |
| Browse History | ❌ EngageLab does not collect user browsing history |
| Search History | ❌ EngageLab does not collect user search history |
| Identifiers | ✅ User ID. EngageLab creates a user-level ID called the EngageLab ID that is not tied to user identity. This ID is used for analytics and SDK functionality. 💡 If you configure aliases to link identifiers to the EngageLab ID, your answer may differ depending on how you generate the aliases. ❌ Device ID. EngageLab does not collect device IDs like advertising identifiers. |
| Purchases | ❌ EngageLab does not collect user purchase data |
| Usage Data | ✅ EngageLab collects user's first session, last session, session count, total usage duration, and notification click count |
| Diagnostics | 💡 EngageLab does not collect crash logs, hang times, or energy usage, but it does collect information related to or associated with the device, such as "last_active", "device_model", "device_os", "net_type", and "state". |
Required Data Type
Type: Usage Data - Product Interaction
You must disclose that your app collects "Product Interaction" data under the "Usage Data" section of your data collection response.
- Product interaction In the context of EngageLab, it is imperative to choose "Analysis" as a minimum requirement. This data is utilized for the dashboard functionality within EngageLab.
- Product Interaction and Identity Related
Apple now asks if you want to link product interaction data with user identity. If you're using EngageLab's EngageLab ID and can't identify individual users, you can choose "No."
If your app's user ID can be linked to a user's email address or other contact information through your own server or another third party, then you should choose "Yes."
- Product Interaction Tracking
Finally, to clarify whether product interaction data will be utilized for tracking purposes, it is essential to review Apple's guidelines and confirm compliance with their tracking definitions.
EngageLab does not inherently track users across various applications for advertising purposes using product interaction data. However, if integrations or other SDKs are employed for this purpose, disclosure may be necessary.
Once your information is saved, you will see the following summary in your account.
Review
After selecting your privacy options, Apple will display a preview of the privacy details applied on the product page. If you have chosen "Usage Data," your privacy details should appear as follows:
If there are changes in how you set up and collect data in the future, you should return to the App Store Connect to edit your response.
