Legal text cannot replace in-interface explanation

What it is

An in-context privacy explanation states what is about to happen in short, concrete language where a person supplies data, enables a feature, or makes a choice, then links to full policy context. The privacy policy is a durable reference and complete record, not an excuse to move decision-critical information outside the task interface.

Why it happens

Questions during interaction are concrete: why this field now, who will see it, and what happens after refusal. Hiding answers in an external long document forces people to leave the task, locate a clause, and translate legal abstraction back into current behavior. A local explanation indexes information by the task object, while a deep link preserves detail and inspectability.

Studying it

In a real data-entry or feature task, compare a generic policy link, an inline summary plus generic link, and an inline summary plus precise passage link. Ask participants to predict data, purpose, recipient, consequence, and choice effect; record task switching, clause location, answer accuracy, and state retention after return. Low link use can mean either a sufficient summary or poor information scent, so interpret it with comprehension.

Where it stops holding

Limited interface space means inline explanation should not reproduce the policy; it selects propositions material to the current decision. Excessive layering can hide exceptions behind a gentle summary, so consequential limits belong in the first layer. Necessary processing still merits explanation, but an action control should not imply a choice that does not exist.

Applying it

• Beside fields, uploads, sharing, permissions, or personalization controls, state current data, concrete use, audience, and refusal effect.
• Keep decision-changing limitations in the first layer and expand the rest; do not place surprises behind “learn more.”
• Deep-link to the exact policy version and passage, preserving task state both when opening and returning.
• Maintain a data-flow proposition inventory for each explanation and test predictions item by item; repair either summary or policy when it misses actual behavior.

Related

• Same group: O2.07.1 Policies need topic-based navigation · O2.07.2 Changes need summaries and comparisons
• Adjacent: O1.05.6 Layered consent information · O2.01 Information design for permission prompts · O2.02 Readable explanations of data use
• Search terms: in-context privacy explanation · layered privacy notice · privacy deep link