# POL-139 — The policy should be printable

> The privacy policy should be available in a form a consumer can print or save.

- **Rule ID:** POL-139
- **Layer:** Policy pages (`POLICY_PAGE`)
- **Checks:** `privacy policy page rendering`
- **Severity:** LOW — Best practice. Worth fixing, rarely fatal on its own.
- **When it bites:** Gates approval — get this wrong and registration is refused
- **How it is detected:** AI judgement over the crawled website or policy page
- **Fix type:** Fix the privacy policy or SMS terms
- **Required by:** CCPA
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/policy-page/pol-139/

## Why this rule exists

A policy that exists only as an expanding accordion, or that prints as a single blank page, cannot be kept by the person it governs — and California asks for a printable format for exactly that reason. It is a rendering accident rather than a decision, so nobody discovers it until somebody tries.

## How to fix it

Render the full text in the page rather than behind toggles, and add a print stylesheet or a downloadable copy. Done when printing the page produces the whole document.

## Notes

Only partly decidable from a text crawl: a fetch that returns the full body is good evidence the text is in the page, and it says nothing about how the page prints. The judge should report which of the two it could see.