App Store Privacy Policy Generator for iOS Apps
Work through six short steps and get a privacy policy for your iPhone or iPad app, written only from the data and SDKs you tick, such as AdMob, Firebase and analytics. Download it as HTML, TXT or Markdown for the privacy policy URL App Store Connect asks for, and get a table that sorts your data into Apple's App Privacy categories. Nothing you type is uploaded.
- Answers stay in your browser
- No sign-up
- HTML, TXT or Markdown
- Built by Mohamed Nasreldeen
Build your privacy policy
Answer a few questions and your policy builds live. Only what you select is included.
Live preview
Your privacy policy will appear here as you fill the form.
How to generate your App Store privacy policy
Enter your app and developer details
Add your app name, developer or company name, contact email, and select iOS (you can also tick Android if you ship on Google Play). These fill the policy's introduction and its Contact Us section.
Select the data and SDKs you actually use
Tick only the data types you collect (email, name, device identifiers, location, usage data) and the third-party services in your build, such as Firebase, Google Analytics, AdMob, or crash reporting. The tool writes clauses only for what you select, so there are no irrelevant boilerplate sections.
Review, copy, and publish
Read every clause, adjust wording for your business, and use the Apple privacy-label helper to cross-check the data types you declared against your App Store Connect questionnaire. Then copy the policy or download it as HTML, TXT, or Markdown and host it at a public URL you can paste into App Store Connect.
What Apple requires, and what this generator covers
The privacy rules in the App Store Review Guidelines (5.1.1 and 5.1.2) and on the App Privacy details page, checked against what the tool writes.
| Apple's requirement | Rule | Who covers it |
|---|---|---|
| A privacy policy link in the App Store Connect metadata | 5.1.1(i) | Generator and you. Export the HTML, host it at a public URL and paste that URL into App Store Connect. |
| The same link inside the app, easy to find | 5.1.1(i) | You. Add it to your settings or about screen. |
| What data the app collects, how, and every use of it | 5.1.1(i) | Generator. “Information We Collect” lists each data type you tick with its purpose. Add how it is collected where that is not obvious. |
| Confirm that third parties you share data with (analytics, ad networks, SDKs) give the same or equal protection | 5.1.1(i) | You. The policy names each SDK and links its own policy, but does not write this confirmation. Suggested sentence below. |
| Retention and deletion policy, and how to revoke consent or request deletion | 5.1.1(i) | Generator. “Data Retention” and “Your Rights” are always included; tick a deletion option in step 5 to add “Account and Data Deletion”. |
| Account deletion inside the app, if users can create an account | 5.1.1(v) | You. The policy can describe it; the delete button lives in your app. The account deletion page generator writes the matching web page. |
| Permission through App Tracking Transparency before tracking | 5.1.2(i) | You, in code. The policy's “Advertising” section tells users where the iOS Tracking setting is. |
| App Privacy answers in App Store Connect, including data your SDKs collect | App Privacy details | Helper and you. The App Store helper under the form sorts your data into Apple's categories; you enter the answers yourself. |
For the third-party row, a sentence like this follows Apple's wording: “Any third party with whom we share user data, including analytics tools, advertising networks and third-party SDKs, provides the same or equal protection of user data as stated in this policy.” Add it under “Data Sharing and Third-Party Services”, and only if it is true for every SDK you use.
From your answers to Apple's App Privacy labels
The App Store helper files each data type you tick under one of Apple's categories. This is the mapping it uses.
| You tick | App Privacy category |
|---|---|
| Name, Email address, Phone number, Account information | Contact Info |
| Device ID, Advertising ID | Identifiers |
| Location | Location |
| Photos / Camera, Files / Documents, Messages / User content | User Content |
| Payment information | Financial Info |
| App usage data | Usage Data |
| Crash logs, Diagnostics | Diagnostics |
For each category, App Store Connect asks two more things. Linked to you: Apple treats data as linked unless it was de-identified before collection and you never try to re-link it. Used to track you: tracking means combining your app's data about a user with other companies' data for targeted ads or ad measurement, or sharing it with a data broker. The helper answers “yes” to tracking when you tick AdMob, the Facebook SDK, the Advertising ID or App Tracking Transparency. This page ticks App Tracking Transparency for you, so untick it in step 2 if your app does not track. Apple also counts the data that third-party SDKs in your app collect, so check each SDK's own disclosure.
Using AdMob in an iOS app
Google's publisher privacy disclosure policy says an app that shows its ads must have, and follow, a privacy policy that clearly discloses the data collection, sharing and use that come from using Google's products, including cookies, IP addresses and other identifiers. Google also requires you to comply with its EU user consent policy.
For the App Privacy answers, Google publishes what the Google Mobile Ads SDK collects on iOS: the IP address (used to estimate location), crash logs, performance data, device IDs including the advertising identifier, advertising data such as which ads were seen, and product interactions such as taps. Linking the advertising identifier with other companies' data for ads is tracking in Apple's sense, so the App Tracking Transparency prompt applies.
When you tick Google AdMob in step 4, the policy names it with a link to Google's own page, adds an “Advertising” section that explains the advertising identifier and the iOS path Settings → Privacy & Security → Tracking, and the helper marks the app as tracking. Shipping an ad-supported Android app instead? The AdMob privacy policy generator starts with Android, AdMob and the advertising ID already selected.
This generator writes a reviewable template, not legal advice, and it does not by itself make your app compliant with the App Store Review Guidelines, the GDPR, the CCPA or any other law. Read every clause, change anything that does not match how your app really handles data, and have a lawyer review it if you target children, handle health or financial data, or sell in many regions. You stay responsible for both the policy and your App Privacy answers. For the background, read do you need a privacy policy for your app.
Frequently asked questions
Does this create my Apple privacy nutrition labels automatically?
No. App Store Connect's App Privacy questionnaire can only be completed inside your account. This tool gives you an Apple privacy-label helper that summarizes the data types and purposes you selected so you can answer the questionnaire consistently, but you still enter those declarations yourself in App Store Connect.
What privacy policy does App Store Connect actually require?
Guideline 5.1.1(i) asks for a link to your privacy policy in the App Store Connect metadata and inside the app, plus separate App Privacy answers about data collection, linkage to the user and tracking. This generator builds the policy you host at that URL: download it as HTML and publish it on your own domain or hosting before you submit.
Does an iOS app that collects no data still need a privacy policy?
Yes. Guideline 5.1.1(i) says all apps must include a link to their privacy policy. Switch off “My app collects data” in step 3 and the policy states that the app does not collect personal data, while still naming any SDKs you tick in step 4.
What does my privacy policy need if the app shows AdMob ads?
Google's publisher policies require a privacy policy that discloses the data collected, shared and used because of Google's ads, including cookies, IP addresses and other identifiers. Tick Google AdMob and the Advertising ID here to add those clauses, and list the Google Mobile Ads SDK's data in your App Privacy answers.
Will the generated policy make my app legally compliant?
No. It is a reviewable template, not legal advice and not a substitute for a lawyer. It reflects only the data and services you select, so you must read it, correct anything that does not match your app's real behavior, and seek professional legal review before relying on it.
Does it cover SDKs like Firebase, AdMob, and Google Analytics?
Yes. Each service you tick in step 4 is named under “Data Sharing and Third-Party Services” with a link to the provider's own page. Firebase Analytics, Crashlytics, Google Analytics and Sentry also add an Analytics section, and AdMob or the Facebook SDK add an Advertising section. Check each provider's current documentation, since an SDK can collect identifiers or usage data that affect both your policy and your App Privacy answers.
Is my data uploaded anywhere when I use this tool?
No. The generator runs 100% in your browser as a client-side form, so the app name, data choices, and SDK selections you enter are never uploaded to a server. You get the result by copying it or downloading an HTML, TXT, or Markdown file locally.
Can I use the same tool for Google Play as well as the App Store?
Yes. Select Android to include a Google Play Data Safety helper alongside the Apple privacy-label notes, so a single cross-platform policy can support both store submissions. Review each store's questionnaire separately, as Apple and Google categorize data differently.