Privacy Policy Generator: Toggle On What Your Site Uses - Flip toggles, get real clauses

An AdSense review bounced a friend's site last spring. The problem was not thin content — it was a privacy policy that mentioned nothing about cookies while the page itself loaded analytics and ad scripts. Patching the mismatch cost 11 extra days of review.

TL;DR

• A copied template that doesn't match what your site actually runs reads worse than no policy at all
• This tool turns your setup into 8 toggles — cookies, ads, analytics, donations, comments, newsletter, embeds, CDN — and the clauses fork with them
• Sections for services you never enabled simply don't appear, so every sentence maps to something real on your site
• Take the result away as Markdown, paste-ready HTML, or a styled standalone .html file; everything stays in your browser

1. Forking clauses, not a reskinned template

Most generators hand everyone the same 3,000 words whether or not you run ads. Here the generation is forked: flip the ads toggle and the Third-party services section grows an ad-network clause and the cookie chapter starts mentioning advertising cookies; flip payments and an Orders and payments section appears. Turn everything off and the cookie section states plainly that the site sets none.

I don't recommend copying someone else's policy wholesale: clauses for services you never integrated look suspicious to visitors and give reviewers nothing to anchor on.

2. Three ways out, one source of truth

Copy the HTML straight into your page template — semantic tags, zero external dependencies. Download the .html for a styled standalone page you can upload as-is. Markdown fits docs folders and code repositories. After changing a toggle, just export again and overwrite.

3. Pick your legal register

The English page offers GDPR, CCPA (as amended by the CPRA), and General: the entire rights chapter rewrites with the register you pick. Serving a mainly domestic Chinese audience? Use the Chinese version, which defaults to the Personal Information Protection Law. The two pages are independently generated documents, not translations of each other.

4. A habit worth keeping

Every time you wire in a new third-party service — analytics, an ad network, a donation button — come back, flip its toggle, set the effective date to today, and re-export. A policy that lags reality by two services costs more trust than a shorter, accurate one.

FAQ

Can I publish the generated policy as-is? Yes, as a working draft. Check that every service you actually run — analytics, ad network, payment provider — has its toggle switched on, because the document only mentions what you enable. It covers common independent-site shapes and is not legal advice; for regulated data such as health or financial information, or sites aimed mainly at children, have a professional review it.

What actually happens when I flip a toggle? The preview re-renders within about 200 milliseconds. Enabling ads adds the ad-network clause to Third-party services along with the advertising cookies it may set; turning on payments adds the Orders and payments section. Switch everything off and the cookie section states, plainly, that the site sets none. Re-copy or re-download after changing switches.

Is my input uploaded anywhere? No. Everything you type stays in this browser. Nothing is uploaded, and there's no account. The form state is saved in localStorage on this device and never sent to a server; clearing site data or switching devices will lose it. The Clear my data button in the footer deletes it after a double confirmation.

Should I pick GDPR or CCPA? Choose by where your visitors are, not where you read about it. The GDPR option fits EU audiences, the CCPA option fits California, and General keeps a plain rights list without citing any law. If your audience spans both the EU and California, keep the stricter GDPR version and add the CCPA opt-out note yourself.

中文版：https://www.9314.cn/tools/privacy-policy-generator/