The email only mentioned the app itself and the app's extensions. If your third party dependencies are statically linked to your app/extension targets (the default for most SPM packages, or when using linkage: :static in CocoaPods), you are probably seeing this because the contents of the third party code is embedded within you app/extension binary rather than embedded in the /Frameworks directory as it's own dynamic framework. This results in the confusing warning message that makes it sound as if the usage exists within your own code. I'd love for somebody to correct me, but I think that the only solution today is for you crawl through the PrivacyManifest.xcprivacy file for each of your third party dependencies and to copy the required API usages into your own PrivacyManifest.xcprivacy files in your app and extension targets. If this sounds frustrating to you, please consider submitting a feedback to Apple as well. If you are not sure what to write, I have a template and instructions here: https://liamnichols.eu/2024/03/22/privacy-manifests.html.