App Privacy Policy Generator

App Store Connect will not take a submission without a privacy policy URL. This writes one from the same data categories Apple uses in its own App Privacy questionnaire, so the policy and your App Store answers say the same thing.

This is a draft built from what you tick, not legal advice. Nothing here has seen your app, your SDKs or your network traffic, and it cannot know what law applies to you. Read every line before you publish it, and have a lawyer read it if your data handling is anything but routine.

The app

Optional: pick it from the App Store to fill the name and developer.

What the app collects

Apple’s own categories — the same list as the App Privacy questionnaire. Only tick what is true.

Not sure what to tick? The privacy label worksheet walks the same categories with Apple’s own definitions and examples.

A complete page to upload. This is the one App Store Connect links to.

Fill these in first

  • App name — The policy has to name the app it covers.
  • Company or developer name — The policy has to name who publishes the app.
  • Contact email — A privacy policy has to give an address people can write to.
  • Data collected — Answer what the app collects. An untouched list must never publish as “this app collects nothing” — only you can say which it is.
  • Policy — [COMPANY] is still unfilled.
  • Policy — [CONTACT EMAIL] is still unfilled.
  • Policy — [DATA COLLECTION] is still unfilled.

Host the HTML anywhere and paste the URL into App Store Connect under App Privacy. Need the support page and a landing page too? The landing page builder produces all of them as one site, using this same policy.

Just the body HTML
      <p>Effective 2026-08-26.</p>
      <p>This policy explains what the app collects and what happens to it. [COMPANY] publishes the app on the App Store.</p>
      <h2>What we collect</h2>
      <p>[DATA COLLECTION]</p>
      <h2>Why we collect it</h2>
      <p>Data is used to run the features described on this site, to keep the app working, and to answer you when you get in touch. It is not sold.</p>
      <h2>Tracking</h2>
      <p>the app does not track you. Data collected in this app is not linked with data from third-party apps or websites for advertising, and it is not shared with data brokers.</p>
      <h2>Third parties</h2>
      <p>the app does not share your data with third-party services.</p>
      <h2>How long we keep it</h2>
      <p>Data is kept for as long as it is needed to provide the app. You can ask us to delete what we hold about you by writing to the address below.</p>
      <h2>Your choices</h2>
      <p>You can ask what we hold, ask for a copy, or ask us to delete it. Deleting the app from your device stops any further collection.</p>
      <h2>Children</h2>
      <p>the app is not directed at children. If you believe a child has provided us with personal information, contact us and we will delete it.</p>
      <h2>Changes</h2>
      <p>If this policy changes, the new version is published on this page with a new effective date.</p>
      <h2>Contact</h2>
      <p>Questions about this policy: [CONTACT EMAIL]</p>

Why does App Store Connect block a submission without a privacy policy URL?

Apple requires a privacy policy URL for every app, no exceptions, and shows it on the product page. It has to be a live page on a domain you control, and it has to describe what your app actually collects. For most solo developers this is discovered at submission time and solved with whatever generic template loads first.

This writes one from Apple’s own data categories — the same groups you answer in the App Privacy questionnaire in App Store Connect. That matters more than the prose: reviewers and users read the two side by side, and a policy phrased in different words than your App Privacy answers is a policy that appears to contradict them.

How it works

  1. 1Optionally pick your app to fill in the name and the developer. Only those two fields come from the listing — what an app collects is invisible from outside it, and nothing here will guess.
  2. 2Tick the data categories the app collects. Each one is Apple’s own group name, so the policy and your App Privacy answers use identical vocabulary.
  3. 3Answer the two questions most templates get wrong: whether the app tracks users across other companies’ apps and websites in Apple’s sense, and which third-party services process data on your behalf. Analytics, crash reporting, ad networks and login SDKs are all third parties, and Apple treats what they collect as data you collect.
  4. 4Take it as a complete HTML page, as Markdown for a README or a docs site, or as plain text. Host it and paste the URL into App Store Connect under App Privacy.

What it cannot tell you

  • It is a draft assembled from what you tick, and it is not legal advice. Nothing here has seen your app, your SDKs or your network traffic, and it cannot know which laws apply to where you and your users are. Read every line, and have a lawyer read it if your data handling is anything but routine.
  • It makes no compliance claim. The policy never says “GDPR compliant”, never names a legal basis for processing, and never describes a control nobody confirmed exists — because a document generated from nine form fields cannot know any of those things.
  • An untouched category list is treated as an unanswered question, not as “this app collects nothing”. Publishing that sentence when it is false is the most consequential thing this tool could do, so the download stays blocked until you say which it is.
  • The third-party SDK trap is the one thing it can warn about and cannot check. If you ship an analytics or crash-reporting SDK, that data is collected by you as far as Apple is concerned, whether or not you ever look at it.
  • No score, no pass mark, no green tick. A tick on a legal document is an invitation to stop reading it.

Frequently asked questions

Does Apple accept a generated privacy policy?

Apple requires a working URL with a policy that describes your app’s data handling; it does not certify generators, and nobody can promise a specific review outcome. What this produces is a policy phrased in Apple’s own data-category vocabulary, so it reads consistently with the App Privacy answers you give in App Store Connect.

My app collects nothing at all. Do I still need a policy?

Yes — Apple requires the URL regardless. Tick nothing, confirm that the app collects none of the categories, and the policy says so plainly. Check your SDKs first: an analytics or crash-reporting library collects data on your behalf.

Where should I host it?

Anywhere that serves a static file — GitHub Pages, Cloudflare Pages, Netlify, or a page on a site you already run. If you need a support page and a landing page as well, the landing page builder produces all of them as one site using this same policy.

What is the difference between this and the privacy label worksheet?

The worksheet helps you decide what to answer in App Store Connect, with Apple’s definitions and examples for each category. This turns those same answers into the public document Apple then asks you to link. They are two halves of one job and share the same category list.

Is anything I type uploaded?

No. The document is built in your browser and the draft is kept in your browser’s local storage. The only network call this page makes is the optional App Store search that fills in your app name.