Which email did Apple send you?
Three App Store Connect emails are about privacy manifests, and each needs a different fix. Paste any of them above.
| Code | What it means | Fix |
|---|---|---|
| ITMS-91053: Missing API declaration | Your code calls an API from a required reason category and your manifest gives no reason. The email names each category, such as NSPrivacyAccessedAPICategoryUserDefaults. | Paste the email above and pick a reason for each category. |
| ITMS-91056: Invalid privacy manifest | A manifest in your app has keys or values Apple doesn't expect, or isn't a well-formed property list. The email gives the file's path. | Paste that file above. The tool lists each problem and gives you the fixed file. If the file is inside an SDK, update the SDK. |
| ITMS-91061: Missing privacy manifest | Your app includes an SDK from Apple's list of commonly used SDKs, and that SDK has no privacy manifest. The email names the SDK and its path. | Update that SDK to a version that ships its own privacy manifest. Your app's file can't fix this, and Apple's guidance is not to copy the SDK's practices into it. |
Since May 1, 2024, App Store Connect doesn't accept apps that use a required reason API without a reason in their privacy manifest. Since November 12, 2024, apps submitted for review must contain valid privacy manifests. Since February 12, 2025, they must also contain a valid privacy manifest for each SDK on Apple's list of commonly used SDKs.
Required reason APIs and their reason codes
Apple lists five categories of API that can be misused to fingerprint a device, so you have to say why you call them. Each category gets one entry in NSPrivacyAccessedAPITypes with one or more reason codes from its own list. A code from another category is invalid. Here is every code on Apple's page as of November 18, 2026, in plain words. The examples are ours.
User defaults
NSPrivacyAccessedAPICategoryUserDefaults. Triggered by UserDefaults.
| 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 that also gives the app a small settings helper. |
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 that also gives the app a helper for a file's modified date. |
System boot time
NSPrivacyAccessedAPICategorySystemBootTime. Triggered by ProcessInfo.systemUptime, 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. |
Codes marked SDKs only are for third-party SDKs that wrap the API for the app. Apple says an app can't declare them, and neither can an SDK that was made mainly to wrap these APIs. If none of the reasons fits what your code does, Apple asks you to find another API or request a new reason.
Example PrivacyInfo.xcprivacy
An app that saves settings in UserDefaults and keeps people's email address for sign-in, with no tracking, looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>NSPrivacyTracking</key>
<false/>
<key>NSPrivacyCollectedDataTypes</key>
<array>
<dict>
<key>NSPrivacyCollectedDataType</key>
<string>NSPrivacyCollectedDataTypeEmailAddress</string>
<key>NSPrivacyCollectedDataTypeLinked</key>
<true/>
<key>NSPrivacyCollectedDataTypeTracking</key>
<false/>
<key>NSPrivacyCollectedDataTypePurposes</key>
<array>
<string>NSPrivacyCollectedDataTypePurposeAppFunctionality</string>
</array>
</dict>
</array>
<key>NSPrivacyAccessedAPITypes</key>
<array>
<dict>
<key>NSPrivacyAccessedAPIType</key>
<string>NSPrivacyAccessedAPICategoryUserDefaults</string>
<key>NSPrivacyAccessedAPITypeReasons</key>
<array>
<string>CA92.1</string>
</array>
</dict>
</array>
</dict>
</plist>
For each data type, Linked means you tie it to the person's identity, Tracking means you use it for tracking, and Purposes are the same reasons App Store Connect asks for. Apple's six purposes are App Functionality, Analytics, Product Personalization, Developer's Advertising or Marketing, Third-Party Advertising and Other Purposes.
Where the file goes
- Native iOS. In Xcode choose File > New File, pick App Privacy File under Resource, and tick your app's target. The name must stay PrivacyInfo.xcprivacy. Xcode places it at the root of the app bundle.
- Flutter. Flutter's docs don't cover the app's own manifest, so use Apple's Xcode steps above: open
ios/Runner.xcworkspace, choose File > New File, pick App Privacy File and tick the Runner target, which is the iOS app target in a Flutter project. Flutter itself and many plugins are on Apple's list of SDKs that must ship their own manifest. - React Native. Expo's docs say to create the file in Xcode and add it to your iOS app target. With Expo, put the same keys in
app.jsonunderexpo.ios.privacyManifestsinstead. Expo also warns that Apple doesn't read every manifest inside static CocoaPods libraries, so you may have to copy their reasons into your own file. - Unity. Unity's manual says to save the file in your project's
Assets/Pluginsfolder, and to declare reasons for your own native code and for the C# .NET framework APIs you use that call required reason APIs. It also asks you to check that the manifest inside the Unity framework is accurate.
To check the result, archive the app (Product > Archive), then Control-click the archive in the Organizer and choose Generate Privacy Report. It combines your manifest with every SDK's.
Why there's no SDK list here
Our privacy policy generator asks which SDKs you use, because the App Store privacy label must include what they collect. The manifest is different. Apple says third-party SDKs provide their own manifests, and your app's manifest doesn't need to cover data they collect. The same goes for required reason APIs: an SDK reports the ones its code calls in its own file. So adding Firebase or an ads SDK here would put their data in your file twice. Tick only what your own code does. An Apple engineer's guidance on the forums for ITMS-91061 says the same: your app's manifest should describe only your app's practices, not an SDK's. The one exception people hit is the Expo warning above about static libraries. If Apple's email names a category your own code doesn't call, a library built into your app may be the cause, and Expo suggests copying the reason that library declares in its own manifest into yours.
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 or the web dashboard. It also sends push notifications. Its iOS SDK ships its own PrivacyInfo.xcprivacy, so adding it doesn't add lines to yours. That file says no tracking and no tracking domains. It lists customer support messages, photos people attach, a device ID, a user ID, product interaction (the chat signals your app sends) and other diagnostic data (app and iOS version, device model, language and time zone), plus name and email only when your app passes them, all linked to the person and used for app functionality. It declares UserDefaults with CA92.1 and 1C8F.1. The Flutter plugin carries the same file. The React Native pod carries it too, but as a static framework, and Expo warns (above) that Apple doesn't read every static pod's manifest. So if Apple's email names User defaults for your app's own code after you add the React Native SDK, add CA92.1 and 1C8F.1 to your app's file. Free for 14 days, no card. See how Hailbell works.
Questions
What is PrivacyInfo.xcprivacy?
It's Apple's privacy manifest: a property list file in your app or SDK that says whether it tracks, which tracking domains it contacts, what data it collects and why, and why it calls the APIs Apple lists as needing a reason. The file must be named PrivacyInfo.xcprivacy. Xcode reads it to build your app's privacy report.
What does ITMS-91053 Missing API declaration mean?
Apple scanned your build and found code that calls an API from a required reason category, such as UserDefaults, with no reason for it in your privacy manifest. The email names each category. Since May 1, 2024 App Store Connect doesn't accept apps that leave the reasons out. Paste the email into the generator, pick a reason code for each category it names, and add the file to your app target.
Does my app need a privacy manifest if it collects no data?
It does if your own code calls any required reason API. UserDefaults is one, so if your app saves even one setting with it, you need a manifest with the reason. Collected data types only list data your own code collects; if that's none, leave them out.
Does my app's privacy manifest need to list what my SDKs collect?
No. Apple says third-party SDKs provide their own privacy manifests, and your app's manifest doesn't need to cover data they collect. Each SDK also declares its own required reason APIs. Xcode combines all the manifests into one privacy report when you archive. Your App Store privacy label still has to include what SDKs collect.
Where do I put PrivacyInfo.xcprivacy in Flutter or React Native?
In the iOS app target. In Flutter, open ios/Runner.xcworkspace in Xcode and add the file to the Runner target. In a React Native app without Expo, Expo's docs say to create it in Xcode and add it to the iOS app target. With Expo, put the same keys in app.json under expo.ios.privacyManifests. In Unity, save it in Assets/Plugins.
Sources, checked November 18, 2026: Apple's Privacy manifest files, Describing use of required reason API, Describing data use in privacy manifests, Adding a privacy manifest to your app or third-party SDK, TN3181: Debugging an invalid privacy manifest, Third-party SDK requirements, the May 1 reminder and App privacy details; the ITMS-91053 email text as posted on Apple's developer forums and an Apple engineer's post on ITMS-91061; Expo's Privacy manifests guide; Unity's Apple privacy manifest page.
Related free tools: privacy policy generator, App Store keyword optimizer, App Store screenshot sizes, or all free tools. Questions? Start a chat with us.