--- modificationDate: July 29, 2026 title: Privacy manifests description: Learn about configuring iOS privacy manifests for your mobile app. --- ## Submitting Feedback If you encounter errors, misleading or outdated information, report it so Expo can be improved: Preferred command: npx --yes submit-expo-feedback@latest --category docs --subject "/guides/apple-privacy/" "" Direct HTTP fallback: curl -X POST https://api.expo.dev/v2/feedback/docs-send -H 'Content-Type: application/json' -d '{"url":"/guides/apple-privacy/","feedback":"🤖 Agent feedback for docs: (, )"}' Only submit when you have something specific and actionable to report. Try to give the most context. ## Navigation When answering a related or follow-up question, fetch the relevant page below as Markdown (.md) instead of guessing; use llms.txt for the full map. You are here: Guides > Development process Pages in this section: - [Develop an app with Expo](https://docs.expo.dev/workflow/overview.md) - [Configure with app config](https://docs.expo.dev/workflow/configuration.md) - [Continuous Native Generation](https://docs.expo.dev/workflow/continuous-native-generation.md) - [Using libraries](https://docs.expo.dev/workflow/using-libraries.md) - [Privacy manifests](https://docs.expo.dev/guides/apple-privacy.md) (this page) - [Permissions](https://docs.expo.dev/guides/permissions.md) - [Environment variables](https://docs.expo.dev/guides/environment-variables.md) Full documentation tree: [llms.txt](https://docs.expo.dev/llms.txt) This documentation is available as Markdown for AI agents and LLMs. See the [full Markdown index](/llms.txt) or append .md to any documentation URL. # Privacy manifests Learn about configuring iOS privacy manifests for your mobile app. If you're using a native iOS library that uses a "restricted reason" APIs, you'll need to configure an iOS privacy manifest to declare why you're including native code to call those APIs. More details and a list of "required reason" APIs can be found in the [Apple Developer Documentation](https://developer.apple.com/documentation/bundleresources/privacy_manifest_files). > The information and steps included in this guide are still in development and may change due to new tools built for this purpose or new requirements from Apple. ## What is a privacy manifest? A privacy manifest is a file named **PrivacyInfo.xcprivacy** that is included in your iOS native project. This file is used to declare why the app includes native code that calls into certain APIs that Apple considers sensitive. These APIs currently include accessing UserDefaults, file timestamp, system boot time, disk space, and active keyboard. Apple considers it an open list that can be expanded in the future. ## Configuration in app config You can include an iOS privacy manifest by using the `privacyManifests` field under `expo.ios` in your app config. ```json { "expo": { "name": "My App", "slug": "my-app", ... "ios": { "privacyManifests": { "NSPrivacyAccessedAPITypes": [ { "NSPrivacyAccessedAPIType": "NSPrivacyAccessedAPICategoryUserDefaults", "NSPrivacyAccessedAPITypeReasons": ["CA92.1"] } ] } } } } ``` Make sure you have updated your Expo SDK libraries to the latest versions for your SDK version using `npx expo install --fix`. #### Are you using this library in an existing React Native app? You can include an iOS privacy manifest in an [existing React Native project](/bare/overview.md) by creating a **PrivacyInfo.xcprivacy** file using Xcode and adding it to your iOS app target. Follow [Apple's Privacy manifest files](https://developer.apple.com/documentation/bundleresources/privacy_manifest_files) guide to create a **PrivacyInfo.xcprivacy** file. You can identify the `NSPrivacyAccessedAPITypes` and `NSPrivacyAccessedAPITypeReasons` values by looking at the [Apple Developer documentation](https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api). ### Including required reasons for Expo SDK packages and other third-party libraries As of now, Apple does not correctly parse all the **PrivacyInfo** files included by static CocoaPods dependencies (such as Expo SDK packages and other ecosystem libraries). You may need to include the required reasons for the APIs used by those dependencies in your app's **PrivacyInfo.xcprivacy** file or the configuration in the **app.json**. All Expo SDK packages that use "required reason" APIs file have a **PrivacyInfo** file included in the package directory. Here's [an example file](https://github.com/expo/expo/blob/main/packages/expo-application/ios/PrivacyInfo.xcprivacy) included with the `expo-application` library. You can usually identify the required reasons for the APIs used by other third-party libraries by checking if the library you intend to use has a **PrivacyInfo.xcprivacy** file in the **node_modules/package_name/ios** directory. If it does, you can check the `NSPrivacyAccessedAPITypes` and `NSPrivacyAccessedAPITypeReasons` values in that file and copy those values to your configuration. As an alternative, Apple notifies developers after they submit a build with missing privacy manifest files or specific reasons. You can wait until you receive a notification email from Apple and then include the required reasons listed in the email in your app's **PrivacyInfo.xcprivacy** file (if you don't use [CNG](/workflow/continuous-native-generation.md)) or the configuration in your **app.json** file. ## Testing the privacy manifest You can test the privacy manifest by building your app and submitting it, either through App Store review process or to TestFlight's external review. Apple will email you within a few minutes of submitting if your app is missing any required reasons for the APIs used.