What the checker reads
- A project folder. Every Swift, Objective-C, C and C++ file, including
Pods, Flutter plugins and React Native modules innode_modules. Xcode keeps Swift packages in DerivedData, not your project, so drop the .ipa to see those. Test files (those that import XCTest or Testing) are skipped, since tests don't ship. Each match is grouped by who owns the code: your app, another target with its own bundle (an extension, App Clip, watch app or framework, found from the Xcode project's target list or itsInfo.plist), or an SDK. Then it's checked against that owner'sPrivacyInfo.xcprivacy. An Expoapp.jsonwithprivacyManifestscounts as your app's manifest. - An .ipa. Your app's binary, each framework in
Frameworksand each app extension, read for the names that calls to these APIs leave behind, such as_statorNSUserDefaults. That's close to what App Store Connect sees when you upload. The manifests inside the .ipa are checked too. - Single files or pasted code. Handy when Apple's email names one category and you want to find the line.
Matching is by name, the way the scanners people run in Terminal work. A line that only mentions an API in a string also counts, and code that calls an API through another system API doesn't. If Apple's email names a category the checker doesn't find, run it on the .ipa.
Every required reason API and its reason codes
Apple lists five categories. Each gets one entry in NSPrivacyAccessedAPITypes with one or more reason codes from its own list; a code from another category is invalid. This is everything on Apple's page as of November 19, 2026, in plain words. The examples are ours. To build the file, use the PrivacyInfo.xcprivacy generator.
User defaults
NSPrivacyAccessedAPICategoryUserDefaults. Triggered by UserDefaults (and @AppStorage, which stores in it).
| Code | When to declare it | Example |
|---|---|---|
CA92.1 | Read and write data that only your app can see. | Remembering that someone picked dark mode. |
1C8F.1 | Read and write data shared with your own app extensions and App Clips in the same App Group. | A widget that reads the same settings as the app. |
C56D.1 SDKs only | Your SDK gives the app a function that wraps UserDefaults, and only touches UserDefaults when the app calls it. Not for the SDK's own use, nothing it reads may leave the device, and not allowed if the SDK was made mainly to wrap required reason APIs. | An analytics SDK with a small settings helper for the app. |
AC6B.1 | Read the managed app configuration set by device management (MDM), or store feedback for it. | A company app that reads its server address from the MDM profile. |
File timestamps
NSPrivacyAccessedAPICategoryFileTimestamp. Triggered by FileAttributeKey.creationDate, FileAttributeKey.modificationDate, UIDocument.fileModificationDate, URLResourceKey.contentModificationDateKey, URLResourceKey.creationDateKey, getattrlist, getattrlistbulk, fgetattrlist, getattrlistat, stat, fstat, fstatat, lstat.
| Code | When to declare it | Example |
|---|---|---|
DDA9.1 | Show file dates to the person using the device. They may not leave the device. | A file list that says "Edited yesterday". |
C617.1 | Read dates, size or other details of files inside your app's container, App Group container or CloudKit container. | Deleting cached images older than a week. |
3B52.1 | Read dates or details of files and folders the person gave you access to, such as through a document picker. | Showing the date of a PDF someone picked to import. |
0A2A.1 SDKs only | Your SDK gives the app a function that wraps file timestamp APIs, and only calls them when the app calls it. Not for the SDK's own use, nothing it reads may leave the device, and not allowed if the SDK was made mainly to wrap required reason APIs. | A crash reporting SDK with a file date helper for the app. |
System boot time
NSPrivacyAccessedAPICategorySystemBootTime. Triggered by ProcessInfo.systemUptime and mach_absolute_time().
| Code | When to declare it | Example |
|---|---|---|
35F9.1 | Measure the time between events in your app, or run timers. Only the elapsed time may leave the device. | Timing how long a screen takes to load. |
8FFB.1 | Work out the clock time of events in your app, such as UIKit or AVFAudio events. Those timestamps may leave the device; the boot time may not. | Turning a touch event's timestamp into a date. |
3D61.1 | Include boot time in a bug report the person chooses to send, shown to them in the report. | A "Report a problem" screen that lists uptime before sending. |
Disk space
NSPrivacyAccessedAPICategoryDiskSpace. Triggered by URLResourceKey.volumeAvailableCapacityKey, URLResourceKey.volumeAvailableCapacityForImportantUsageKey, URLResourceKey.volumeAvailableCapacityForOpportunisticUsageKey, URLResourceKey.volumeTotalCapacityKey, FileAttributeKey.systemFreeSize, FileAttributeKey.systemSize, statfs, statvfs, fstatfs, fstatvfs, getattrlist, fgetattrlist, getattrlistat.
| Code | When to declare it | Example |
|---|---|---|
85F4.1 | Show disk space to the person. It may not leave the device, except over the local network to their own device with their permission. | "2.1 GB free" on a downloads screen. |
E174.1 | Check there is room to write files, or delete files when space is low, in a way people can notice. It may not leave the device, but you may skip a download when space is short. | Pausing a video download when the phone is nearly full. |
7D9E.1 | Include disk space in a bug report the person chooses to send, shown to them in the report. | A "Report a problem" screen that lists free space before sending. |
B728.1 | Health research apps only: tell participants that low disk space is affecting research data collection. | A study app warning it can't record more sensor data. |
Active keyboards
NSPrivacyAccessedAPICategoryActiveKeyboards. Triggered by UITextInputMode.activeInputModes.
| Code | When to declare it | Example |
|---|---|---|
3EC4.1 | Custom keyboard apps only, where the keyboard is the app's main feature: see which keyboards are turned on. | A keyboard app checking that its keyboard is enabled. |
54BD.1 | Show the right interface in your text fields for the active keyboard, in a way people can notice. It may not leave the device. | Changing a text field's layout for the keyboard in use. |
getattrlist, fgetattrlist and getattrlistat are on both the File timestamps and Disk space lists, so declare the category that matches what your code reads. Codes marked SDKs only are for third-party SDKs that wrap the API for the app; an app can't declare them. If no reason fits, Apple asks you to use another API or request a new reason.
Your app's code, an extension or an SDK
Apple's ITMS-91053 email names the file it blames: your app's binary, a framework inside it, or an app extension. The checker groups its results the same way, because the fix differs.
| Where the call is | What to do |
|---|---|
| Your app's own code | Add the category and a reason to your app's PrivacyInfo.xcprivacy. |
| An app extension (a widget, a notification service) | The extension is its own bundle. If Apple's email names it, give its target its own manifest with the reason. |
| An SDK with its own manifest that declares it | Nothing. Xcode combines the SDK's manifest with yours when you archive. |
| An SDK with no manifest, or one that leaves the category out | Update the SDK. For a library linked statically into your app, Expo's docs suggest copying its reason into your app's file, because Apple doesn't read every static pod's manifest. |
Where Hailbell fits
Hailbell is a support chat inside your iOS, Android or web app, where an AI answers first from your docs and prices, and messages reach you in Discord, Telegram, Slack or the web dashboard. It also sends push notifications. Its iOS SDK ships its own PrivacyInfo.xcprivacy, and the only required reason API it declares is User defaults, with CA92.1 and 1C8F.1. Free for 14 days, no card. See how Hailbell works.
Questions
What is a required reason API?
It's an API Apple says can be misused to fingerprint a device, so an app or SDK that calls it must say why in its privacy manifest (PrivacyInfo.xcprivacy). There are five categories: user defaults, file timestamps, system boot time, disk space and active keyboards. Each has a short list of allowed reasons with codes like CA92.1. Since May 1, 2024 App Store Connect doesn't accept apps that call them without a reason.
How do I find which code uses a required reason API?
Drop your Xcode project folder or your .ipa into the checker on this page. It lists each call by file and line, or by binary for an .ipa, and says whether it's your app's code, an app extension or an SDK. Without a tool, you can search your source for the API names, or run nm on your built app and look for symbols such as _stat and _mach_absolute_time.
Which reason code do I use for UserDefaults?
CA92.1 if your app reads and writes its own settings, which covers most apps. Add 1C8F.1 if you share UserDefaults with your own widgets, extensions or App Clips through an App Group (UserDefaults(suiteName:)). AC6B.1 is only for reading managed configuration from device management. C56D.1 is only for third-party SDKs that wrap UserDefaults for the app.
Do I declare the required reason APIs my SDKs call?
Usually not. Apple says each third-party SDK declares the APIs its own code calls in its own privacy manifest, and Xcode combines them when you archive. The exception is a library linked statically into your app's binary: Expo's docs warn that Apple doesn't read every manifest inside static CocoaPods, so if Apple's email names a category your own code doesn't call, copy that library's reason into your app's file.
Does @AppStorage count as UserDefaults?
Yes. Apple describes @AppStorage as a property wrapper that reflects a value from UserDefaults, so an app that uses it stores data in UserDefaults and needs the User defaults category in its manifest, usually with CA92.1.
Sources, checked November 19, 2026: Apple's NSPrivacyAccessedAPIType (every category, API and reason code), Describing use of required reason API, Privacy manifest files, the May 1 reminder and AppStorage; the ITMS-91053 email text as posted on Apple's developer forums; Expo's Privacy manifests guide.
Related free tools: PrivacyInfo.xcprivacy generator, privacy policy generator, App Store keyword optimizer, or all free tools. Questions? Start a chat with us.