Repeated requests produce habitual acceptance rather than understanding

What it is

Consent fatigue occurs when recurrent, similar, weakly controllable requests teach people to clear prompts with a fixed action instead of interpreting and weighing each one. Unlike the burden of a single long policy, it is learned across time: the interface turns “accept” into a continue button. Click records remain complete, but their evidential value for understanding and intention deteriorates.

Why it happens

Repeated stimuli with similar outcomes become habituated and attract progressively less attention. When refusal regularly adds steps and prompts rarely contain meaningful novelty, rapid acceptance becomes an efficient cognitive strategy. Similar layouts across services also support motor memory, allowing selection before content is processed. Cosmetic variation or forced delay may interrupt the routine briefly, but habituation returns when frequency and control remain unchanged.

Studying it

Longitudinal studies can vary request frequency, importance, and content change over days or weeks, tracking response time, reading coverage, comprehension, choice, and confidence by exposure number. Sequence analysis distinguishes stable preference from content-insensitive repetition. Reversal probes can test whether participants still read, provided they create no real harm. A one-shot laboratory prompt cannot establish fatigue, while field studies must account for prior exposure across other applications.

Where it stops holding

Fast choice is not necessarily fatigue; a person may understand a durable purpose and hold a stable preference. Repeated requests can be warranted when data or context genuinely changes, although a higher-level rule may be more usable. Forced reading, randomized button placement, and continual visual novelty add friction and error without restoring voluntariness. An infrequent but coercive request is primarily a freedom-of-choice problem, not habituation.

Applying it

• Consolidate repeat requests covered by the same purpose and scope, prompting again only after a material condition changes.
• Let people define duration, context, or recipient rules and show their active state instead of interrupting every processing event.
• Distinguish genuinely high-risk requests from routine ones in content and action while keeping refusal accessible and avoiding alarmist copy.
• Run repeated-exposure tests comparing the first, fifth, and twentieth encounter, inserting a consequential content change; if action does not track consequences, reduce prompts or move the decision up a level and retest.

Related

• Same group: O1.05.1 Lengthy terms go unread in practice · O1.05.2 Blanket consent cannot express granular preferences · O1.05.3 Take-it-or-leave-it access is not a free choice · O1.05.4 Request timing determines whether attention is available · O1.05.5 Small mobile screens further constrain understandable consent · O1.05.6 A simplified summary can omit decisive exceptions
• Adjacent: O2.06 Consent-interface design and abuse · O3.05 Security-warning fatigue and disregard
• Search terms: consent fatigue · habituation · click-through behavior