# Legal & policy pages — OM1

Playbook for **privacy**, **terms**, and other compliance pages.

## URL patterns

| Public path | CMS slug (typical) | Document |
|-------------|-------------------|----------|
| `/privacy/` | `privacy` | Site privacy policy |
| `/terms-and-conditions/` | `terms-and-conditions` | Terms of use |

These pages are linked from the **footer legal row**. If slugs change, coordinate redirects — see `redirects.json` in the repo.

## Editing rules

| Rule | Why |
|------|-----|
| **Legal/compliance sign-off** before publish on substantive changes | cms-edit saves drafts only |
| Prefer **`task-bulk-find-replace`** for global terminology (company name, product name) — legal must re-read the full rendered page after |
| Do **not** restructure numbered sections without legal approval | Section order may match regulatory expectations |
| Preserve effective dates, entity names, and contact emails unless legal supplies replacements |
| Do not add marketing CTAs into policy body without approval |

## Typical content stack

### Privacy policy (`/privacy/`)

| Region | Type | Notes |
|--------|------|-------|
| `content` | **Legal rich text** | Full policy — long RTF, numbered sections |

### Terms and conditions (`/terms-and-conditions/`)

| Region | Type | Notes |
|--------|------|-------|
| `content` | **Legal rich text** | All sections in one or more RTF blocks |

## Legal rich text styling

Policy body uses **Legal rich text** — see `docs/cms-guidelines/components/legal-rich-text.md` and `COMPONENT_GUIDELINES_FOR_LLM.md`.

Edit RTF:

```bash
cms-edit open /privacy
cms-edit snapshot
printf 'Updated paragraph.\n\n' | cms-edit rtf @cN body --markdown -
```

Use `task-edit-rich-text` for multi-paragraph updates; keep heading hierarchy stable.

## Reference pages

| Path | Clone when |
|------|------------|
| `/privacy/` | Privacy copy refresh |
| `/terms-and-conditions/` | Terms revision |

Fetch markdown for legal review: `https://www.om1.com/privacy.md`

## Workflow

1. Obtain approved copy from legal (tracked doc or redlines)
2. Read `cms-edit://customer/pages` for save/preview rules
3. `cms-edit open --page-slug privacy` (or `terms-and-conditions`)
4. Edit **Legal rich text** `body` only — page title in page entry `title` field
5. For sitewide phrase replacement: `task-bulk-find-replace` with narrow scope — preview full page after
6. Set `description` and `featuredImage` when SEO/compliance requests it
7. `preview urls` on staging → `diff` → `save` → legal review → `task-publish-handoff`

## Out of scope

- **Cookie consent / OneTrust** banner configuration — platform/marketing ops
- New legal page types without engineering (new route + template work first)
- **Resource articles** — use article playbooks

## Publish handoff

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