App Privacy Policy Generator

Answer a short questionnaire and get a complete privacy policy for your app — plus the exact answers for Apple's and Google's store forms.

Apple will not let you submit an app without a working privacy policy URL, and Google will not let you publish without filling in the Data safety form. Both checks happen at the worst possible moment — the day you are trying to ship. Most of the generators that come up when you search for one are trial funnels: you answer everything, then find the finished document behind a subscription.

This one writes the whole policy in your browser and hands it straight over. Tick what your app collects, tick the SDKs you actually bundle, and the document builds itself as you go — introduction, what you collect, why, legal bases, every third-party service named individually, retention, security, GDPR and CCPA rights, children's privacy, and contact details. Copy it as text or HTML, or download it as an .html file you can host as-is.

Then there is the part nobody helps with. The same answers drive a store form cheat sheet that tells you exactly which data types to tick in App Store Connect, whether each one is linked to identity, whether it counts as tracking, and what to select in Play Console's Data safety section. Getting those two forms to agree with your policy is what actually stops a rejection.

Nothing is uploaded. Every answer stays in this browser tab, the policy is written by JavaScript running on your device, and nothing is saved when you close the page.

Your app

Platforms
Accounts

What the app collects

Personal data collected

Third-party services

Third-party services used

Sharing & scope

Do you share personal data with third parties beyond the services above?
Do you sell personal data?
Is the app directed at children under 13?
Regions to cover

Retention & deletion

0 words

Watch: how to use this tool

How to use it

  1. Enter your app name, company name, contact email and effective date.
  2. Tick every kind of personal data the app collects — including the data your analytics and crash SDKs send automatically.
  3. Tick the third-party services you bundle, so each one gets named in the policy with a link to its own privacy policy.
  4. Choose the regions you need to cover — GDPR, CCPA/CPRA, or general — and set your retention and deletion answers.
  5. Read the live preview on the right, then copy the policy or download it as .html or .md.
  6. Open the Store form cheat sheet tab and use it to fill in Apple's App Privacy questionnaire and Google Play's Data safety form.
  7. Have a lawyer review the policy before you submit the app.

Questions

Does Apple require a privacy policy URL?
Yes — for every app on the App Store, with no exceptions, even a free app that collects nothing. The URL goes in App Store Connect under App Information, it must be publicly reachable without a login, and Apple checks it during review. Google Play requires one too, in the App content section of the Play Console.
Where do I host the privacy policy?
Anywhere stable and public. A page on your marketing site is ideal, for example yourdomain.com/privacy. If you have no site yet, a GitHub Pages page, a Notion page published to the web, or a Google Sites page all work — the store only needs a URL that loads for anyone, forever, without a login or a redirect to an app.
Is this legal advice?
No. This tool produces a solid starting template built from the answers you gave, covering the sections app stores and privacy regulators expect. It cannot know everything your app does, and generating a document does not make you compliant with the GDPR, the CCPA or COPPA. Read every line, correct anything that is wrong, and have a lawyer review it before you launch.
Is anything I type uploaded or stored?
No. The questionnaire and the policy generator both run as JavaScript inside your browser tab. Nothing is sent to a server, nothing is saved, and closing the tab erases everything. That is also why there is no signup and no email gate.
What counts as tracking in Apple's App Privacy form?
Tracking means linking data from your app with data from other companies' apps or websites for advertising or advertising measurement, or sharing data with a data broker. If you bundle AdMob or the Meta SDK, you are almost certainly tracking, you must declare it, and you must show the App Tracking Transparency prompt before accessing the advertising identifier. Plain analytics you use only inside your own app is not tracking.
Do I need to update the policy when I add an SDK?
Yes, and you need to update both store forms too. Adding a single analytics or attribution library changes what data leaves the device, which changes your App Privacy answers, your Data safety answers, and the third-party services section of the policy. Re-run this tool with the new answers and republish.

Built by US APP Team

Need more than a free tool?

We build custom mobile apps for founders and small businesses — idea to live on the App Store and Google Play. Fixed price, no surprises, and you own the code.

Get your app built properly Takes about 3 minutes · or book a free intro call