Native SwiftUI apps use a smaller, more specific set of Apple frameworks — Core Location, StoreKit, Sign in with Apple, App Tracking Transparency — but every one of them still has to be disclosed in your privacy policy before Apple will approve your app for the App Store. This page covers the Apple-first privacy disclosure stack for SwiftUI apps.
Core Location (even 'when in use' permission) means you're collecting location data. StoreKit means you're processing in-app purchases. Sign in with Apple means you're collecting account identifiers. AppTrackingTransparency requires you to declare whether you track users. Each of these maps to a category in the App Privacy questionnaire and has to be mentioned in the privacy policy.
HealthKit, HomeKit, and ResearchKit have stricter disclosure requirements because the data they touch is sensitive. If you use any of them, your policy needs explicit language about what specific health or home data you access and whether it leaves the device.
Even 'pure SwiftUI' apps often include Firebase, TelemetryDeck, Mixpanel, Sentry, or RevenueCat via Swift Package Manager. These all collect device identifiers or usage data and belong in the disclosed data categories. TelemetryDeck is worth calling out — it's marketed as privacy-first, but it still collects anonymized usage events that need to be disclosed under 'usage data'.
Toggle on the categories your app uses in BaseTerms. The generated policy references the common Apple frameworks and third-party SDKs by category (analytics, location, accounts, ads, payments). Host the page at yourapp.baseterms.com/privacy and paste the URL into App Store Connect.
Ready to ship?
Privacy Policy, Terms, Support, and Data Deletion — all 4 pages, ready to paste into App Store Connect and Google Play Console. Copy the raw Markdown free or host on a custom subdomain for $9 one-time.
One-time payment. No subscription. No renewal fees.