- Home
- Skills
- Mobile Development
- Apple Privacy Manifest Check
More screenshots
Works with the AI Agents you already use
Apple Privacy Manifest Check
This skill finds those and the other privacy manifest mistakes before you upload, and tells you how to fix each one.
$5
Apple Privacy Manifest Check
Example session with this skill installed
Check this project with apple-privacy-manifest-check.
- Read your context and instructions
- Compiled the apple privacy manifest
$ python3 scripts/check_privacy_manifest.py examples/risky
BLOCK Notes/PrivacyInfo.xcprivacy:5 P02 MANIFEST_NOT_VALID
<key>NSUserTrackingUsageDescription</key> -- an Info.plist key; move it to Info.plist
Why: The privacy manifest is not a valid property list (broken XML, a value without a key, JSON, an empty file) or holds keys that are not privacy manifest keys. App Store Connect rejects app submissions that contain an invalid manifest (ITMS-91056), even when the file comes from a third-party SDK.
Safer: Fix the XML (plutil -lint PrivacyInfo.xcprivacy), keep only NSPrivacyTracking, NSPrivacyTrackingDomains, NSPrivacyCollectedDataTypes and NSPrivacyAccessedAPITypes at the top level, and put Info.plist keys such as NSUserTrackingUsageDescription in Info.plist. For an SDK's file, update the SDK or ask its developer.
BLOCK Notes/PrivacyInfo.xcprivacy:11 P04 INVALID_TRACKING_KEYS
BLOCK Notes/PrivacyInfo.xcprivacy:17 P05 INVALID_COLLECTED_DATA_ENTRY
BLOCK Notes/PrivacyInfo.xcprivacy:44 P03 INVALID_ACCESSED_API_ENTRY
BLOCK Notes/Sync/Clock.swift:5 P01 REQUIRED_REASON_API_NOT_DECLARED
REVIEW Notes.xcodeproj/project.pbxproj:63 P14 MANIFEST_NOT_BUNDLED
REVIEW Notes/Api/DeviceInfo.swift:6 P15 COLLECTED_DATA_NOT_DECLARED
REVIEW Notes/Info.plist:11 P12 PRIVACY_KEYS_IN_WRONG_FILE
REVIEW Notes/PrivacyInfo.xcprivacy:36 P17 SDK_ONLY_REASON_IN_APP
REVIEW NotesKit/Package.swift:12 P14 MANIFEST_NOT_BUNDLED
REVIEW NotesWidget/NotesProvider.swift:5 P16 REASON_ONLY_IN_OTHER_MANIFEST
REVIEW NotesWidget/PrivacyInfo.xcprivacy:5 P11 TRACKING_DECLARATION_MISMATCH
REVIEW Podfile.lock:2 P13 LISTED_SDK_WITHOUT_MANIFEST
REVIEW notes-expo/modules/settings/ios/SettingsModule.swift:8 P18 GENERATED_MANIFEST_UNVERIFIED
(Each finding also has Why and Safer lines, as in the first one.)
Verdict: BLOCK. Checked 16 files, 16 with privacy manifest content.
This is a static check of file text. NOT FLAGGED is not a guarantee.
Connects securely to your tools. The creator never sees your data.
About this skill
UserDefaults.standard in your Swift code with no NSPrivacyAccessedAPICategoryUserDefaults entry, or a reason code typed as c617.1 instead of C617.1, is enough for App Store Connect to refuse a build, and a full URL where Apple expects a bare tracking domain makes the manifest invalid. This skill finds those and the other privacy manifest mistakes before you upload, and tells you how to fix each one.
Your agent runs a scanner on your project: PrivacyInfo.xcprivacy files, the manifests Cordova (config.xml) and Expo (app.json, app.config.json) write at build time, Info.plist and other plists, Swift, Objective-C and C/C++ code, Xcode project files (classic groups and Xcode 16 synchronized folders), Package.swift, Podfile, Podfile.lock, Package.resolved and Flutter pubspec.lock. It checks every key and value against Apple's lists of categories, reason codes, data types and purposes, works out which manifest covers which code (app, extension, Swift package), and skips comments, strings, tests and vendored code (Pods, Cordova plugins and platforms). Manifests inside Pods are checked only for what makes App Store Connect reject them, and a manifest in a library's resource bundle covers that library's code. It never builds or runs the project. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach, and every rule links the Apple documentation behind it. Secrets are never printed.
What it checks
BLOCK
- P01: required reason APIs used in your code (UserDefaults, @AppStorage, file timestamps, stat, systemUptime, mach_absolute_time, disk space keys, statfs, activeInputModes) with no manifest that declares the category (iOS, iPadOS, tvOS, visionOS and watchOS projects)
- P02: manifests (files, Cordova config.xml or Expo config) that are not valid property lists or hold keys that are not privacy manifest keys
- P03: invalid NSPrivacyAccessedAPITypes entries (unknown or wrongly cased category, reason code not approved, wrongly cased or from another category, empty reason list, missing or extra key)
- P04: invalid tracking keys (wrong types, tracking true with an empty domain list, tracking false with domains, entries that are not a bare domain: a URL, a path, a query or a trailing slash)
- P05: invalid NSPrivacyCollectedDataTypes entries (unknown data type or purpose, missing or extra key, Linked or Tracking that is not a Boolean)
REVIEW
- P11: tracking that does not add up (true with no domain list, domains without NSPrivacyTracking, a data type used for tracking while tracking is not declared, an App Tracking Transparency request with no manifest that says the app tracks)
- P12: privacy manifest keys in Info.plist or another plist, or a .xcprivacy file with the wrong name
- P13: SDKs from Apple's list locked to versions without a privacy manifest (Alamofire, Kingfisher, SDWebImage, SnapKit, Lottie, SwiftyJSON, Starscream, Firebase, RxSwift, SVProgressHUD, RealmSwift, Charts, Facebook SDK, AFNetworking, MBProgressHUD) and discontinued Flutter plugins (path_provider_ios, shared_preferences_ios, package_info, wakelock)
- P14: a PrivacyInfo.xcprivacy the app target does not copy, or a Swift package target that does not declare it as a resource
- P15: code that reads the advertising identifier, identifierForVendor, location, contacts or health data with no matching collected data type
- P16: a required reason API declared in another target's manifest but not in the one next to the code (app extensions, frameworks)
- P17: an app's own manifest that declares 0A2A.1 or C56D.1, reasons reserved for third-party SDKs
- P18: required reason API use in an Expo project whose manifest comes from app.config.js or app.config.ts that does not name the category (the config cannot be run, so this is a review item)
What's included
- The scanner (Python 3.9+, standard library only)
- A rules guide with the reason, safer approach and Apple documentation link for each rule
- A risky and a safe example project (a notes app with a widget, a Swift package, CocoaPods and a small Expo app), and the real report the scanner produces on the risky one
Limits It reads the project's files, not the built app: manifests inside binary SDKs, APIs called only by compiled SDKs, and code in Kotlin, C# or JavaScript are not checked. Build-time manifests are read from Cordova config.xml and Expo app.json or app.config.json; an Expo app.config.js or app.config.ts is only searched for category names, and manifests added by config plugins are not seen. Which manifest covers which code comes from folders, Swift packages and the Xcode project, not a full build graph. The SDK version table covers the SDKs named above; other SDKs on Apple's list are not reported. Whether a declared reason matches what the code really does, and whether data leaves the device, cannot be decided from the text. NOT FLAGGED is not a guarantee.
Static check of project files. Compiled SDKs, manifests added by Expo config plugins or other build steps, and code outside Swift, Objective-C and C are not checked. NOT FLAGGED is not a guarantee.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 4 days ago
Requires
Permissions
Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example project is a small, inert notes app written for this skill. It is never built or run.