Policies need topic-based navigation
Aliases: privacy-policy topic navigation · policy findability · policy information architecture
What it is
A topic-addressable privacy policy lets readers jump from a concrete question—location, retention, advertising, deletion, or a child's account—to the relevant passage without reading the document linearly. Stable headings, a contents structure, search synonyms, and linkable anchors make the policy usable in a task, not merely available.
Why it happens
Policies are often organized by legal doctrine, organizational department, or processing stage, while people begin with a data object or intended action. When those vocabularies diverge, page search misses synonyms and vague headings offer poor information scent. Topic navigation maps user language to legal content while retaining context and complete clauses.
Studying it
Give lookup tasks that do not reveal headings, such as “how long is a backup retained after I delete a photo?” Record first topic, route, query, time, backtracking, and answer accuracy. Tree testing can isolate architecture before testing scanning and anchors in the full page. Reaching a passage is insufficient; verify that it actually answers the question.
Where it stops holding
Over-fragmentation can scatter one data flow and invite readers to miss limiting context. A contents list does not replace full text, and search should not require exact legal vocabulary. Regional, role, or product variants may personalize content, but the active scope must remain visible so dynamic presentation does not conceal unfavorable material.
Applying it
- Build top-level topics from user questions and data objects, using legal duties within sections rather than as the sole navigation vocabulary.
- Give each topic a descriptive heading, stable anchor, in-page contents entry, and return route, preserving deep links.
- Maintain synonyms from search logs and research so everyday terms such as “close account” or “wipe” reach the relevant clause.
- Test unprompted lookup with common and long-tail questions, accepting both rapid arrival and complete answers rather than contents clicks.
Related
- Same group: O2.07.2 Changes need summaries and comparisons · O2.07.3 Legal text cannot replace in-interface explanation
- Adjacent: O2.02 Readable explanations of data use · O2.08 Readability of data-use explanations
- Search terms:
topic-addressable privacy policy·privacy policy findability·policy tree testing