legal-document-generator git:20260407.3f5f769A

Immutable. This exact content is served forever at /api/v1/blob/3ae53c982119cd25.

---
name: legal-document-generator
description: "Generate draft legal documents from company context. Supports 8 document types across US, EU/GDPR, and UK jurisdictions."
---

A legal document generator that produces draft legal documents from company context.

## Supported Document Types

Terms & Conditions, Privacy Policy, Cookie Policy, GDPR Policy, Acceptable Use Policy, Data Processing Agreement, Data Protection Disclosure, Disclaimer / Limitation of Liability.

## Instructions

Before generating any documents, collect entity name, contact email, jurisdiction, and architecture type (SaaS vs local-only vs open-source) upfront -- the generator creates each document independently, so missing this context produces cross-document inconsistencies that require a full audit cycle to fix.

For local-only or open-source tools with no data processing on behalf of third parties, offer "Data Protection Disclosure" instead of "Data Processing Agreement" -- a binding DPA implies a processor relationship that does not exist.

### 1. Disclaimer Placement

Every generated document MUST include this blockquote at the very top and very bottom:

> **DRAFT -- This document was generated by AI and requires professional legal review before use. It does not constitute legal advice.**

NEVER omit the disclaimer. NEVER place it only at the top or only at the bottom. Both locations are mandatory.

### 2. Output Format

Output as markdown with YAML frontmatter:

```yaml
---
title: "Privacy Policy"
type: privacy-policy
jurisdiction: EU
generated-date: YYYY-MM-DD
---
```

Use kebab-case for `type` values: `terms-and-conditions`, `privacy-policy`, `cookie-policy`, `gdpr-policy`, `acceptable-use-policy`, `data-processing-agreement`, `data-protection-disclosure`, `disclaimer`.

### 3. Cross-Reference Hints

When a document logically references another document type, add a note at the end:

> **Related documents:** This [document type] references [other type]. Consider generating a companion [other type] document to ensure consistency.