breautek commented on code in PR #193: URL: https://github.com/apache/cordova-plugin-device/pull/193#discussion_r1557585100
########## README.md: ########## @@ -305,3 +305,47 @@ var boolean = device.isiOSAppOnMac; ### Supported Platforms - iOS + +--- + +## iOS Privacy Manifest + +As of May 1, 2024, Apple requires a privacy manifest file to be created for apps and third-party SDKs. The purpose of the privacy manifest file is to explain the data being collected and the reasons for the required APIs it uses. Starting with `cordova-ios@7.1.0`, APIs are available for configuring the privacy manifest file from `config.xml`. + +This plugin comes pre-bundled with a `PrivacyInfo.xcprivacy` file that contains the list of APIs it uses and the reasons for using them. + +However, as an app developer, it will be your responsibility to identify additional information explaining what your app does with that data. + +In this case, you will need to review the "[Describing data use in privacy manifests](https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_data_use_in_privacy_manifests)" to understand the list of known `NSPrivacyCollectedDataTypes` and `NSPrivacyCollectedDataTypePurposes`. + +For example, with this plugin, you may collect the device ID for app functionality or analytics. In the case of app functionality, you would write the following in `config.xml`: Review Comment: > For example, with this plugin, you may collect the device ID for app functionality or analytics. I don't really like this statement because the example suggests functionality or analytics, but shows in the example plist only functionality, suggesting that functionality key is acceptable for both functionality and analytics. I think we should either make it simple and drop `or analytics`, or change the terminology to `functionality and analytics` and include the analytics key in the plist array. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
