Preselection treats no response as consent and conflicts with informed consent

What it is

Preselected consent enables an optional purpose, recipient, or tracking control before the person performs an affirmative action. Clicking “continue” may accept only the primary task, yet the interface interprets it as assent to every preselected item. The design therefore cannot distinguish active selection from failure to notice or change a state.

Why it happens

Defaults affect retention through inertia, implied recommendation, and change cost. During an interrupted flow, people may also treat untouched options as system configuration rather than their own declaration. If the backend records only final switch values, preselection then creates an apparently complete consent record that cannot establish item-level comprehension or choice.

Studying it

Holding options, copy, and layout constant, randomize unselected, preselected, and mandatory-response states. Measure retention, option recall, reason reconstruction, and delayed preference separately. The question is not whether defaults are effective, but whether the final state identifies affirmative intent. Selection rates alone cannot separate preference, inertia, and misunderstanding.

Where it stops holding

Ordinary security, accessibility, or core-service defaults are not all preselected consent; the concern is optional processing that requires authorization. Preserving an existing account preference also differs from preselecting a new request, provided migration does not expand its meaning. Jurisdictions may impose specific legal requirements, so products still need applicable-law review rather than treating this card as a universal legal conclusion.

Applying it

• Initialize every optional purpose as unselected and require an attributable affirmative action after clear explanation.
• Separate core-service processing from optional consent; do not mimic choice with a disabled switch.
• Record the version, objects, action, and time actually presented instead of inferring consent from a database value.
• Exercise new, migrated, and untouched-account branches; fail any case where optional processing becomes enabled without affirmative action.

Related

• Same group: O2.06.1 Path asymmetry · O2.06.3 Repeated prompting · O2.06.4 Visual weight · O2.06.5 Interruption timing · O2.06.6 Order and default focus · O2.06.7 Visual parity
• Adjacent: O1.01 Systemic nature of privacy · O1.04 Privacy-protective defaults · O1.05 Valid consent
• Search terms: preselected consent · consent by default · affirmative action