| name | privacy-policy-presentation |
| description | Use when designing privacy-policy and terms pages. Covers readability (sections, plain English summaries), the change log, when to require re-consent, and how to balance legal accuracy with usability.
|
Privacy Policy Presentation
A privacy policy is a contract. Users won't read it, but the few that do should find it readable.
Two-layer presentation
Plain-English summary at top of each section ('In plain English: ...'). Legal text below. Best of both.
Anchored sections
TOC at top with anchored links. Sections: What we collect / How we use it / Who we share with / Your rights / Contact.
Last-updated date
Prominent at top of page. Change log linked from there.
Re-consent
When policy changes materially, prompt user to acknowledge on next login. Don't bury changes.
Common mistakes
Pure legalese — unusable. No date — looks stale. No section anchors. Hidden behind sign-in. Cookie banner that doesn't match policy.
Where this fits in X3 Compass
Applied in the X3 Compass build via the relevant pages and components.