As far as I know, it's best to create a privacy manifest for your app. Here are two key reasons:
The privacy manifest not only declares which APIs your app uses but also describes the data the app collects and why. This information is essential for generating a privacy report to help you complete Privacy Nutrition Labels. However, currently, this doesn't seem to affect the App Store review.
Despite many statically linked libraries having their own privacy manifest, they could still affect your app's privacy manifest. It's highly recommended to analyze your application bundle (.app) before submitting it for App Store review.
Regarding the processing needed for these emojis, you can refer to the README.
If it's not one of the commonly used SDKs tagged with 🎯, it seems unnecessary for now, but it may be needed in the future.
Hello, thanks a lot for creating this tool. It is so helpful. I have some follow-up questions.
==================== Analysis completed! ⏰: 1684s 💡: 38 ⚠️ : 68 🛠️ : 12 ✅: 37 🎯: 35 ====================
How does this overview look for an app with no privacy problems when submitted to the Apple Store?
Since they have API usage analysis result(s): 0, should they include a privacy manifest nevertheless?