Do I need a privacy policy to publish an app?

Yes, on both stores. App Store Connect requires a privacy policy URL for every app before you can submit, and Google Play requires one on every store listing. It applies even if your app collects nothing — the policy still has to exist at a public URL and say so.

Where do I host the privacy policy?

At a stable, public URL on a domain you control, such as yourapp.com/privacy. It has to load for a signed-out visitor on any device, without a login, a redirect chain or a download prompt. Document-sharing links are a common rejection reason.

Does analytics count as collecting data?

Yes. If an analytics, crash-reporting or advertising SDK sends identifiers, device information or usage events off the device, that counts as collection for Apple's App Privacy label and Google's Data safety form — even when the data is anonymised and even if you never open the dashboard.

Do I need a support URL too?

On iOS, yes. Apple requires a support URL for every app, separate from the privacy policy URL, pointing at a page where a user can actually get help. Google Play requires contact details on the listing. One small site covers both, which is why this tool also generates a support page.

Is a generated privacy policy good enough for review?

It gives you the correct structure and the standard clauses, which is most of the work. What it cannot know is your dependency list — reconcile the generated text against the SDKs your app actually ships with before you submit, because the store declarations are checked against real behaviour. This is a template, not legal advice.

AI Generator Deals Blog

App Privacy Policy Generator

Apple will not review your app without a public privacy policy URL, and Google Play requires one for every listing. Tick what your app collects and get a policy plus a support page you can publish today.

App Name

Developer or Company Name

Contact Email

Where you will host it (optional)

What does your app collect?

These match Apple's App Privacy label categories. If an SDK sends it off the device, it counts — even if you never look at the data.

AnalyticsUsage events, screen views, device identifiersCrash reportingCrash logs, diagnostics, device stateAdvertisingAd networks, advertising identifiersAccount or email sign-inName, email address, user IDLocationPrecise or coarse device locationIn-app purchasesPurchase history, subscription statusOther third-party SDKsPush, auth, storage, backend services

What to generate

Privacy policySupport page blurb

This is a template, not legal advice. Reconcile it against your actual dependency list before you submit — the store declarations are checked against what your app really sends.

Privacy Policy

Fill in the form and click Generate to see your policy here.

Now it has to be a public URL

App Store Connect and Play Console both want a link, not a document. Reviewers routinely reject document-sharing links and pages behind a login, so the policy needs to live at a stable address on a domain you own.

Get the domain Publish the page

Check your app nameApple enforces unique app names — a collision is a hard rejection.Open the checker The full launch pathEight steps from an app idea to a live listing, in order.Ship an App

Privacy policy requirements, answered

Do I need a privacy policy to publish an app?: Yes, on both stores. App Store Connect requires a privacy policy URL for every app before you can submit, and Google Play requires one on every store listing. It applies even if your app collects nothing — the policy still has to exist at a public URL and say so.
Where do I host the privacy policy?: At a stable, public URL on a domain you control, such as yourapp.com/privacy. It has to load for a signed-out visitor on any device, without a login, a redirect chain or a download prompt. Document-sharing links are a common rejection reason.
Does analytics count as collecting data?: Yes. If an analytics, crash-reporting or advertising SDK sends identifiers, device information or usage events off the device, that counts as collection for Apple's App Privacy label and Google's Data safety form — even when the data is anonymised and even if you never open the dashboard.
Do I need a support URL too?: On iOS, yes. Apple requires a support URL for every app, separate from the privacy policy URL, pointing at a page where a user can actually get help. Google Play requires contact details on the listing. One small site covers both, which is why this tool also generates a support page.
Is a generated privacy policy good enough for review?: It gives you the correct structure and the standard clauses, which is most of the work. What it cannot know is your dependency list — reconcile the generated text against the SDKs your app actually ships with before you submit, because the store declarations are checked against real behaviour. This is a template, not legal advice.

More on this in the privacy policy URL guide and do I need a website to publish an app.