Journey guide · 11 related patterns

Dark patterns in 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.

The patterns below are review prompts, not automatic findings. A useful journey review keeps ordinary persuasive design, usability problems, current legal tests and possible future DFA policy separate while preserving the evidence needed to examine each question.

Review the complete sequence

Decision points and signals.

Capture the state before a material choice, the controls and information available at that choice, the immediate result and any later account or billing consequence. This prevents a clear-looking screen from being assessed without the steps that give it practical effect.

Decision points

  • Finding and changing privacy, communication and attention controls
  • Exporting data, deleting an account and recovering from errors
  • Whether choices persist across devices, apps and later sessions
  • How self-service hands off to support when the normal route cannot complete

Review signals

  • Related controls use inconsistent names or live in disconnected menus
  • A represented deletion, refund or preference action does not change backend state
  • A form loops, loses progress or requires information irrelevant to the request
  • Optional attention, referral or disclosure requests block an earned account function

Fair-design principles

  • Provide one coherent overview of material account states and controls
  • Make the represented action and resulting backend state agree
  • Persist preferences across channels and disclose conflicts before changing them
  • Preserve progress and offer an accessible fallback with a case reference

Evidence to retain

  • Navigation map from account home to each material control
  • Frontend-to-backend state assertions and confirmation records
  • Cross-device preference and deletion tests
  • Support handoff, error recovery and accessibility findings

Pattern directory

Patterns that can appear during account management.

Journey tags identify where a mechanism may be observable; they do not mean it appears in every product or only at that stage. Follow the detail links for two concrete comparisons, boundary cases, legal context and evidence questions.

Editorial analysisObstruction

Account deletion obstruction

Deleting an account is unavailable, disguised as another outcome or burdened by unnecessary barriers. 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

2 visual examples

See examples in context: Account deletion obstruction
Editorial analysisForced action

Automatic attention capture

Content continues automatically or lacks meaningful stopping cues, reducing deliberate control over time and attention. 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
  • Pricing

2 visual examples

See examples in context: Automatic attention capture
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 examples in context: Bait and switch
Current lawObstruction

Cancellation friction

Ending an existing subscription, recurring service or permission is made difficult to find or complete through unnecessary steps or channel asymmetry. 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
  • Account Management
  • Cancellation

2 visual examples

See examples in context: Cancellation friction
Editorial analysisForced action

Contact harvesting and coerced referrals

The service extracts contact information, sends or prepares unwanted invitations, or ties functionality to recruiting other people. 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.

  • Signup
  • Account Management

2 visual examples

See examples in context: Contact harvesting and coerced referrals
Editorial analysisObstruction

Customer-support obstruction

Access to support needed to resolve a purchase, account, charge or right is hidden or burdened by unnecessary loops and dead ends. 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
  • Pricing

2 visual examples

See examples in context: Customer-support obstruction
Editorial analysisObstruction

Dead end

A consumer-favourable route cannot reach its represented outcome and instead loops, stalls or loses progress. 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
  • Cancellation

2 visual examples

See examples in context: Dead end
Editorial analysisInterface interference

Feedforward ambiguity

A control does not let the user reasonably predict its material outcome before activation. 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
  • Account Management

2 visual examples

See examples in context: Feedforward ambiguity
Editorial analysisForced action

Gamified or paid access coercion

Desired functionality is practically conditioned on repetitive engagement or an additional payment not sufficiently clear at acquisition. 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

2 visual examples

See examples in context: Gamified or paid access coercion
Current lawInterface interference

Preselection and defaults

A business-favoured option with a plausible adverse consequence is active before a deliberate 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.

  • Signup
  • Checkout
  • Subscription
  • +1

2 visual examples

See examples in context: Preselection and defaults
Editorial analysisObstruction

Privacy maze

Privacy controls are fragmented, inconsistently labelled or layered so that limiting collection or use is unnecessarily difficult. 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

2 visual examples

See examples in context: Privacy maze

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. Digital Services ActEuropean Parliament and Council of the European Union · Primary · checked 2026-08-09 · Regulation (EU) 2022/2065; CELEX 32022R2065
  4. Consumer Rights DirectiveEuropean Parliament and Council of the European Union · Primary · checked 2026-08-09 · Directive 2011/83/EU; CELEX 02011L0083-20220528
  5. Digital Fairness Act: call for evidence for an impact assessmentEuropean Commission · Primary · checked 2026-08-09 · Initiative 14622; Ares(2025)6275573
  6. An Ontology of Dark Patterns KnowledgeGray et al.; ACM CHI 2024 · Secondary · checked 2026-09-14 · DOI 10.1145/3613904.3642436; arXiv:2309.09640
  7. General Data Protection RegulationEuropean Parliament and Council of the European Union · Primary · checked 2026-08-09 · Regulation (EU) 2016/679; CELEX 32016R0679
  8. 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