← All playbooks · Raw API

legal-policy-pages

# Legal & policy pages — HopSkipDrive

Playbook for **privacy, terms, zero-tolerance, and related policy** pages. These are **not** marketing funnels — treat body copy as counsel-owned.

## URL patterns

| Public path | Role | Notes (live CMS) |
|-------------|------|------------------|
| `/privacy` | Privacy Policy | Many **Rich text (without padding)** sections (A–L); template **no newsletter** |
| `/terms-of-use` | Terms of Use | Single **Rich text** body; template **b2b newsletter** |
| `/zero-tolerance-policy` | Zero Tolerance Policy | Single **Rich text** body; template **b2b newsletter** |
| `/guidelines` | Community Guidelines | Policy-adjacent marketing: **Text and Image** hero + **Square Cards** — still counsel-sensitive |

Other policy-named pages (if added) follow this playbook when the content is legal/compliance language rather than product marketing.

## Editing rules

| Rule | Why |
|------|-----|
| **Legal / compliance review required** for substantive wording changes | `save` only creates drafts; humans publish after counsel signs off |
| Do **not invent** statutes, rights, retention periods, contact addresses, or jurisdiction language | Only apply copy supplied by legal or existing CMS text |
| Prefer **`task-bulk-find-replace`** for global renames (company name, product name) — then legal re-reads the diff | Safer than free-form rewrites of long RTF |
| Do **not** restructure section order (especially Privacy A–L) without legal approval | Heading order may match notice expectations |
| Preserve effective dates, contact emails, and defined terms unless legal supplies replacements | Compliance continuity |
| No marketing CTAs, forms, or product upsells in pure policy bodies without approval | Privacy/terms should stay document-like |
| Prefer editing **existing** RTF components in place over adding marketing collections | Keeps chrome minimal |

## Typical content stack

### Document-style (privacy, terms, zero-tolerance)

| Section | Type | Notes |
|---------|------|-------|
| Policy body | **Rich text** and/or **Rich text (without padding)** | One long RTF **or** one component per major section (privacy) |
| Hero / chrome | Usually **none** in `topContent` | No product hero funnel |
| Collections | Rare | Do not add FAQs/testimonials unless already on the page |

**Templates observed:**

| Template | Pages |
|----------|--------|
| **General page template - no newsletter** | `/privacy` |
| **General page template - b2b newsletter** | `/terms-of-use`, `/zero-tolerance-policy` |

Do not switch templates casually — footer/newsletter chrome changes sitewide appearance for that page.

### Policy-adjacent community guidelines — `/guidelines`

| Section | Type |
|---------|------|
| Hero | **Text and Image** |
| Principles | **Square Cards** (e.g. Be Safe / Be Considerate / Be Respectful) |

Still treat substantive rule language as legal-sensitive; do not invent community rules.

## Reference pages

| Path | Use when |
|------|----------|
| `/privacy` | Privacy notice updates; multi-section RTF pattern |
| `/terms-of-use` | Single-document terms revisions |
| `/zero-tolerance-policy` | Safety/zero-tolerance legal text |
| `/guidelines` | Community guidelines card layout |

## Workflow

1. Read `cms-edit://customer/pages` and this playbook  
2. Open by slug (`--page-slug /privacy`, etc.)  
3. Confirm you have **approved legal copy** (doc or counsel email) — do not draft from memory  
4. Edit RTF via `rtf` / scalar fields; keep `cmsLabel`s descriptive  
5. `diff` carefully — large RTF diffs are expected  
6. `preview urls` on staging  
7. `save` → **stop** — hand off for legal review before Contentful publish (`task-publish-handoff` only after approval)

## Out of scope

- Product marketing (Safety, RouteWise, Supplemental) → `offering-pages`  
- Program verticals → `program-vertical-pages`  
- Quote / thank-you / form utilities → `utility-landing-pages`  
- Inventing CCPA/GDPR/HIPAA language  
- Changing shared footer legal links via this playbook alone → `task-navigation` if needed  

## Related

- Hub: `cms-edit://customer/pages`  
- Bulk terminology: `cms-edit://customer/task-bulk-find-replace`  
- Publish: `cms-edit://customer/task-publish-handoff`