Do I really need a privacy policy for a small site?

If you collect anything — names, emails, form submissions, analytics, payments — then almost certainly yes, and the specifics depend on where you and your visitors are. A plain, accurate description of what you collect and why is both the legal expectation and what earns trust.

Can I use the pages this prompt produces as they are?

Treat them as an honest draft, not final legal advice. They will describe your actual site accurately, which is more than a copied template does, and that makes a lawyer's review shorter and cheaper. Anything involving health data, children, or regulated professions should be reviewed before it goes live.

Why not just copy another site's policy?

Because it describes their data practices, not yours, so it is wrong in exactly the places that matter — and it may be copyrighted. A policy that does not match what your site actually does is worse than none, since it is a documented inaccurate promise.

Compliance & Legal

Add the legal pages your site needs

Get honest, readable privacy, terms and cookie notices in place — drafted for your lawyer to check, not copied from a random site.

Time: ~15 minutes, plus your review Difficulty: Beginner Works with: Base44 / Lovable / v0

When to use this

Before you launch, and again whenever you start collecting something new.

Before you start

A list of what your site collects: every form, every login, any payments, any analytics.
The name of the country/state your business operates from, and where your customers mostly are.
A contact email for privacy questions.
The knowledge that this produces a draft — not legal advice.

The prompt

Create the legal pages this site needs, written in plain readable language, and mark them clearly as drafts for my review.

Base them on what this site actually does, not on generic templates. My business: [NAME], [WHAT YOU DO], based in [COUNTRY/STATE]. My customers are mainly in [COUNTRIES OR REGIONS]. My contact email for privacy questions: [EMAIL].

Create:
1. A privacy policy that lists exactly what this site collects (go through every form and feature and list them specifically), why, how long it is kept, who else can see it (name the services this site actually uses), and how someone can ask to see or delete their data.
2. Terms of use covering what the service is, acceptable use, payment and refund terms if the site takes money [DESCRIBE YOUR POLICY], liability limits in plain language, and how disputes are handled.
3. If the site uses cookies or analytics: a short cookie notice and a consent banner that actually works — declining must not break the site, and the choice should be remembered.

Link all of them in the footer of every page.

Do not invent claims about certifications, insurance or compliance standards. Where something depends on my specific situation, leave a clearly marked note telling me what to confirm rather than guessing.

Already building? Paste this into your project. Starting fresh? Open a free account with a compatible builder below.

Build it on

Start free with Base44 Read Review: Base44

Start free with Lovable Read Review: Lovable

Start free with v0 Read Review: v0 by Vercel

How we make money

What this creates

A privacy policy based on what your site actually does
Terms of use in readable language
A cookie notice and working consent banner, if relevant
Footer links on every page
Marked notes wherever your specific situation needs confirming

Check it worked

Paste the prompt, wait for the build to finish, then confirm these — in plain language, no technical checks needed:

The privacy policy mentions your actual forms and features by name — if it's generic, it wasn't done properly
Links appear in the footer of every page and open correctly
If you declined cookies, the site still works normally
Every "check this with a professional" note is visible rather than buried

Something missing? That's normal — ask for it in one short follow-up message rather than re-running the whole prompt.

Next steps

Add the disclaimer your profession needs

If you're in a regulated or advice-giving field

Add a clearly visible disclaimer appropriate for my field: [YOUR FIELD, e.g. coaching is not therapy; content is general information and not medical/legal/financial advice]. Place it in the footer of every page and at the end of any page where I give guidance. Mark it as a draft for my review.

You'll know it worked when: The disclaimer appears in the footer and on your guidance pages.

Explain your prices honestly

If you sell anything on the site

Add a clear section covering: what is included in each price, whether taxes are included [YOUR SITUATION], when payment is taken, my refund and cancellation policy [DESCRIBE IT], and how a customer contacts me about a problem. Write it in plain language and place it where customers see it before paying, not only in the terms.

You'll know it worked when: A customer can find your refund policy before they pay, without hunting.

Make an accessibility statement true

After doing accessibility work — never before

Write an accessibility statement describing what has actually been done on this site to make it usable for people with disabilities, what is known to be imperfect, and how someone can report a problem to me at [EMAIL]. Be honest — do not claim a standard we have not verified.

You'll know it worked when: A statement that describes reality, with a working contact route for problems.

Watch out for

This is a draft, not legal advice. For most small business sites it's a solid, honest starting point; if you handle health, financial, or children's data, or sell across borders, have a professional read it. That review is cheap compared to the alternative.
Never copy another company's policy. It's their document describing their systems — and using it is both inaccurate for you and a copyright problem.
Update it when you change what you collect. The day you add a newsletter, a chat widget or payments, the policy is out of date.
Cookie banners that block the site when declined are illegal in several places — test declining before you launch.

Platform notes

Identical across platforms — this is content, not capability. What differs is what your site collects, which is why the prompt asks it to inventory your actual forms rather than assume.

Spend fewer credits

Every builder charges you for the work its AI does — so the cheapest habit is thinking before you build. These six rules cut most of the waste, whichever platform you choose.

Plan in a free chat first. Sketch the whole thing in ChatGPT, Claude or Gemini — pages, features, what each form collects, what it should look like. Thinking there is free; thinking inside a builder is billed.
Start from a written prompt, not a sentence. "Make me a website" is the most expensive sentence in AI building. A complete first prompt — like the ones on this site — saves dozens of correction rounds.
Don't be lazy with the details. Every detail you leave out comes back as a correction you pay for. Business name, colors, every page, every form field, what happens after someone submits — put it all in the first prompt.
One change per message afterwards. "Fix the header, and the form, and the colors" produces a tangle that costs more to unpick than it saved.
Stuck? Stop patching. If the same fix fails about three times, don't send a fourth correction — describe the whole section's desired end state in one fresh message instead.
Start free. Upgrade when you need more. Use the free allowance to build and explore your first version. Upgrade when you need more usage or paid features, and check any connected service costs before launch.

The prompts on this page are written to do most of this work for you — that's the point of them.

Read the full guide

Related playbooks

Related prompts

Part of these kits

privacy terms cookies gdpr

Last reviewed: 2026-07-27