Learn how you can Unlock Limitless Customer Lifetime Value with CleverTap’s All-in-One Customer Engagement Platform.
Apple has always prided itself on caring for the privacy of its customers. And their latest move continues in that direction — they’ve announced App Store Connect to help customers see what each app may potentially do with their user data once it’s downloaded to their devices.
Starting December 8, 2020, all apps are now required to disclose their data collection practices, including the data collection practices of any third-party software that the app runs.
This means app developers must answer a questionnaire detailing the types of data being collected, how that data is being used, whether the app runs code from a third party, and if so, where that user data goes and whether users are being tracked by it.*
We’ve outlined a few tips below to help you if you’re using CleverTap’s SDK in your iOS app. But due to the complexity of Apple’s privacy rules and app integrations with multiple third-party SDKs, please make sure you refer to Apple’s App Privacy Details page and your own legal team to figure out the right decision for your app.
From December 8, 2020 onward, the information on your data collection practices is now required when submitting new apps or app updates to the App Store.
And note that the App Store typically shuts down around the Christmas and New Year holidays each year.
Plan to answer these privacy questions even if your upgrade is down the road. It’s best to get this done sooner rather than later.
Here, we outline the types of data that the CleverTap SDK collects.
There are really only 4 data types that our SDK tracks out of the box. These are:
Legend:
Data Type | CleverTap Data Collection | Remarks |
|---|---|---|
Contact information
| May be, By Default: Not collected | If you have configured to transmit this data, respond accordingly. |
Health and fitness
| May be, By Default: Not collected | If you have configured to transmit this data, respond accordingly. |
Financial info
| May be, By Default: Not collected | If you have configured to transmit this data, respond accordingly. |
Location info
| May be, By Default: Not collected | If you have configured to transmit this data, respond accordingly. Requires additional integration : |
Sensitive info | May be, By Default: Not collected | If you have configured to transmit this data, respond accordingly. |
Contacts | May be, By Default: Not collected | If you have configured to transmit this data, respond accordingly. |
User content
| May be, By Default: Not collected | If you have configured to transmit this data, respond accordingly. |
Browsing history | Not collected | If you have configured to transmit this data, respond accordingly. |
Search history | Not collected | If you have configured to transmit this data, respond accordingly. |
Identifiers
| May be, By Default: Not collected | Latest CleverTap iOS SDK does not capture IDFA or other device IDs like IMEI etc. IDFV is used to create the CleverTap ID, which is disclosed under Other Data. |
Purchases
| May be, By Default: Not collected | If you have configured to transmit this data, respond accordingly. |
Usage data
| Required, Collected Product interaction: Yes | Product interactions: App launches are measured, as well as any other user interaction, configured by the app developer. |
Diagnostics data
| Not collected Crash data: No | For crash & other diagnostics data: if you have configured to transmit this data, respond accordingly. |
Other Data | Required, Collected | Technical device information (for example, OS, device type, language, WiFi status, screen size, etc.) or network information (for example, IP address, HTTP user agent) is received by CleverTap. IDFV is collected. |
How does your app handle or utilize customer data? Below, we’ve clarified the possible use cases for the user data collected. Select the ones appropriate for your app.
| Purpose | Selection based on how data from CleverTap will be used |
| Third-Party Advertising | Select if you share the data type with a third party for the purpose of displaying third-party ads in your app. |
| Developer’s Advertising or Marketing | Select if you share the data type with a third party for the purpose of displaying first-party ads in your app, sending marketing communications directly to your users, or sharing data with entities who will display your ads. |
| Analytics | Select this if the CleverTap SDK is integrated, which means you are using the data to evaluate user behavior, including to understand the effectiveness of existing product features, plan new features, or measure audience size or characteristics. |
| Product Personalization | Select if you are using the data to customize what the user sees, such as a list of recommended products, posts, or suggestions based on their past behavior. This must be selected if you plan to use CleverTap Engagement features like Product Experiences, In-App Notifications, App Inbox, etc. to personalize the product. |
| App Functionality | Select if your app uses the data to: authenticate the user, enable features, prevent fraud, implement security measures, ensure server up-time, minimize app crashes, improve scalability and performance, or perform customer support. |
| Other Purposes (any other purposes not listed) | Select if applicable. |
Data types collected through CleverTap are typically connected to identifier(s) when configured. App developers should select Yes when asked if the data is linked to an identity.
What associations the customer is capable of making (e.g. to a customer account or an identifiable individual) is unique to the customer and at its own discretion.
You’ll need to understand whether you and your third-party partners use data from your app to track users and, if so, which data is used for this purpose. CleverTap iOS SDK does not track and it is unique to the customer and at its own discretion.
Please refer to CleverTap privacy policy here: https://clevertap.com/privacy-policy/.
How to Spot Your App Uninstalls From a Distance
