Boring documents.
Done well.

A privacy policy isn't a contract — it's a disclosure of how you handle data. The legal question is whether the disclosure is accurate and complete for your business and the laws that apply to you. Our generator builds the document from your declared practices and the relevant statutes (GDPR, CCPA, COPPA, etc.), then audits the output for missing disclosures before delivery. That said, we're a tool, not a law firm. For high-stakes situations or unusual data practices, a privacy attorney is still the right call.

Two reasons. First, our cost structure: we're a small software-only operation built on a low-cost AI model, with no enterprise sales team and no ongoing per-customer service obligation. Second, the others charge monthly because they bundle hosting and update notifications into the price. We separate those: $2 buys you the document, full stop. Auto-updates and hosted policy URLs come with the optional $5/month Pro tier.

The single document you buy is a snapshot — accurate as of the day you generate it. Privacy law moves slowly (CCPA's last major amendment was 2023, GDPR's was 2018) but it does move. The Pro tier emails you when relevant law changes and offers a regenerated document at no extra cost. The single-document tier doesn't get auto-updates — you'd regenerate manually for another $2 if you wanted to refresh.

The information you enter — business name, website, integrations, data categories — flows into the language model that generates your document, then to your screen. We don't sell it, share it with third parties, or train models on it. We cache the generated document briefly so you can return to unlock it after payment, then delete it. Our own privacy policy (linked in the footer) details exactly what we keep and for how long.

Yes — two ways. Single ($2) and Free users get Markdown, HTML, and PDF downloads; edit those in whatever editor you prefer. Pro subscribers also get a built-in editor on their dashboard with paragraph-level AI rewriting, version history with diffs, and hosted policy URLs that update when you save — the AI knows the legal context of each clause so it won't let you accidentally break a required disclosure. Either way, substantial substantive changes (e.g. adding a major data category we didn't know about) are worth a re-audit via the free /audit page.

Almost always no. The privacy policy generator builds a single multi-jurisdictional document by default — the EU and California sections layer onto the same underlying disclosures rather than running as parallel policies. If your business genuinely operates as two separate legal entities (e.g. a US LLC and a separate EU GmbH with different data practices), then yes, you'd want two documents.

Pick the closest fit from the form, generate the document, then either (a) edit the result yourself, (b) re-run the /audit pipeline against your edited version, or (c) take the result to a privacy attorney as a starting draft. Lawyers charge by the hour to write documents from scratch; they charge less to review and revise an existing one. We're a starting point, not a finishing line, for any non-standard situation.