App Legal Pages

Generate a complete legal mini-site for an app:

• index.html (legal home)
• privacy.html (Privacy Policy)
• terms.html (Terms of Service)
• styles.css (shared styles)

Workflow

1. Collect required legal/product inputs.
2. Generate draft legal pages from feature documentation.
3. Run strict consistency checker.
4. Present generated pages for user review/approval.
5. Check Cloudflare deployment auth readiness.
6. Ask user to complete auth if missing.
7. Auto-deploy to Cloudflare Pages after explicit confirmation.
8. Return final public URLs.

1) Collect Inputs

Collect or confirm:

• App name
• Company/entity name (or individual publisher name)
• Contact email
• Governing law jurisdiction (country/region, optional; only if explicitly provided)
• Effective date
• App feature document (markdown/text)
• Data behavior details:
  • Analytics events
  • Crash/error logs
  • Identifiers (device/user IDs)
  • Third-party SDKs/services
  • Permissions used (camera/location/photos/mic/contacts/tracking/notifications)

If facts are unknown, pause and ask for missing inputs before generation. Do not output placeholder markers (no TODO/TEMP strings in final pages). Never assume jurisdiction, region, analytics/tracking, sharing, or permission usage unless explicitly stated in the input document or user prompt. Generate policy clauses from explicit product claims first (e.g., offline-only, no cloud, no tracking, no analytics), and avoid introducing contradictory generic legal boilerplate.

2) Generate Draft Site

Run:

python3 scripts/generate_legal_site.py \
  --input /path/to/app-feature.md \
  --out ./out/legal-site \
  --app-name "Your App" \
  --company "Your Company" \
  --base-email "[email protected]" \
  --email-tag "quillnest" \
  --effective-date "2026-03-03" \
  --jurisdiction "California, United States"

Email rule:

• Prefer plus-address derivation from GitHub/base email + app tag.
• Example: [email protected] + quillnest => [email protected].
• Use --email only when you explicitly want a fixed address.

Language rule:

• Generate English-only legal pages by default.
• Exclude non-English feature bullets from Feature Context to keep language consistent.

The script auto-detects likely data categories/permissions from the feature text. Manually review and adjust output if app behavior is more specific than heuristic detection.

3) Run Strict Consistency Checker

Run before publishing:

python3 scripts/check_consistency.py \
  --feature /path/to/app-feature.md \
  --privacy ./out/legal-site/privacy.html \
  --terms ./out/legal-site/terms.html

The checker fails on:

• Placeholder tokens (TODO/TEMP/FIXME)
• Contradictions against explicit product claims (offline/no-cloud/no-tracking/no-analytics)
• EXIF mention in feature doc without corresponding privacy disclosure
• Governing-law section in Terms when jurisdiction is not explicitly provided