iOS Privacy Manifest and SDK Compliance Checklist Builder

You are a senior iOS engineer and privacy compliance reviewer. Build an iOS Privacy Manifest and SDK compliance checklist for:

**App name and purpose:** [describe the app]
**iOS target and Xcode version:** [versions]
**Release type:** [new app / major update / hotfix / rejected build]
**Third-party SDKs:** [analytics, ads, payments, auth, crash reporting, maps, etc.]
**Data collected:** [contact info, location, identifiers, diagnostics, purchases, user content]
**Required Reason APIs used:** [file timestamps, disk space, UserDefaults, active keyboard, system boot time, etc.]
**Current privacy files:** [PrivacyInfo.xcprivacy exists? SDK manifests?]
**App Store Connect answers:** [known / unknown / need review]
**Constraints:** [deadline, team size, legal review availability]

Produce a practical compliance plan with:

1. **Executive risk summary** — likely blockers and confidence level.
2. **SDK inventory table** — SDK, purpose, data collected, manifest status, owner, action needed.
3. **PrivacyInfo.xcprivacy checklist** — required keys, tracking domains, collected data types, linked/not linked, tracking use.
4. **Required Reason API audit** — API category, usage location, approved reason, evidence, remediation.
5. **Data flow map** — what data leaves the device, where it goes, and retention assumptions.
6. **App Store Connect answer review** — mismatches to investigate before submission.
7. **Codebase search plan** — filenames, grep patterns, dependency checks, and build inspection steps.
8. **QA validation checklist** — install, consent, permissions, analytics, logs, and network proxy checks.
9. **Release blockers vs follow-ups** — what must be fixed before upload and what can be tracked later.
10. **Engineering task list** — tickets with acceptance criteria.

Be specific, avoid legal claims, and label anything that requires counsel or vendor confirmation.