Free tool

Free Privacy Manifest Generator for iOS apps

The generator writes the PrivacyInfo.xcprivacy file for your app target, with the required reason APIs and the data your code collects, and checks your SDKs against the Apple list.

Build your privacy manifest App Store Privacy Label Generator
  • PrivacyInfo.xcprivacy
  • Required reason APIs
  • SDK check
  • App Store Connect answers

Build your privacy manifest.

Complete 3 steps and copy the results in step 4.

Tell us about your app

Paste the email Apple sent about a missing API declaration or privacy manifest. The generator reads the API categories and SDKs it names.

Find your SDKs

Paste Podfile.lock, Package.resolved, pubspec.lock (Flutter) or package.json (React Native or Capacitor).

SDKs in your app

Select every SDK your app includes. Each one adds the data it collects to your answers.

Describe what your app does

Your own code

Select what your app and your server do with data, apart from the SDKs.

Tracking

Tracking means linking data from your app with data from other companies for targeted ads or ad measurement, or sharing it with a data broker.

Required reason APIs in your own code

Select each API category your own code uses, then the reasons that match. Most apps use user defaults, with reason CA92.1.

App Store

The App Privacy card on your App Store page, by data category.

Copy your privacy details

Review the answers before you publish them. They follow your answers above and the published data of each SDK.

Enter your app name to see your privacy details.

The generator writes answers from your selections and the published data of each SDK, such as its privacy manifest. It isn't legal advice. SDKs change what they collect between versions, so check each one against the documentation of its vendor and the privacy report Xcode generates.

Where to add your privacy manifest.

The file goes in your app target, so Xcode bundles it with the app. Each SDK brings a manifest of its own.

  1. Download the file. Keep the name PrivacyInfo.xcprivacy, which Xcode looks for.

  2. Add it to your app target. Drag it into the Xcode project and check your app target, or create one with File > New File and the App Privacy file type.

  3. Update your SDKs. Use versions of the SDKs on the Apple list that include their own privacy manifest and signature.

  4. Check the privacy report. Archive the app (Product > Archive), then Control-click the archive and choose Generate Privacy Report.

  5. Upload the build. Paste any email App Store Connect sends about missing reasons into step 1, and update the file.

  6. Keep the reasons accurate. Use each API only for the reasons you declare, and update the file when your code changes.

The rules

What Apple asks.

Each row names an Apple rule or a privacy law, when it applies, and what your app needs.

Apple rules and privacy laws for iOS apps, when each applies, and what it asks
Rule or law When it applies What it asks
App Review Guideline 5.1.1(i) Every app on the App Store. A link to the privacy policy in the App Store Connect metadata and inside the app, easy to find.
App Privacy details in App Store Connect New apps and app updates. Every data type you and your third-party partners collect, why, whether it's linked to the person and whether it's used for tracking.
App Review Guideline 5.1.2(i) Apps that track people across apps and websites of other companies. Explicit permission through the App Tracking Transparency prompt before any tracking.
Privacy manifest and required reason APIs Apps and SDKs that use the listed APIs, since May 1, 2024. An approved reason for each API category in PrivacyInfo.xcprivacy. App Store Connect doesn't accept an upload without one.
Third-party SDK requirements Apps that include an SDK on the Apple list, such as Firebase, the Facebook SDK or OneSignal. A privacy manifest and a signature for each listed SDK, in new apps and in updates that add the SDK.
Privacy laws, such as the GDPR and the CCPA Apps with users in the EU, the UK, California and other places with a privacy law. A privacy policy that tells people what you collect, why, and who receives it, in line with the App Store answers.

Privacy Policy Generator

Apple asks every app for a Privacy Policy.

The TermsFeed Privacy Policy Generator writes a Privacy Policy for your app, with the analytics, advertising and payment providers your SDKs send data to.

Generate Privacy Policy

Frequently asked questions.

Answers to common questions about privacy manifests.

What is PrivacyInfo.xcprivacy?

PrivacyInfo.xcprivacy is the privacy manifest: a property list in your app or SDK that records the data it collects and the required reason APIs it uses.

  • NSPrivacyTracking and NSPrivacyTrackingDomains say whether the code tracks, and through which domains.
  • NSPrivacyCollectedDataTypes lists each data type with its purposes.
  • NSPrivacyAccessedAPITypes lists each required reason API category with its reasons.

What are required reason APIs?

Required reason APIs are APIs that apps could misuse to fingerprint a device, so Apple asks for an approved reason before you use them.

  • The 5 categories are user defaults, file timestamps, system boot time, disk space and active keyboards.
  • Each category has its own approved reasons, such as CA92.1 for user defaults only your app reads.
  • App Store Connect has refused uploads without the reasons since May 1, 2024.

Why did App Store Connect refuse my upload?

An upload fails without a reason for each required reason API the app uses, or without the privacy manifest of a listed SDK.

  • Paste the email into step 1 to find the API categories and SDKs it names.
  • Add the reasons to your app manifest for your own code.
  • Update each listed SDK to a version with its own privacy manifest.

Does my app manifest cover my SDKs?

No. Each SDK ships a privacy manifest of its own, and your app manifest covers your own code.

  • Update SDKs to versions that include a manifest.
  • The App Store Connect answers still cover the data of every SDK.
  • Xcode combines all the manifests in the privacy report.

Which reason fits user defaults?

CA92.1 fits most apps: it covers data only your app reads and writes.

  • 1C8F.1 covers data shared with your other apps, extensions and App Clips in the same App Group.
  • AC6B.1 covers managed app configuration from MDM.
  • Declare only reasons that match what your code does.

Is the Privacy Manifest Generator free?

Yes, the Privacy Manifest Generator is free.

  • The generator needs no account.
  • The generator writes the App Store Connect answers too.

Build your privacy manifest with the generator above.