Stop Copy-Pasting Privacy Policies From That One Blog Post
You've built the app. It works. It's tested. And now you're staring down the barrel of a legal document you need to publish before you can ship—something about data collection, consent, and third-party services that you're pretty sure you're supposed to have. So you do what everyone does: you find a template online, swap out the app name, and hope for the best. The App Privacy Policy Generator is a free, open-source web app that tries to make that process a little more structured, supporting Android, iOS, KaiOS, and Web apps.
What It Does
It's a wizard-driven generator. You fill out a form, select the data your app actually collects, and it produces a privacy policy or Terms & Conditions document. You pick from three flavors—Simple, No Tracking, or GDPR—and the generated text adapts depending on whether you're targeting mobile, web, or both platforms combined.
There are a few knobs worth knowing about. You can set the age of consent, add an AI disclosure, note location tracking, and specify PII fields. When you're done, you can export the result as a preview, an HTML file, or a Markdown file. The whole thing also works offline as a PWA, which is a nice touch if you're drafting on a plane or just don't want another tab open.
Under the hood, it's a Go project (you'll need Go 1.25 or later), with a Makefile-driven workflow and Firebase Hosting for deployment. Nothing exotic—which is arguably the point.
Why It's Cool
The output adapts to your platform. A lot of policy generators hand you one generic blob. Here, the text changes based on whether you're shipping a mobile app, a web app, or both. That's a small detail, but it's the kind of thing that makes the result feel less like a fill-in-the-blank and more like something written for your actual situation.
The compliance options are concrete, not vague. Instead of a single "privacy policy" output, you choose between Simple, No Tracking, and GDPR variants. For a solo developer or small team, that's a useful shortcut—you don't need to know the exact regulatory language to get a document that at least reflects the right posture.
It runs offline as a PWA. This is a genuinely practical design decision. Policy drafting often happens in the gaps of a workday, and not needing a network connection means one less thing in the way.
Multiple export formats. Preview, HTML, or Markdown. If you're maintaining a docs site or a repo, Markdown is the format you actually want. Getting it directly saves a conversion step.
The contribution policy is refreshingly honest. The README states plainly that the project accepts bug fixes only, with feature proposals going through an issue first. That's a maintenance-boundary decision you don't see often enough, and it's a reasonable signal that the project is being run with sustainability in mind rather than scope creep.
How to Try It
You can skip the setup entirely and use the hosted version at app-privacy-policy-generator.nisrulz.com. Fill out the wizard, pick your options, and export.
If you want to run it locally—or poke at the source—clone the repo and use the Make targets:
make format
make check
make serve
That last one spins up a dev server on port 8000. You'll need Go 1.25 or later installed. The make check target runs Go checks and E2E tests, installing Node dependencies on demand, so you don't have to manually wire that up.
The repo is at github.com/nisrulz/app-privacy-policy-generator. There's development and localization documentation in the docs/ folder if you want to dig in, and an AGENTS.md file covering project layout and conventions. If you find a bug, the issue templates are set up and ready.
Final Thoughts
This is a focused utility, and it knows it. It won't replace a lawyer, and it doesn't claim to—but for indie developers and small teams who need a reasonable starting document without paying for a consultation, it fills a real gap. The project is licensed under AGPLv3 and maintained by Nishant Srivastava and contributors, with sponsorship options if it saves you time. If you've been putting off the policy page because the legalese felt like a wall, this lowers that wall considerably.
Follow @githubprojects for more developer tools and open source projects.