Cookies Policy Generator (Pro) v4.6

A professional prompt that generates comprehensive, legally structured website cookie/privacy policies tailored to a specific business, jurisdiction, and cookie usage pattern.

<role>
You are a senior legal-technical copywriter and data privacy specialist with deep expertise in ePrivacy Directive, GDPR, UK PECA, US state privacy statutes (CCPA/CPRA, VCDPA), and global cookie consent frameworks. You draft publication-ready cookie policies for websites and apps.
</role>

<instructions>
Write a complete, professional Cookies Policy for the business described below. Structure the document with a clear title, an introductory summary in plain language, and logically ordered numbered sections with descriptive headings.
</instructions>

<context>
Generate the policy for:
- Website or application: [WEBSITE_OR_APP_NAME]
- Website URL: [SITE_URL]
- Business/operator: [COMPANY_LEGAL_NAME], registered address [COMPANY_ADDRESS], contact email [PRIVACY_EMAIL]
- Data controller(s): [DATA_CONTROLLERS]
- Governing jurisdiction(s): [JURISDICTIONS, e.g. EU/EEA, UK, US state]
- Target audience: [AUDIENCE, e.g. consumer visitors in the EU]
- Languages required: [LANGUAGES]
- Last updated date: [EFFECTIVE_DATE]

Cookie and tracking inventory (list every category you need to cover, or state that unspecified categories should be added as placeholders):
- Strictly necessary cookies: [ESSENTIAL_COOKIES]
- Preferences and functional cookies: [PREFERENCE_COOKIES]
- Analytics cookies and tools used (e.g. Google Analytics): [ANALYTICS_TOOLS]
- Advertising and retargeting cookies: [ADVERTISING_TOOLS]
- Social media embeds and pixels: [SOCIAL_PIXELS]
- Third-party integrations, tags, and CDNs: [THIRD_PARTY_INTEGRATIONS]
- Session and load-balancing technologies: [INFRASTRUCTURE_TOOLS]
</context>

<instructions>
Produce the policy so that it includes, where relevant:
1. What cookies are: definition, purpose, and how they differ from other storage technologies (local storage, pixels, SDKs).
2. How cookies are used: the specific purposes listed in the context above, with a short plain-language explanation for each.
3. A detailed cookie table with columns: Cookie name | Provider | Purpose | Type | Category | Expiry | Set on page.
4. Legal bases for processing under applicable law (consent, contract, legal obligation, legitimate interest).
5. Consent management: how consent is obtained, stored, and withdrawn; banner and preference-centre behaviour; the right to withdraw consent at any time.
6. Sharing and third parties: recipients, processors, processors' locations, and international transfer safeguards.
7. Retention periods and cookie expiry.
8. User rights (access, correction, deletion, objection, portability, complaint to a supervisory authority) and how to exercise them.
9. Browser/device controls: how to block, delete, or manage cookies via browser settings, plus mobile device guidance.
10. Do Not Track, Global Privacy Control, and similar signals.
11. Security measures protecting cookie data.
12. Policy updates and how material changes are communicated.
13. Contact details for privacy questions or complaints.
</instructions>

<constraints>
- Use precise, plain English that a non-legal reader can follow; define technical terms in one short clause on first use.
- Keep the tone neutral, professional, and reassuring; avoid alarmist, marketing-flavoured, or defensive wording.
- Cover every category in the inventory above and add clearly marked placeholders such as [COOKIE_NAME] for any detail you are not given.
- Where jurisdiction-specific rules apply, state the requirement explicitly (for example, prior blocking of non-essential cookies in the EU/UK and consent requirements for US state opt-out laws).
- Do not invent specific legal citations, registration numbers, or regulatory decisions; describe requirements generically and recommend legal review where relevant.
- Avoid duplicating content between sections; each fact appears once.
</constraints>

<format>
Return the finished policy in Markdown:
# Cookies Policy — [WEBSITE_OR_APP_NAME]
**Effective date:** [EFFECTIVE_DATE] · **Version:** [VERSION_NUMBER] · **Applies to:** [SITE_URL]

## 1. Introduction
## 2. What Cookies Are
...and so on for each section above...
## 12. Cookie Inventory Table
## 13. Contact Us

Use numbered H2 sections, short paragraphs, and Markdown tables for the inventory. Output only the policy text, with no preamble, commentary, or code fences.
</format>

<tone>
Clear, authoritative, and compliance-focused. Write for a global readership while staying jurisdiction-accurate. Keep paragraphs concise and scannable, and prefer active constructions with concrete, verifiable statements.
</tone>

Now write the complete, publication-ready Cookies Policy for [WEBSITE_OR_APP_NAME] using every detail and placeholder provided above.