Nagging · European Union
Repeated prompting
The label “Repeated prompting” describes this recurring design mechanism: a business-favoured request repeatedly interrupts the user after decline, dismissal or non-response without a durable way to stop it. It is a design and research taxonomy, not a standalone legal conclusion. Depending on the complete journey and likely effect, current EU consumer or sector rules may require separate assessment. No published Digital Fairness Act proposal currently creates a pattern-specific prohibition or duty under this label.
- Family
- Nagging
- Also known as
- Journey stages
Definition
What is this pattern?
A business-favoured request repeatedly interrupts the user after decline, dismissal or non-response without a durable way to stop it. The label describes a recurring design mechanism; whether a particular implementation is harmful or unlawful depends on the complete journey, audience, evidence and rules within scope.
How it works
A business-favoured request repeatedly interrupts the user after decline, dismissal or non-response without a durable way to stop it. Refusal is stored only briefly while acceptance would be durable, allowing repeated interruption costs to wear down a choice already made.
Warning signs
- The prompt purpose is materially the same across occurrences.
- The user previously declined, dismissed or ignored it.
- Recurrence exceeds a configured reasonable observation rule and creates plausible pressure or time cost.
Potential harms
- Repeated interruption can wear down a refusal and prevent ordinary use of the service.
- A traveller may accept simply to stop repeated interruptions or may believe the earlier refusal was ineffective.
Learn by comparison
What does this look like?
These fictional examples make the design mechanism easier to recognise. They do not depict a real company and do not establish that an individual interface is unlawful.
Illustrative example 1 · Mobile app onboarding
A fictional app shows the same full-screen notification request after the user declines, then repeats it on each of the next four screens.
Potential consumer harm: Repeated interruption can wear down a refusal and prevent ordinary use of the service.
Illustrative example 2 · Travel checkout
A fictional booking journey restores a previously declined insurance offer at passenger details, payment and final confirmation.
Potential consumer harm: A traveller may accept simply to stop repeated interruptions or may believe the earlier refusal was ineffective.
Notification request returns on every screen
A fictional app shows the same full-screen notification request after the user declines, then repeats it on each of the next four screens.
Turn on notifications. The request returns immediately after every decline.. Not now. Continue without notifications
Notifications remain off. The app records the refusal and explains where the setting can be changed later.. Continue without notifications. Not now. What happens next, expanded: Activating “Continue without notifications” produces the outcome stated on the control.
Why the first version can mislead: The user’s earlier refusal loses effect while the request keeps interrupting the signup journey. The practical influence comes from recurrence, not from one isolated prompt: “The request returns immediately after every decline.” Repeated interruption can wear down a refusal and prevent ordinary use of the service.
What a fairer design does: Respect the decision for a meaningful period and keep any later change available in settings.
Show annotated differences (2)
- Continue without notificationsIn “Notification request returns on every screen”, this element shows how repeated prompting can shape the decision.
- What happens next, expanded: Activating “Continue without notifications” produces the outcome stated on the control.In “Notification request returns on every screen”, this element keeps the clearer alternative visible at the same decision point.
Review questions (3)
- Which event causes “Not now” to return after refusal, and how long does the product persist that refusal?
- Can the dialog be dismissed, what action does each control trigger, and what later state confirms or contradicts “The prompt purpose is materially the same across occurrences”?
- After an explicit refusal, when may the prompt legitimately return, and how would that changed context remain distinct from “Required safety or legal notice”?
Declined add-on repeatedly reappears
A fictional booking journey restores a previously declined insurance offer at passenger details, payment and final confirmation.
Add insurance before continuing. The same rejected extra blocks three later checkout steps.. Amount affected: €24: Add €24 insurance. Add €24 insurance. Continue to payment
Insurance declined. The decision persists and checkout continues without another blocking prompt.. Continue to payment. Add €24 insurance. Payable total and selected items, expanded: The summary shows the line items and total before “Continue to payment” is activated.
Why the first version can mislead: The user’s earlier refusal loses effect while the request keeps interrupting the checkout journey. The practical influence comes from recurrence, not from one isolated prompt: “The same rejected extra blocks three later checkout steps.” A traveller may accept simply to stop repeated interruptions or may believe the earlier refusal was ineffective.
What a fairer design does: Persist the refusal throughout the transaction and provide one optional, non-blocking way to reconsider.
Show annotated differences (2)
- Continue to paymentIn “Declined add-on repeatedly reappears”, this element shows how repeated prompting can shape the decision.
- Payable total and selected items, expanded: The summary shows the line items and total before “Continue to payment” is activated.In “Declined add-on repeatedly reappears”, this element keeps the clearer alternative visible at the same decision point.
Review questions (3)
- Which event causes “Add €24 insurance” to return after refusal, and how long does the product persist that refusal?
- Compare the basket before and after the action, including total and line items; does the mutation satisfy “The user previously declined, dismissed or ignored it”?
- After an explicit refusal, when may the prompt legitimately return, and how would that changed context remain distinct from “materially changed request triggered by a new user action”?
What is a fairer alternative?
Respect decline and dismissal, provide a durable preference, and limit reminders to justified, transparent intervals.
Legal and information status
Legal position at a glance
A business-favoured request repeatedly interrupts the user after decline, dismissal or non-response without a durable way to stop it. Refusal is stored only briefly while acceptance would be durable, allowing repeated interruption costs to wear down a choice already made. Risk increases where the mechanism changes a material consumer choice, hides a consequence or makes a genuine alternative harder to use. The taxonomy label remains a review prompt and does not establish an infringement.
Dark-pattern research taxonomy
Editorial analysis
The cited research sources support identification and comparison of this recurring interface mechanism. They do not determine that a particular interface is unlawful.
UCPD Articles 5 to 9, where applicable
Possible risk indicator
Depending on the trader, audience, overall presentation, material information and likely transactional effect, the facts may require a separate assessment under the applicable UCPD provisions.
Evidence layers and open questions
Applicable law, enforcement records, policy preparation, stakeholder input, editorial analysis and unknown future details remain visibly distinct.
Current lawCurrent law
The UX label “Repeated prompting” is not a standalone EU offence. Depending on the trader, audience, complete presentation, omitted information and likely transactional effect, the observed facts may require a separate assessment under the applicable UCPD provisions or another instrument within scope.
Under considerationUnder consideration
The Commission is preparing a Digital Fairness Act initiative, but the call for evidence does not select a final rule for repeated prompting or establish that this taxonomy term will appear in a proposal.
Editorial analysisEditorial analysis
The pattern definition, variants and examples on this page use the cited research taxonomy sources to support recognition and comparison. That analytical classification is not a legal conclusion about an individual interface.
UnknownUnknown
No published DFA proposal currently establishes a definition, covered actor, legal threshold, duty, remedy, transition rule or application date for repeated prompting. Those details remain unknown pending primary legislative text.
Context matters
Context and boundary cases
- The prompt purpose is materially the same across occurrences.
- The user previously declined, dismissed or ignored it.
- Recurrence exceeds a configured reasonable observation rule and creates plausible pressure or time cost.
- Exclude or qualify the label where required safety or legal notice.
- Exclude or qualify the label where materially changed request triggered by a new user action.
- Exclude or qualify the label where one reminder after a long and relevant interval.
When a similar design can serve a legitimate purpose
- A similar design should not be classified this way where required safety or legal notice.
- A similar design should not be classified this way where materially changed request triggered by a new user action.
- A similar design should not be classified this way where one reminder after a long and relevant interval.
Operational review
What teams should review
- Teams
- Which event causes “Not now” to return after refusal, and how long does the product persist that refusal?
- Can the dialog be dismissed, what action does each control trigger, and what later state confirms or contradicts “The prompt purpose is materially the same across occurrences”?
- After an explicit refusal, when may the prompt legitimately return, and how would that changed context remain distinct from “Required safety or legal notice”?
- Which event causes “Add €24 insurance” to return after refusal, and how long does the product persist that refusal?
- Compare the basket before and after the action, including total and line items; does the mutation satisfy “The user previously declined, dismissed or ignored it”?
- After an explicit refusal, when may the prompt legitimately return, and how would that changed context remain distinct from “materially changed request triggered by a new user action”?
- Which complete journey evidence supports or contradicts the repeated prompting classification?
Evidence to retain
- Versioned captures of the Signup and Checkout states before, during and after the relevant decision
- Configuration, content and event records supporting the observed repeated prompting mechanism
- Responsive, keyboard and assistive-technology review of every material option and consequence
- Price-component, offer-version and calculation records linked to the captured screen
Legal map and implementation tools
Evidence base
Sources
- Dark commercial patternsOrganisation for Economic Co-operation and Development · Secondary · checked 2026-09-14 · OECD Digital Economy Papers No. 336
- Unfair Commercial Practices DirectiveEuropean Parliament and Council of the European Union · Primary · checked 2026-08-09 · Directive 2005/29/EC; CELEX 02005L0029-20220528
- Digital Fairness Act: call for evidence for an impact assessmentEuropean Commission · Primary · checked 2026-08-09 · Initiative 14622; Ares(2025)6275573
- Commission work programme 2026: Europe's Independence MomentEuropean Commission · Primary · checked 2026-09-14 · COM(2025) 870 final; CELEX 52025DC0870; Annex I item 30