← All playbooks · Raw API

legal-policy-pages

# Legal & policy pages — Headwater Science

Playbook for **privacy** and **cookie** policy pages (root-level slugs).

## URL patterns

| Public path | CMS slug | Document |
|-------------|----------|----------|
| `/privacy-policy/` | `privacy-policy` | Site privacy policy |
| `/cookie-policy/` | `cookie-policy` | Cookie policy |

Linked from footer legal row (`navigation.entries` last index). Coordinate redirects if slugs change.

**No Engage™ terms page** on Headwater (Pedestal-only).

## Editing rules

| Rule | Why |
|------|-----|
| Legal/compliance sign-off before substantive publish | cms-edit saves drafts only |
| `task-bulk-find-replace` only with full-page legal re-read | Avoid accidental jurisdiction/contact errors |
| Do not restructure numbered sections without legal approval | |
| Preserve effective dates and entity names unless legal supplies replacements | |

## Typical content stack

### Privacy policy

| Region | Type |
|--------|------|
| `topContent` or `content` | **Split hero** — title |
| `content` | **Legal rich text** — full policy (`rtf-legal` styling) |

### Cookie policy

| Region | Type |
|--------|------|
| `content` | **Legal rich text** — cookie notice body |

Headwater does not register a **Cookie Policy List** external (unlike Pedestal OneTrust embed) — policy text is CMS-authored.

## Workflow

1. Obtain legal-approved copy
2. `cms-edit open /privacy-policy` or `/cookie-policy`
3. Edit **Legal rich text** `body` via `task-edit-rich-text`
4. `preview urls` on staging
5. `diff` → `save` → legal review → `task-publish-handoff`

## Out of scope

- News/publications
- OneTrust banner configuration — platform ops

## Publish handoff

`save` creates drafts only — publish in Contentful UI after legal approval.