Dark-pattern family · 5 patterns

Sneaking

Hides, disguises or delays material consequences so that the user takes an action they may otherwise reject.

This family groups related interface mechanisms for learning and journey review. It is not a legal category and does not make every matching interface unlawful. Start with the mechanism, then examine the complete decision, audience, effect and EU rule actually within scope.

Explore the 5 patternsBrowse the 10 individual examples

Recognition framework

How to review sneaking.

Reconstruct what the user selected, what the interface represented and what the transaction ultimately created. Diff basket, contract, price and renewal state after every material interaction. Pay special attention to recalculation, trial conversion and situations where silence or failure is interpreted as agreement.

Recognition signals

  • A material cost, product or recurring consequence appears after the relevant choice.
  • The interface produces a different commercial outcome from the action represented.
  • Silence, an ineffective refusal or an unrelated interaction is treated as authorisation.

Decision points

  • The first representation of product, price and contract type
  • Each basket or state mutation not initiated by a clear add action
  • The final payable and recurring consequences
  • Persistence of removal, refusal and opt-out states

Fair-design principles

  • Require a deliberate specific action for every paid or recurring consequence.
  • Show foreseeable total cost and contract type before commitment.
  • Preserve removals and refusals across recalculation, channel and lifecycle changes.

Evidence to retain

  • Screen-to-cart and cart-to-order state diffs
  • Price, fee and subscription configuration
  • Removal and refusal persistence tests
  • Order, billing and immediate-reversal records

Boundary to keep visible

A price can change or availability can require a new choice, but the changed outcome should be disclosed and deliberately confirmed. Automatic technical recalculation is not a substitute for assent to a new item, subscription or charge.

EU legal and policy context

Keep taxonomy, current law and the announced DFA process separate.

A family name helps teams compare interface mechanisms. It is not an EU legal category, and similarity to an example does not establish that a current rule has been infringed or that a future Digital Fairness Act will use the same label.

Current-law context

The UCPD and any relevant sector instrument require their own scope, conduct, information and likely-effect assessment. The complete journey and evidence matter; a taxonomy match is only a prompt to investigate.

Officially announced

The Commission is preparing a legislative DFA initiative and currently places a proposal in Q4 2026. That planning date is indicative, and no published proposal yet creates a family-specific duty.

Under consideration

The call for evidence discusses possible policy responses to digital fairness concerns. Options, consultation questions and stakeholder submissions are not Commission proposals or present obligations.

Still unknown

Final instrument form, scope, definitions, thresholds, enforcement, transition and application remain unknown until primary legislative text is published and validated.

Open the current-law mapCheck the verified timeline

Journey coverage

Where sneaking can become visible.

Review the state before the decision, the controls and information available at that moment, the immediate result and any later account or billing consequence. Journey links below show where this family appears in the published taxonomy; they do not imply that every product or every stage contains the mechanism.

1 related pattern

Account Management

Account settings determine whether earlier choices remain controllable. Privacy preferences, exports, deletion, support and content controls often span several channels and states. Review therefore needs to test persistence and actual system outcomes, not only whether a settings label or help article exists.

Open the journey guide →

4 related patterns

Checkout

Checkout concentrates price, add-ons, urgency, identity and the final payment action. Review should begin with the state carried into the basket and finish only when the order, receipt and account state agree. A control that appears clear in isolation can still be misleading when a fee arrives late, a removed item returns or the final button does more than its label predicts.

Open the journey guide →

1 related pattern

Pricing

Pricing review starts before checkout. Search cards, campaign landing pages, recommendation logic, comparison tables and membership offers can each shape the price a person understands. Teams should reconstruct the comparable payable amount, the basis of every saving or popularity claim and the information available when a product first becomes a realistic option.

Open the journey guide →

3 related patterns

Subscription

A subscription is a lifecycle rather than one purchase screen. Trial conversion, billing period, renewal, plan changes and continued access must be understood together. The interface should enable a person to distinguish a one-off payment from a recurring arrangement and compare the present benefit with later price and exit consequences.

Open the journey guide →

1 related pattern

Cancellation

Cancellation review compares the represented exit with the steps, channels and final account state needed to complete it. Legitimate identity or account-protection controls can add proportionate friction, but retention prompts, language and technical dead ends should not prevent a clear instruction from reaching a durable outcome.

Open the journey guide →

Pattern directory

Explore every sneaking pattern.

Each detail page contains two fictional interface comparisons, practical recognition and exclusion criteria, a fairer alternative, review questions and a legal-status map that keeps editorial taxonomy separate from current law and the announced DFA process.

Editorial analysisSneaking

Bait and switch

The user selects a represented action or offer but receives a materially different outcome that favours the business. 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.

  • Account Management
  • Checkout

2 visual examples

See visual examples
Current lawSneaking

Drip pricing and hidden charges

A mandatory or foreseeable charge is omitted, obscured or revealed only after the user has invested effort in the transaction. 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.

  • Pricing
  • Checkout
  • Subscription

2 visual examples

See visual examples
Editorial analysisSneaking

Hidden subscription or forced continuity

A transaction creates or continues recurring liability without effective, timely disclosure of the subscription, renewal and exit consequences. 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.

  • Subscription
  • Checkout

2 visual examples

See visual examples
Editorial analysisSneaking

Negative option or unauthorised transaction

Silence, inactivity or an ineffective prior interaction is treated as authorisation for a paid or consequential transaction. 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.

  • Subscription
  • Cancellation

2 visual examples

See visual examples
Editorial analysisSneaking

Sneak into basket

A paid or consequential item is added to a basket or transaction without a clear, deliberate and specific user 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.

  • Checkout

2 visual examples

See visual examples

Evidence-led workflow

Turn a visual signal into a reviewable record.

  1. Reproduce the complete decision path and preserve each material state, option, disclosure, default and price before and after the action.
  2. Check the pattern’s inclusion criteria and legitimate-use boundaries instead of classifying from appearance alone.
  3. Verify the operating facts behind timing, stock, ranking, price, consent and account state, and record what evidence would falsify the initial concern.
  4. Apply current law, announced preparation, matters under consideration and unknown future details as separate layers with dated sources.

Evidence base

Sources

  1. Dark commercial patternsOrganisation for Economic Co-operation and Development · Secondary · checked 2026-09-14 · OECD Digital Economy Papers No. 336
  2. Unfair Commercial Practices DirectiveEuropean Parliament and Council of the European Union · Primary · checked 2026-08-09 · Directive 2005/29/EC; CELEX 02005L0029-20220528
  3. Consumer Rights DirectiveEuropean Parliament and Council of the European Union · Primary · checked 2026-08-09 · Directive 2011/83/EU; CELEX 02011L0083-20220528
  4. Digital Fairness Act: call for evidence for an impact assessmentEuropean Commission · Primary · checked 2026-08-09 · Initiative 14622; Ares(2025)6275573
  5. An Ontology of Dark Patterns KnowledgeGray et al.; ACM CHI 2024 · Secondary · checked 2026-09-14 · DOI 10.1145/3613904.3642436; arXiv:2309.09640
  6. Review of EU consumer lawEuropean Commission, Directorate-General for Justice and Consumers · Primary · checked 2026-09-14
  7. Commission work programme 2026: Europe's Independence MomentEuropean Commission · Primary · checked 2026-09-14 · COM(2025) 870 final; CELEX 52025DC0870; Annex I item 30