privacy-manifests

Automate privacy manifest compliance for iOS App Store submissions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Privacy manifests are required for App Store submissions. This skill guides implementing PrivacyInfo.xcprivacy and required APIs, ensuring ATT is properly integrated and compliant.

Core Features & Use Cases

  • Declares and validates NSPrivacyTracking, NSPrivacyTrackingDomains, NSPrivacyCollectedDataTypes, and NSPrivacyAccessedAPITypes.
  • Audits third-party SDK privacy declarations and ensures official manifest presence for all SDKs.
  • Generates an App Store-ready PrivacyInfo.xcprivacy and prepares privacy nutrition labels.

Quick Start

Create PrivacyInfo.xcprivacy at the app target root with all required keys and declared APIs before submission.

Frequently Asked Questions about privacy-manifests

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

FAQPage Schema
What is a PrivacyInfo.xcprivacy manifest and when do I need it for App Store submission?

A PrivacyInfo.xcprivacy manifest declares your app's privacy practices, required for App Store submission. You need it when preparing iOS apps to declare tracking, collected data types, and accessed API types.

How do I declare NSPrivacyTracking and NSPrivacyTrackingDomains in my iOS app?

To declare NSPrivacyTracking and NSPrivacyTrackingDomains, create a PrivacyInfo.xcprivacy file at your app target root. This validates these keys to ensure tracking declarations are App Store compliant.

How do I audit third-party SDKs for required privacy manifests?

Auditing third-party SDK privacy declarations involves checking that each SDK provides its own official PrivacyInfo.xcprivacy manifest. This verifies official manifest presence for all SDKs to satisfy App Store requirements.

Do I need ATT prompts and NSPrivacyCollectedDataTypes declared for App Store compliance?

Yes, ATT prompts for user consent and NSPrivacyCollectedDataTypes declarations are required for App Store privacy compliance. This verifies proper ATT integration and validates your data type declarations.

What's the best way to generate App Store-ready privacy nutrition labels?

The best way to generate App Store-ready privacy nutrition labels is to validate NSPrivacyAccessedAPITypes and NSPrivacyCollectedDataTypes first. This prepares these labels based on your PrivacyInfo.xcprivacy declarations.

Why does my iOS app submission fail without NSPrivacyAccessedAPITypes declarations?

App Store submission fails without NSPrivacyAccessedAPITypes declarations because Apple requires transparency regarding API usage. This identifies and validates required API types to satisfy App Store privacy compliance rules.