O2.06.3Consent naggingdesignresearch

Repeated prompting until acceptance is a dark pattern

Aliases: repeated consent prompting · consent harassment · privacy nagging

What it is

Consent nagging repeatedly resurfaces an optional request after a person has refused or deferred it, without a materially new reason, until they accept. Its asymmetry unfolds over time rather than within one button set: refusal must be expressed repeatedly, while one acceptance is remembered indefinitely.

Why it happens

Repeated interruption turns refusal into a continuing tax. The person must keep spending attention while the system waits for fatigue, haste, or a mistaken tap. Because acceptance ends the disturbance, the eventual action communicates both “remove this prompt” and “permit this processing,” so it is not clean preference evidence. A single-session usability test misses this cumulative pressure entirely.

Studying it

Use a longitudinal study across sessions. After refusal, dismissal, or “later,” record recurrence intervals, triggers, primary-task disruption, and choice changes. Compare remembered refusal, fixed-frequency prompting, and re-prompting only after material change. Delayed interviews should distinguish preference change, accidental acceptance, and capitulation intended to stop interruptions.

Where it stops holding

When purpose, data scope, recipient, or risk materially changes, the old choice may not cover the new situation; asking again is not necessarily nagging. An explicit “ask next time” also differs from refusal, although “later” needs a predictable cooling period. Security warnings and service-essential confirmations should remain separate from optional marketing or tracking requests.

Applying it

  • Store refusal as a durable preference across account, device, and anonymous-session scope where feasible.
  • Give “later” a stated cooling period and a noninterruptive voluntary entry point instead of resurfacing during every primary task.
  • Re-request only after user-initiated settings access or a material change, naming what changed.
  • Run cross-session tests that continue ordinary tasks after refusal; treat any reasonless recurrence as a regression failure.

Related

  • Same group: O2.06.1 Path asymmetry · O2.06.2 Preselected consent · O2.06.4 Visual weight · O2.06.5 Interruption timing · O2.06.6 Order and default focus · O2.06.7 Visual parity
  • Adjacent: O1.05 Valid consent · O1.10 Consent withdrawal and granularity
  • Search terms: consent nagging · repeated consent prompting · interruption fatigue

Cards in the same group

Quick Actions

Share

Share this page

ios_share

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