O2.08.1Legalese barrier in privacy noticesdesignresearch

A disclosure buried in legal terminology is functionally undisclosed even when public

Aliases: privacy-notice legalese · formal disclosure · legalistic privacy notice

What it is

A legalese barrier in a privacy notice exists when public content consists mainly of undefined legal terms, nested exceptions, passive constructions, and vague referents, preventing its intended readers from predicting concrete data behavior. Openability is only a delivery condition. If readers cannot identify what is collected, for which function, by whom, and under what limits, the interaction has not accomplished notice.

Why it happens

Specialized vocabulary turns “trace the data flow” into “first learn a legal classification.” Negation, exceptions, and cross-references in long sentences burden working memory, while undefined “we,” “partners,” and “may” conceal actors and conditions. Readers can recognize each word yet fail to assemble an actionable mental model, replacing comprehension with skimming, guessing, or abandonment.

Studying it

Extract propositions for data, source, function, recipient, condition, and retention, then ask target readers to answer scenarios without the text. Mapping errors back to terms, syntax, and referents separates vocabulary barriers from inherent conceptual complexity. Reading time and self-reported clarity do not demonstrate notice; test prediction and exception judgment.

Where it stops holding

Legal precision should be preserved through definitions, parallel plain language, and traceable layers rather than deleted. Some terms distinguish rights or roles and become misleading when replaced by broad everyday words. Professional documentation may be more technical, but a consumer product's first layer should not assume privacy-law training.

Applying it

  • Define each necessary specialized term inline with a plain-language product example instead of outsourcing all meaning to a glossary.
  • Write actor, action, object, condition, and exception as traceable short sentences, reducing passive voice and unbound pronouns.
  • Retain formal language in a detail layer and map each plain-language proposition back to its clause.
  • Validate proposition by proposition with target-user scenarios; revise the specific sentence when an actor, condition, or exception is systematically misunderstood.

Related

  • Same group: O2.08.2 Measure readability through user comprehension · O2.08.3 Icons and examples build mental models · O2.08.4 Simplification can omit critical limits
  • Adjacent: O2.02.1 Explanations need function-level specificity · O2.07 Scannable privacy policies
  • Search terms: legalese barrier · plain-language privacy notice · formal disclosure

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/O2.08.1