Why an offline app still needs a privacy policy
Google Play requires a privacy policy link on every app listing since 2023, regardless of what the app collects. A bundled HTML app that talks to no server is the easy case: the honest policy is three paragraphs saying so. The mistake is not writing one, or copying a generic template that claims you collect analytics you do not — Play's reviewers compare the policy with the Data safety form and with what the app actually requests, and a mismatch is a rejection.
This generator writes the policy from the boxes you tick. Tick nothing but "bundled" and "local data" and you get a short, accurate document stating that no personal information is collected. Tick analytics, ads or accounts and the matching sections appear, naming the third party and linking to its policy.
What to check before you publish it
- Every sentence must be true. If the app loads a live URL, "loads content from our website" must be ticked, because your server sees IP addresses. If you added push notifications in the builder, tick push.
- The contact email must work. Play requires a way to reach you, and people do use it.
- Host it somewhere public and stable. A page on your own site, a GitHub Pages file, or a Firebase Hosting page. The URL cannot require a login and should not change — Play links to it from the listing.
- Keep it in sync with the Data safety form. The Data Safety Form Helper works from the same questions so the two agree.
Not legal advice
The generated text is a plain-English starting point that matches Google Play's expectations for a small app. Laws differ by country (GDPR in Europe, CCPA in California, and others) and an app with a real user base, payments, or children as its audience should have its policy reviewed by someone qualified. For a portfolio app, a class project or a small tool, the generated document is honest and complete.