← All playbooks · Raw API

legal-policy-pages

# Legal & policy pages — point.me

Playbook for **privacy**, **terms**, cookies, and accessibility pages on the marketing site.

## URL patterns

| Public path | Typical CMS slug |
|-------------|------------------|
| `/privacy-policy/` | `privacy-policy` |
| `/terms-and-conditions/` | `terms-and-conditions` |
| `/amex-terms-and-conditions/` | `amex-terms-and-conditions` |
| `/cookie-list/` | `cookie-list` |
| `/accessibility/` | `accessibility` |

Linked from the footer. If slugs change, coordinate redirects (`redirects.json`).

## 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 — legal must re-read the rendered page |
| Do **not** restructure numbered sections without legal approval | |
| Preserve effective dates, entity names, and contact emails unless legal supplies replacements |
| Do not add marketing search heroes or card-affiliate modules into policy body |

## Typical content stack

| Region | Type | Notes |
|--------|------|-------|
| `content` | **Rich text** and/or **Content** | Long policy body — match the live page |

There is no separate **Legal rich text** type on this site.

## Workflow

1. Open the page (`cms-edit open /privacy-policy/`)
2. Edit body via `task-edit-rich-text` or `rtf`
3. `preview urls` on staging → `diff` → `save` → legal approval → `task-publish-handoff`

## Out of scope

- Product-app legal surfaces on AWS
- Insights articles that quote policy