← IndexEntry № 149·legal

Draft a Starter Privacy Policy and Terms of Service

Produces a starter privacy policy and terms of service draft with placeholders and flags for regional legal tailoring.

Optimized for
ChatGPTClaude
§ When to use this

Every product that collects user data needs a privacy policy and terms of service, and most early teams cobble them together from whatever they can find. This prompt drafts a starter set tailored to your product, regions, and the third parties you share data with, so you begin from something coherent instead of a borrowed template. The draft uses plain headings and leaves placeholders where specifics are unknown, and crucially it flags where regional regimes like GDPR or CCPA may require additional language. That flag list is your roadmap for what still needs real legal input. This is a drafting aid, not legal advice. Privacy law is jurisdiction-specific and changes often, and the wrong disclosures can create regulatory exposure, so a qualified attorney should review before you publish. Treat the output as a structured first draft to hand to counsel, not a ready-to-post policy.

§ The Prompt— fill in the fields, then copy or open in a tool
§ Customize0/5 fields filled
your prompt — fill the fields above
You are an experienced policy drafting assistant. Draft a starter privacy policy and terms of service for [PRODUCT NAME], a [PRODUCT TYPE] operated by [COMPANY] serving users in [REGIONS]. The privacy policy should cover what data is collected, how it is used, [THIRD PARTIES] it is shared with, retention, user rights, and contact info. The terms should cover acceptable use, accounts, payment, disclaimers, limitation of liability, and governing law. Use plain headings and placeholders where specifics are unknown. After the draft, list assumptions and flag where regional law (e.g., GDPR or CCPA) may require tailoring. Close by recommending review by a qualified attorney, as this is a drafting aid, not legal advice.
Open with your prompt →ChatGPTClaudeSends your filled-in prompt straight into a new chat.
§ Example Output

What you can expect back

PRIVACY POLICY - TrailLog (operated by Summit Labs Inc.)

1. Data We Collect: account info, location and activity data, device info.
2. How We Use It: to provide tracking features, improve the app, and process payments.
3. Sharing: with analytics and payment processors under contract; we do not sell personal data.
4. Retention: kept while your account is active, then deleted within [X] days.
5. Your Rights: access, correction, deletion; EU users have GDPR rights.
6. Contact: [privacy email].

TERMS OF SERVICE
1. Acceptable Use ... 2. Accounts ... 3. Payment ... 4. Disclaimers (provided 'as is') ... 5. Limitation of Liability ... 6. Governing Law: [state].

Assumptions: no children's data; no health-data classification. Flags: GDPR needs a lawful-basis and DPO section; CCPA needs a 'Do Not Sell' notice. Drafting aid, not legal advice; have an attorney review.

Illustrative example — your results will vary by tool and inputs.

§ Pro Tips

Get sharper results

  • 01Make sure the policy describes what your product actually does; a mismatch between policy and practice is a common compliance failure.
  • 02Treat the GDPR/CCPA flags as a to-do list for counsel rather than optional extras.
  • 03Use a real monitored contact channel for privacy requests, not a placeholder, before you publish.
  • 04Have a qualified attorney review before launch; privacy law is jurisdiction-specific and incorrect disclosures can create regulatory exposure.
§ Variations

Adapt it for your case

GDPR-focused

Ask the model to expand the privacy policy with lawful-basis, data-subject-rights, and transfer sections for EU users.

Cookie notice

Request a separate cookie/tracking notice suitable for a website banner.

Plain-language layer

Have it add a short, friendly summary at the top of each document for users.

Best For — Roles
Use For — Tasks
Tags#privacy-policy#terms-of-service#first-draft
§ FAQ

Common questions

Is this legal advice?

No. It produces a structured first draft. Privacy law is jurisdiction-specific and changes frequently, so a qualified attorney should review before you publish.

Can I publish this as-is?

No. Fill the placeholders, address the GDPR/CCPA flags, and have counsel review; incorrect disclosures can create regulatory risk.

Does it cover every region's law?

No. It flags major regimes like GDPR and CCPA based on the regions you list, but a qualified attorney should confirm coverage for your specific markets.

§ Related Entries

You may also need