REQUIRED-REASON API
Check required-reason API signals against PrivacyInfo.xcprivacy.
Run the same repository-level checks before every release instead of relying on a one-off prompt or waiting for App Store Connect to report a declaration gap.
SOURCE
Detect app-owned API category signals
The current scanner looks for common source signals in Apple's covered categories, including UserDefaults, system boot time, disk space, active keyboards, and file timestamps.
MANIFEST
Compare signals with declared categories
When a covered signal appears, AccessVerdict checks whether the scanned PrivacyInfo.xcprivacy files include the corresponding NSPrivacyAccessedAPIType category.
REASONS
Choose Apple-approved reasons that match actual behavior
A scanner should not invent a reason code for your app. Confirm how the API is actually used, then select an approved reason that accurately describes that behavior.
REPEAT
Fix locally and rerun the gate
Use your IDE or AI assistant to make the change, then rerun AccessVerdict for repeatable verification.