App Legal Pages

Generate a complete legal mini-site for an app:

• - index.html (legal home)
• INLINECODE1 (Privacy Policy)
• INLINECODE2 (Terms of Service)
• INLINECODE3 (shared styles)

Workflow

1. 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:

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:

CODEBLOCK0

Email rule:

• - Prefer plus-address derivation from GitHub/base email + app tag.
• Example: chentuan7963@gmail.com + quillnest => chentuan7963+quillnest@gmail.com.
• 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:

CODEBLOCK1

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

4) Validate Draft Quality

Check before publishing:

• - privacy.html and terms.html both exist.
• App/company/email/effective date are consistent across pages.
• Privacy disclosures match only explicitly stated permissions and data behavior (no inferred tracking/region claims).
• User rights and contact/deletion request path are present.
• No unverifiable legal claims.
• Final pages contain no placeholder markers (forbidden: TODO/TEMP/FIXME).

If the app uses sensitive permissions or SDKs, verify these are explicitly disclosed in Privacy Policy.

5) Review Gate (Mandatory)

Before deployment, share generated files with the user and ask for explicit approval to deploy.
Do not deploy automatically without user confirmation.

6) Check Deployment Auth

Run auth readiness check:

CODEBLOCK2

Auth is valid when either:

• - CLOUDFLARE_API_TOKEN + CLOUDFLARE_ACCOUNT_ID are set, or
• INLINECODE12 succeeds.

If auth is missing, ask the user to authenticate:

CODEBLOCK3

7) Auto-Deploy to Cloudflare Pages

After explicit approval + auth ready:

CODEBLOCK4

Or use one-shot pipeline:

CODEBLOCK5

8) Returnables

Return:

• - Cloudflare Pages site URL
• Privacy Policy URL (<site>/privacy.html)
• Terms of Service URL (<site>/terms.html)
• Auth mode used (api-token or wrangler-login)

Guardrails

• - Do not claim legal compliance guarantees.
• Keep wording plain and readable.
• Keep deterministic page structure for easy future edits.
• Recommend human legal review before production app-store submission.