A plain-language privacy policy built from what your site actually does, tick only what applies, and the policy says only that.
A privacy policy is a promise written down: what data you collect, why, who else touches it, and what choices people have. This generator builds that promise from your actual practices, each ticked box adds the matching honest section and unticked boxes add nothing, so the policy never claims practices you do not have or omits ones you do. The output follows the structure regulators and app stores expect: collection, use, sharing, cookies, retention, security, user rights, children's privacy (when relevant), changes, and contact.
The necessary legal note, stated as plainly as the policy itself: this is a template, not legal advice. Privacy law varies by where your users live, GDPR in Europe, CCPA/CPRA in California and a growing list of state and national laws impose specific rights and wording. A small site whose practices are simple and honestly described is most of the way there; businesses collecting sensitive data, selling data, or operating at scale should have the result reviewed by a privacy lawyer. Keep the policy updated whenever practices change, an outdated policy is worse than a short one.
Do I legally need a privacy policy? Almost certainly if you collect anything, analytics alone counts in many jurisdictions, and app stores require one regardless. If your site truly collects nothing (no forms, no analytics, no cookies), a short 'we collect nothing' statement like this site's own is the honest policy.
What if I use none of the listed services? Generate with nothing ticked: the policy states the site collects no personal data beyond server logs, uses no tracking cookies, and shares nothing, a complete and valid policy for a static site.
How often should it be updated? Whenever a practice changes, a new analytics tool, a newsletter launch, a payment provider. Re-run the generator with the new boxes ticked and bump the effective date.