privacy-manifests

Audit and implement Apple privacy manifests for App Store submission requirements.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/mazicimert/RunDom --skill privacy-manifests-mazicimert
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: privacy-manifests
Source: https://github.com/mazicimert/RunDom/tree/main/.claude/skills/security/privacy-manifests
Command: npx skills add https://github.com/mazicimert/RunDom --skill privacy-manifests-mazicimert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Privacy manifests (PrivacyInfo.xcprivacy) are required for App Store submissions and must declare tracking, APIs used, data collection, and third-party SDK privacy.

Core Features & Use Cases

  • Defines the privacy manifest file format and required reason APIs
  • Declares tracking (NSPrivacyTracking) and domains (NSPrivacyTrackingDomains)
  • Documents App Tracking Transparency (ATT) integration and data nutrition labeling
  • Audits third-party SDK privacy declarations and ensures SDKs provide their own PrivacyInfo.xcprivacy

Quick Start

Create or update PrivacyInfo.xcprivacy at the app target root and declare the required keys and APIs per the manifest.

Frequently Asked Questions about privacy-manifests

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a privacy manifest and when do I need it for an iOS App Store submission?

A privacy manifest (PrivacyInfo.xcprivacy) declares your app's tracking, data collection, and API usage. You need it for App Store submissions to satisfy Apple's privacy compliance requirements and pass app review.

How do I create a PrivacyInfo.xcprivacy file and declare required reason APIs?

Create or update PrivacyInfo.xcprivacy at your app target root. Declare required keys like NSPrivacyTracking, NSPrivacyTrackingDomains, NSPrivacyCollectedDataTypes, and NSPrivacyAccessedAPITypes to specify required reason APIs.

How do I handle third-party SDK privacy declarations in my app's privacy manifest?

Third-party SDKs must provide their own PrivacyInfo.xcprivacy files. You audit these SDK privacy declarations to ensure their tracking domains and data types are correctly documented for App Store submission.

Does my app need App Tracking Transparency integration if NSPrivacyTracking is set to true?

Yes, if NSPrivacyTracking is true, you must integrate App Tracking Transparency (ATT). The privacy manifest documents ATT integration and data nutrition labeling to comply with App Store tracking rules.

What are the required keys for a valid xcprivacy manifest file?

A valid xcprivacy manifest requires correct structure and keys: NSPrivacyTracking, NSPrivacyTrackingDomains, NSPrivacyCollectedDataTypes, and NSPrivacyAccessedAPITypes to declare tracking, domains, data types, and APIs.

What happens if my privacy manifest is missing required reason API declarations during iOS submission?

Missing required reason API declarations in your privacy manifest can cause App Store submission failures. Auditing your manifest ensures all NSPrivacyAccessedAPITypes and data nutrition labels are correct and complete.