[iOS] 4. Apple Privacy Manifest
From 01 May 2024 on, Apple will require app publishers to add a "privacy manifest" to each app that is uploaded into the appstore. The privacy manifest outlines how the app is using certain technologies or features. Since these technologies may be relevant to the user's privacy, the app needs to specify the reason why these technologies are used. Apps that do not have a privacy manifest, where the privacy manifest does not cover all used technologies or where the reasons for using the technologies are incorrect/inadequate, the apple verification team may reject the app and the app may not be published in the Apple App-Store.
Developer Privacy Manifest Details
The consentmanager's SDK Privacy Manifest File details the data types collected and the reasons for accessing UserDefaults. Two primary data categories are outlined: "Other Data Types" and "Coarse Location," both collected solely for app functionality without being linked to the user's identity or used for tracking purposes. Additionally, the SDK accesses UserDefaults, with specified reasons under codes "CA92.1" and "C56D.1," indicating that this access is intended for managing user preferences or settings essential for app operation, while maintaining privacy by not linking data to user identity or engaging in tracking.
The privacy manifest file is included in our iOS SDK from Version 2.0 on. If you are using an older SDK version, we recommend upgrading.
CMP SDK Data
Additional Metadata required for the SDK's app functionality:
| Key | Description | Type |
| CMP_PreviousVersion |
The previous version of the CMP used. |
String |
| CMP_ConsentLayerUpdated |
Timestamp of the last update to the TCF data. |
Date |
|
CMP_Metakeys |
TCF Metadata key array | String |
| CMP_ConsentDryCheckLastUpdated | Timestamp of the last dry check for consent updates. | Date |
| CMP_ConsentDryCheckStatus | Status of the last dry check | Boolean |
| CMP_UserConsent | Stores the user's consent decisions. | Data |
TCF Framework Data
Our SDK stores the key values in UserDefaults to manage GDPR compliance data as per TCF v2.2, enabling interoperability with third-party SDKs that also comply with TCF standards.
More details about the TCF Framework can be found here:
https://iabeurope.eu/transparency-consent-framework/
