---
name: privacy-policy-draft-helper
description: "Turns a few facts about your app and its data practices into a structured first-draft Privacy Policy, with the clauses your jurisdictions usually expect and a list of gaps to fix. Use when a founder needs a first-draft Privacy Policy for an app or website and wants it matched to the data they collect and the regions they serve. Do not use for a Terms of Service, a cookie banner, or a legal opinion on compliance. Related topics: business, legal, utility."
---

# Privacy Policy Draft Helper

Turns a few facts about your app and its data practices into a structured first-draft Privacy Policy, with the clauses your jurisdictions usually expect and a list of gaps to fix.

## When to use

Use this skill when a founder needs a first-draft Privacy Policy for an app or website and wants it matched to the data they collect and the regions they serve. Do not use it for a Terms of Service, a cookie banner, or a legal opinion on compliance.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. Map each collected data type to a purpose, a sharing party, and a retention period, and mark any that the inputs leave blank as assumptions.
3. Select the jurisdiction clauses that apply (CCPA, GDPR, or both for a global audience) and confirm each one has a matching user right in the draft.
4. Handle third-party tracking and children under 13 explicitly, adding the opt-out or parental consent wording, or stating that neither applies.
5. Write the policy in plain language using the fixed section order, so every section is present and none is empty.
6. List every assumption and every point that needs lawyer review at the end of the draft.

## Inputs

- **Company or app name** (free text, e.g. "Your app name")
- **Website URL** (free text, e.g. "https://example.com")
- **Contact email for privacy requests** (free text, e.g. "privacy@yourdomain.com")
- **Data collected** (choose any: Email and names, Usage analytics, Payment info, Location data, Device IDs)
- **Third-party tracking such as Google Analytics or a Facebook Pixel** (choose one: Yes, No)
- **Target jurisdictions** (choose any: US (CCPA), Europe (GDPR), Global)
- **Children under 13 are a target audience** (choose one: Yes, No)
- **How the data is used** (longer free text)

## Output

A complete Privacy Policy draft with the fixed section order in plain language, followed by a short list of assumptions and items for legal review.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### Privacy Policy Draft Helper

Draft a first-version Privacy Policy for my product. This is a starting draft for a lawyer to review, not legal advice.

- Company or app name: {{Company or app name}}
- Website URL: {{Website URL}}
- Contact email for privacy requests: {{Contact email for privacy requests}}
- Data collected: {{Data collected}}
- Third-party tracking such as Google Analytics or a Facebook Pixel: {{Third-party tracking such as Google Analytics or a Facebook Pixel}}
- Target jurisdictions: {{Target jurisdictions}}
- Children under 13 are a target audience: {{Children under 13 are a target audience}}
- How the data is used: {{How the data is used}}

Write the policy in plain language with these sections in order: what we collect, why we collect it, who we share it with, how long we keep it, user rights, children, security, changes to the policy, and contact details. Add the rights and legal bases that match each chosen jurisdiction (for example access and deletion rights for CCPA, lawful basis and data transfer wording for GDPR). If third-party tracking is on, name the category of tool and say users can opt out. If children are a target audience, add the parental consent and age-gate wording and flag that this needs legal review first.

Only describe practices the inputs support. After the draft, list every place where you had to assume something, so I can confirm it before publishing.

## Pitfalls

- Claiming practices the user never described, such as data deletion within 30 days, which creates a promise the company may not keep.
- Copying GDPR wording into a policy for a US-only audience, or missing it for a global one.
- Skipping the children section when the product could appeal to under 13s, which is where regulators look first.
