SwipeToLaunch
Add your product

Privacy policy generator

A privacy policy draft from your data, tools and laws, in Markdown or HTML.

How to use it

  1. Describe your business. Name, website, contact email and the country you operate from.
  2. Tick what you collect. Emails, accounts, analytics, cookies, payments, newsletters, uploads.
  3. List your providers. Google Analytics, Stripe, PostHog, Mailchimp and others, each linked to its own policy.
  4. Download and review. Markdown or HTML. Read every line and have a lawyer check it before publishing.

Why you need a privacy policy on day one

If your site collects anything about visitors, and an analytics script or a signup form counts, most privacy laws expect you to explain what you collect and why. The App Store, Google Play, Stripe, Google OAuth and most ad platforms also require a privacy policy URL before they approve you. It is one of the most common blockers in a launch week.

What a policy should cover

  1. What you collect: account details, email, payment info, usage data, cookies, uploaded content.
  2. Why you collect it: to provide the service, process payments, improve the product, send newsletters.
  3. Who you share it with: your processors, such as hosting, analytics, payments and email.
  4. How long you keep it and how you protect it.
  5. People's rights: access, correction, deletion and how to ask.
  6. How to contact you.

The generator only includes sections for the data and services you tick, so the draft describes your product rather than every product.

GDPR and CCPA

If anyone in the EU or UK can sign up, the GDPR applies, and your policy needs a legal basis for each use of data, the rights people have, and how you handle international transfers. California's CCPA, as amended by the CPRA, applies to businesses above certain revenue or data thresholds and requires a description of consumer rights and whether you sell or share personal information. Ticking either option adds those sections.

Before you publish

This is a template-built draft, not legal advice. Templates cannot know about your edge cases: health or financial data, children's apps, data brokers, or selling data. Check every statement against what your product really does, update it when you add a new tool, and get it reviewed by a lawyer.

Then link it in your footer, signup form and app store listing. For your terms, use the terms of service generator, and work through the rest of launch week with the launch checklist.

What you get

  • Sections built from the data you actually collect
  • 19 common providers with links to their policies
  • Optional GDPR and CCPA/CPRA sections
  • Markdown and HTML downloads
  • Runs in your browser; nothing you type is stored

Questions

Is a generated privacy policy legally valid?

It is a starting draft, not legal advice. Whether it is enough depends on your business, the data you handle and where your users are. Review it carefully and have a qualified lawyer check it before relying on it.

Do I need a privacy policy if I only use Google Analytics?

Yes. Google Analytics collects usage data and sets cookies, and Google's own terms require sites that use it to have a privacy policy that discloses it.

Does my small startup need to follow GDPR?

If you offer your product to people in the EU or UK, or monitor their behavior with analytics, the GDPR generally applies regardless of your size or where you are based.

Where should I put my privacy policy?

On its own page, usually /privacy, linked from your site footer, signup forms and app store listings. Payment and sign-in providers often ask for that URL too.

How often should I update it?

Whenever you start collecting new data or add a new service that processes personal data, and at least once a year. Change the effective date each time.