In the Required Reason API doc, the UserDefaults section defines NSPrivacyAccessedAPITypeReasons CA92.1: Declare this reason to access user defaults to read and write information that is only accessible to the app itself. This reason does not permit reading information that was written by other apps or the system, or writing information that can be accessed by other apps. If I store a user generated string in UserDefaults, later on fetch it within the same app, send it to my backend component, and lastly my backend component share the string with 3rd party developers, do I still fall into the CA92.1 category? In other words, do I need to submit an approval request for this kind of usage? My understanding is this usage still falls into CA92.1 because it does not access device signals for fingerprinting purposes, but I am not sure. Please advice. Thanks!

For an ad SDK that shows web ads in WKWebView, if it does not know what tracking pixels will be in the web ads, is it still responsible for reporting Tracking Domains in the Privacy Manifest? If yes, how?

Please consider the following scenario: I am an ad serving SDK. Each ad comes with a callback URL provided by the advertiser which can be anything and I didn't know ahead of time. After the app user clicks on the ad, I fire the callback URL without adding any privacy tracking parameter to the URL request. I think such callback URL has no concern of privacy tracking, thus it does not need to be added to the list of Privacy Tracking Domains in PrivacyInfo.xcprivacy. Can Apple confirm? Thanks!

The video mentioned the following documentations but I can't find them anywhere ( developer.apple.com and Google): App privacy details on the App Store Required reason APIs Privacy-impacting SDKs Does anyone know where they are, or when they will be available? Thanks!