# Privacy

> Route Privacy Manifest (PrivacyInfo.xcprivacy) implementation tasks to the correct Knowledge Contracts -- file structure/bundling, required-reason API declarations, collected data type declarations, and tracking domains/third-party SDK signatures. Use when writing or editing PrivacyInfo.xcprivacy, NSPrivacyCollectedDataTypes, NSPrivacyAccessedAPITypes, NSPrivacyAccessedAPITypeReasons, NSPrivacyTracking, NSPrivacyTrackingDomains, NSPrivacyCollectedDataType, NSPrivacyCollectedDataTypePurposes, or handling "required reason API" / "privacy manifest" / "third-party SDK signature" tasks. v1 is manifest file implementation/schema only -- no App Store Connect nutrition-label questionnaire, no permission-request UI design, no Info.plist usage strings, no Keychain/security. Triggers on PrivacyInfo.xcprivacy, privacy manifest, NSPrivacyTracking, NSPrivacyTrackingDomains, NSPrivacyCollectedDataTypes, NSPrivacyAccessedAPITypes, NSPrivacyAccessedAPITypeReasons, required reason API, App Privacy Configuration, third-party SD

- Skill: `caglarbaranbora/privacy` (Agent Skill)
- Install (CLI): `npx skillmds@latest add caglarbaranbora/privacy`
- Raw SKILL.md: https://api.skillmd.com/api/skills/caglarbaranbora/privacy/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- Author: caglarbaranbora (https://skillmd.com/u/caglarbaranbora)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/caglarbaranbora/privacy

---


# Privacy — Foundations Skill

## Purpose

Route Privacy Manifest (`PrivacyInfo.xcprivacy`) implementation tasks
to the minimum required Privacy Knowledge Contracts. v1 scope is the
manifest file's structure and schema mechanics — how to write it
correctly the first time — not App Store review consequences, not
permission-UI design, not Info.plist strings, not credential storage.

## Routing

Load only the contracts relevant to the task. All paths relative to
knowledge/privacy/.

-   File placement, bundling per product type, or per-target/framework/xcframework manifest requirements -> manifest-file-structure-and-scope.md
-   `NSPrivacyAccessedAPITypes`/`NSPrivacyAccessedAPITypeReasons`, required-reason API categories or justification codes -> required-reason-api-declarations.md
-   `NSPrivacyCollectedDataTypes` entries, `NSPrivacyCollectedDataType`/`NSPrivacyCollectedDataTypePurposes` values -> collected-data-types-declaration.md
-   `NSPrivacyTracking`/`NSPrivacyTrackingDomains`, or third-party SDK manifest-and-signature coverage -> tracking-domains-and-third-party-sdk-signatures.md

Never load more than the contracts relevant to the specific question.

## Stop Conditions

Stop and report if the requested topic has no matching Knowledge
Contract in knowledge/privacy/ — do not guess or fall back to general
knowledge, especially for specific enum values or reason codes, since
Apple has changed this list before.

-   App Store Connect "App Privacy" nutrition-label questionnaire — owned by
    `app-store-review-guidelines`
-   Permission-request UI/consent-flow design, purpose-string wording — owned by
    `human-interface-guidelines`
-   `Info.plist` runtime usage-string keys — owned by `app-store-review-guidelines`
-   Keychain/credential storage — owned by `security`