Obstruction · European Union
Account deletion obstruction
The label “Account deletion obstruction” describes this recurring design mechanism: deleting an account is unavailable, disguised as another outcome or burdened by unnecessary barriers. 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
- Obstruction
- Also known as
- Journey stages
Definition
What is this pattern?
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.
How it works
Deleting an account is unavailable, disguised as another outcome or burdened by unnecessary barriers. The deletion route is hidden, delayed or conditioned on unnecessary information even after the user has authenticated and stated the irreversible account outcome.
Warning signs
- The user seeks permanent account deletion.
- The observed route is missing, materially harder than account creation or produces only deactivation without clear disclosure.
- The account persists after apparent completion or the journey cannot complete.
Potential harms
- A person may reasonably believe the account and associated data were deleted when only visibility changed.
- People may be unable to exercise the represented account control because of irrelevant information and route barriers.
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 · Social account settings
A fictional platform labels a control “Delete account”, but the confirmation only hides the profile and leaves data and reactivation available indefinitely.
Potential consumer harm: A person may reasonably believe the account and associated data were deleted when only visibility changed.
Illustrative example 2 · Shopping account
A fictional retailer places account deletion behind six help pages and requires a support ticket containing an order number even for users who never ordered.
Potential consumer harm: People may be unable to exercise the represented account control because of irrelevant information and route barriers.
Deactivation presented as deletion
A fictional platform labels a control “Delete account”, but the confirmation only hides the profile and leaves data and reactivation available indefinitely.
Delete account. The resulting state is only temporary deactivation, disclosed after the action.. Delete now. Unconfirmed state: Delete now
Choose deactivation or deletion. Each option states what remains, for how long and whether recovery is possible.. Permanently delete account. Saved state: Permanently delete account. Persisted account state, expanded: The saved state behind “Permanently delete account” remains consistent after refresh and across supported channels.
Why the first version can mislead: The route adds avoidable effort between the user’s stated intention and completion. In this social account settings example, the obstacle is: “The resulting state is only temporary deactivation, disclosed after the action.” Evidence should show whether the alternative remains usable and whether “Permanently delete account” reaches the represented state. A person may reasonably believe the account and associated data were deleted when only visibility changed.
What a fairer design does: Separate deactivation from deletion and state retention, timing, recovery and consequences before confirmation.
Show annotated differences (2)
- Unconfirmed state: Delete nowIn “Deactivation presented as deletion”, this element shows how account deletion obstruction can shape the decision.
- Persisted account state, expanded: The saved state behind “Permanently delete account” remains consistent after refresh and across supported channels.In “Deactivation presented as deletion”, this element keeps the clearer alternative visible at the same decision point.
Review questions (3)
- How many steps, waits and channel changes separate “Delete now” from the completed social account settings outcome?
- Test the control across refresh, device and account states; is “The user seeks permanent account deletion” still observable after persistence is considered?
- Measure the same task through the clearest available route: does the effort difference persist once “Legally required record retention clearly distinguished from account access” is accounted for?
Deletion buried behind an unsupported ticket
A fictional retailer places account deletion behind six help pages and requires a support ticket containing an order number even for users who never ordered.
Contact support to delete. The form rejects users without an order number and links back to the same help article.. Blocking step: Enter order number: current. Obscured outcome: Request deletion: current
Delete your account. A direct settings route uses account authentication and explains completion timing.. Completion step: Request deletion: completed. Recorded outcome: Enter order number: completed. Request recorded: Request deletion
Why the first version can mislead: The route adds avoidable effort between the user’s stated intention and completion. In this shopping account example, the obstacle is: “The form rejects users without an order number and links back to the same help article.” Evidence should show whether the alternative remains usable and whether “Request deletion” reaches the represented state. People may be unable to exercise the represented account control because of irrelevant information and route barriers.
What a fairer design does: Put deletion in normal settings, require only necessary verification and offer a usable fallback for inaccessible accounts.
Show annotated differences (2)
- Obscured outcome: Request deletion: currentIn “Deletion buried behind an unsupported ticket”, this element shows how account deletion obstruction can shape the decision.
- Request recorded: Request deletionIn “Deletion buried behind an unsupported ticket”, this element keeps the clearer alternative visible at the same decision point.
Review questions (3)
- How many steps, waits and channel changes separate “Enter order number” from the completed shopping account outcome?
- Count steps, waits, offers and channel changes through final confirmation; where does the route meet “The observed route is missing, materially harder than account creation or produces only deactivation without clear disclosure”?
- Measure the same task through the clearest available route: does the effort difference persist once “reasonable authentication” is accounted for?
What is a fairer alternative?
Offer a clear self-service deletion route, distinguish deletion from deactivation, and confirm the resulting state.
Legal and information status
Legal position at a glance
Deleting an account is unavailable, disguised as another outcome or burdened by unnecessary barriers. The deletion route is hidden, delayed or conditioned on unnecessary information even after the user has authenticated and stated the irreversible account outcome. 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 “Account deletion obstruction” 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 account deletion obstruction 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 account deletion obstruction. Those details remain unknown pending primary legislative text.
Context matters
Context and boundary cases
- The user seeks permanent account deletion.
- The observed route is missing, materially harder than account creation or produces only deactivation without clear disclosure.
- The account persists after apparent completion or the journey cannot complete.
- Exclude or qualify the label where legally required record retention clearly distinguished from account access.
- Exclude or qualify the label where reasonable authentication.
- Exclude or qualify the label where temporary technical outage with a documented recovery path.
When a similar design can serve a legitimate purpose
- A similar design should not be classified this way where legally required record retention clearly distinguished from account access.
- A similar design should not be classified this way where reasonable authentication.
- A similar design should not be classified this way where temporary technical outage with a documented recovery path.
Operational review
What teams should review
- Teams
- How many steps, waits and channel changes separate “Delete now” from the completed social account settings outcome?
- Test the control across refresh, device and account states; is “The user seeks permanent account deletion” still observable after persistence is considered?
- Measure the same task through the clearest available route: does the effort difference persist once “Legally required record retention clearly distinguished from account access” is accounted for?
- How many steps, waits and channel changes separate “Enter order number” from the completed shopping account outcome?
- Count steps, waits, offers and channel changes through final confirmation; where does the route meet “The observed route is missing, materially harder than account creation or produces only deactivation without clear disclosure”?
- Measure the same task through the clearest available route: does the effort difference persist once “reasonable authentication” is accounted for?
- Which complete journey evidence supports or contradicts the account deletion obstruction classification?
Evidence to retain
- Versioned captures of the Account Management states before, during and after the relevant decision
- Configuration, content and event records supporting the observed account deletion obstruction mechanism
- Responsive, keyboard and assistive-technology review of every material option and consequence
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