Forced action · European Union
Forced or bundled consent
The label “Forced or bundled consent” describes this recurring design mechanism: access is conditioned on accepting optional or separable data uses, communications or permissions as one bundled choice. 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
- Forced action
- Also known as
- Journey stages
Definition
What is this pattern?
Access is conditioned on accepting optional or separable data uses, communications or permissions as one bundled choice. 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
Access is conditioned on accepting optional or separable data uses, communications or permissions as one bundled choice. Several distinct processing purposes are collapsed into one take-it-or-leave-it permission, so a person cannot accept necessary operation without optional uses.
Warning signs
- Multiple consequences or purposes are attached to one acceptance control.
- At least one consequence appears separable from the core function.
- Refusal blocks or materially burdens access.
Potential harms
- A visitor cannot distinguish necessary operation from optional data uses or express separate choices.
- Refusing unrelated marketing appears to prevent completion of the requested transaction.
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 · News site entry
A fictional news service presents one accept control for essential storage, audience analytics, advertising profiles and partner sharing, while access is blocked.
Potential consumer harm: A visitor cannot distinguish necessary operation from optional data uses or express separate choices.
Illustrative example 2 · Ticket checkout
A fictional ticket seller requires one checkbox that accepts the purchase terms, promotional messages and sharing with event partners.
Potential consumer harm: Refusing unrelated marketing appears to prevent completion of the requested transaction.
Optional analytics bundled with access
A fictional news service presents one accept control for essential storage, audience analytics, advertising profiles and partner sharing, while access is blocked.
Accept and enter. Essential storage, analytics, advertising and partner sharing are one package.. Selected: Accept everything. Not selected: Use necessary storage only
Choose data uses. Necessary storage is explained and optional purposes have separate controls.. Not selected: Use necessary storage only. Not selected: Accept everything. Choice consequences, expanded: The consequence of selecting “Use necessary storage only” is displayed beside the option.
Why the first version can mislead: The additional dependency controls access to the signup goal. The panel states: “Essential storage, analytics, advertising and partner sharing are one package.” Reviewers need to establish whether “Accept everything” is necessary for the selected task or pressures the user into a separable action. A visitor cannot distinguish necessary operation from optional data uses or express separate choices.
What a fairer design does: Separate purposes, explain consequences and keep optional permissions off unless the visitor chooses them.
Show annotated differences (2)
- Not selected: Use necessary storage onlyIn “Optional analytics bundled with access”, this element shows how forced or bundled consent can shape the decision.
- Choice consequences, expanded: The consequence of selecting “Use necessary storage only” is displayed beside the option.In “Optional analytics bundled with access”, this element keeps the clearer alternative visible at the same decision point.
Review questions (3)
- What functional need makes “Accept everything” necessary for the news site entry goal, and can that need be met with less disclosure or commitment?
- Capture every peer option, its default state and visual prominence; do those states support “Multiple consequences or purposes are attached to one acceptance control”?
- Could the stated purpose make this dependency genuinely necessary under the boundary “Single necessary processing operation clearly explained”, and what product evidence would demonstrate that necessity?
Purchase terms combined with promotions
A fictional ticket seller requires one checkbox that accepts the purchase terms, promotional messages and sharing with event partners.
Agree to continue. Purchase, newsletters and partner offers use one required checkbox.. Selected: Accept all terms and offers. Continue with selected choices
Confirm purchase terms. The contract control is required; marketing and partner choices are separate and optional.. Complete purchase. Only task-relevant details requested. Purpose and refusal effect, expanded: The form explains why “Complete purchase” is requested and what happens if it is not used.
Why the first version can mislead: The additional dependency controls access to the checkout goal. The panel states: “Purchase, newsletters and partner offers use one required checkbox.” Reviewers need to establish whether “Accept all terms and offers” is necessary for the selected task or pressures the user into a separable action. Refusing unrelated marketing appears to prevent completion of the requested transaction.
What a fairer design does: Keep contract acceptance distinct from optional marketing and partner permissions with unticked controls.
Show annotated differences (2)
- Continue with selected choicesIn “Purchase terms combined with promotions”, this element shows how forced or bundled consent can shape the decision.
- Purpose and refusal effect, expanded: The form explains why “Complete purchase” is requested and what happens if it is not used.In “Purchase terms combined with promotions”, this element keeps the clearer alternative visible at the same decision point.
Review questions (3)
- What functional need makes “Accept all terms and offers” necessary for the ticket checkout goal, and can that need be met with less disclosure or commitment?
- Which fields or permissions are required, what happens on refusal, and does the resulting state support this criterion: “At least one consequence appears separable from the core function”?
- Could the stated purpose make this dependency genuinely necessary under the boundary “bundle with granular equivalent controls and no penalty for refusal”, and what product evidence would demonstrate that necessity?
What is a fairer alternative?
Separate distinct purposes, make optional uses genuinely optional, and provide an equally accessible refusal path.
Legal and information status
Legal position at a glance
Access is conditioned on accepting optional or separable data uses, communications or permissions as one bundled choice. Several distinct processing purposes are collapsed into one take-it-or-leave-it permission, so a person cannot accept necessary operation without optional uses. 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 “Forced or bundled consent” 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 forced or bundled consent 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 forced or bundled consent. Those details remain unknown pending primary legislative text.
Context matters
Context and boundary cases
- Multiple consequences or purposes are attached to one acceptance control.
- At least one consequence appears separable from the core function.
- Refusal blocks or materially burdens access.
- Exclude or qualify the label where single necessary processing operation clearly explained.
- Exclude or qualify the label where bundle with granular equivalent controls and no penalty for refusal.
When a similar design can serve a legitimate purpose
- A similar design should not be classified this way where single necessary processing operation clearly explained.
- A similar design should not be classified this way where bundle with granular equivalent controls and no penalty for refusal.
Operational review
What teams should review
- Teams
- What functional need makes “Accept everything” necessary for the news site entry goal, and can that need be met with less disclosure or commitment?
- Capture every peer option, its default state and visual prominence; do those states support “Multiple consequences or purposes are attached to one acceptance control”?
- Could the stated purpose make this dependency genuinely necessary under the boundary “Single necessary processing operation clearly explained”, and what product evidence would demonstrate that necessity?
- What functional need makes “Accept all terms and offers” necessary for the ticket checkout goal, and can that need be met with less disclosure or commitment?
- Which fields or permissions are required, what happens on refusal, and does the resulting state support this criterion: “At least one consequence appears separable from the core function”?
- Could the stated purpose make this dependency genuinely necessary under the boundary “bundle with granular equivalent controls and no penalty for refusal”, and what product evidence would demonstrate that necessity?
- Which complete journey evidence supports or contradicts the forced or bundled consent 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 forced or bundled consent mechanism
- Responsive, keyboard and assistive-technology review of every material option and consequence
- Control defaults, validation rules and consent or selection state changes
Legal map and implementation tools
Evidence base
Sources
- An Ontology of Dark Patterns KnowledgeGray et al.; ACM CHI 2024 · Secondary · checked 2026-09-14 · DOI 10.1145/3613904.3642436; arXiv:2309.09640
- Behavioural study on unfair commercial practices in the digital environmentEuropean Commission, Directorate-General for Justice and Consumers · Secondary · checked 2026-09-14 · DOI 10.2838/859030; ISBN 978-92-76-52316-1
- 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