Obstruction · Australia
Account deletion obstruction
Account deletion obstruction is a working label for this design mechanism: Deleting an account is unavailable, disguised as another outcome or burdened by unnecessary barriers. This is editorial implementation guidance for Australian journeys, not a finding of unlawfulness. From 1 July 2027, a similar interface is relevant to ACL section 28B only if the complete consumer-connection, manipulation or unreasonable-distortion and actual-or-likely-detriment test is met. Current ACL rules require a separate assessment.
- 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. This is a design and research taxonomy for learning and evidence review, not a statutory offence label or an automatic finding that an interface is unlawful.
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 · 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.
Potential consumer harm: A person may reasonably believe the account and associated data were deleted when only visibility changed.
Illustrative example 2 · 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.
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 (4)
- The resulting state is only temporary deactivation, disclosed after the action.Why this state matters: 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.
- Unconfirmed state: Delete nowReview prompt: How many steps, waits and channel changes separate “Delete now” from the completed social account settings outcome?
- Each option states what remains, for how long and whether recovery is possible.Fairer design: Separate deactivation from deletion and state retention, timing, recovery and consequences before confirmation.
- Persisted account state, expanded: The saved state behind “Permanently delete account” remains consistent after refresh and across supported channels.Review prompt: Test the control across refresh, device and account states; is “The user seeks permanent account deletion” still observable after persistence is considered?
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: upcoming. Obscured outcome: upcoming
Delete your account. A direct settings route uses account authentication and explains completion timing.. Completion step: upcoming. Recorded outcome: upcoming. 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 (4)
- The form rejects users without an order number and links back to the same help article.Why this state matters: 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.
- Obscured outcome: upcomingReview prompt: How many steps, waits and channel changes separate “Enter order number” from the completed shopping account outcome?
- A direct settings route uses account authentication and explains completion timing.Fairer design: Put deletion in normal settings, require only necessary verification and offer a usable fallback for inaccessible accounts.
- Request recorded: Request deletionReview prompt: 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”?
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
How Australian law may apply
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. These harms describe a review risk, not an automatic legal conclusion. Australian section 28B commences on 1 July 2027 and requires its complete, context-specific test. Existing ACL provisions remain a separate current-law assessment.
ACL section 28B, inserted by the 2026 Act
Possible risk indicator
In account management journeys, the account deletion obstruction mechanism may warrant review where it manipulates a consumer or unreasonably distorts the decision environment and causes, or is likely to cause, detriment. The obstruction label and an interface similarity do not establish a contravention; the complete section 28B test, scope, facts and evidence must be applied from 1 July 2027.
Dark-pattern research taxonomy
Editorial analysis
The cited research sources support this working pattern within the obstruction family. It is editorial implementation guidance, not an Australian statutory category, regulator finding or legal safe harbour.
Evidence layers and open questions
Applicable law, enforcement records, policy preparation, stakeholder input, editorial analysis and unknown future details remain visibly distinct.
Final Act mappingEditorial implementation guidance
This editorial practice label is not itself an express statutory prohibition. Apply the complete provision and its scope to the facts.
Possible general-test applicationCommences 1 July 2027
ACL section 28B, inserted by the 2026 Act: In account management journeys, the account deletion obstruction mechanism may warrant review where it manipulates a consumer or unreasonably distorts the decision environment and causes, or is likely to cause, detriment. The obstruction label and an interface similarity do not establish a contravention; the complete section 28B test, scope, facts and evidence must be applied from 1 July 2027.
Existing ACLCurrent enforcement
Existing ACL provisions continue to apply on their own elements before and after commencement. The 2027 provisions must not be applied early.
Verified enforcement contextCurrent enforcement
No named pattern-specific enforcement example is asserted on this page. Existing ACL analysis remains fact-specific and separate from the 2027 provisions.
RegulationsRegulation pending
Later regulations may affect specified exclusions, matters or exceptions. That uncertainty does not postpone a core enacted rule unless the provision itself depends on prescription.
Regulator implementation materialGuidance pending
Government funding and parliamentary material anticipate regulator education and guidance. No dedicated final ACCC implementation guide is treated here as published.
Journey and evidence recommendationsEditorial implementation guidance
Offer a clear self-service deletion route, distinguish deletion from deactivation, and confirm the resulting state. This is editorial portal guidance, not a statutory duty, regulator safe harbour or compliance certificate.
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.
- Boundary to test: Legally required record retention clearly distinguished from account access
- Boundary to test: reasonable authentication
- Boundary to test: temporary technical outage with a documented recovery path
When a similar design can serve a legitimate purpose
- Legally required record retention clearly distinguished from account access
- reasonable authentication
- 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?
Evidence to retain
- Annotated account management screenshots at each responsive breakpoint
- The complete state sequence before, during and after the consumer decision
- Design-system component, content, default and configuration records for the reviewed release
- Operational records substantiating price, availability, timing and eligibility claims
- Usability, accessibility, reversal, complaint and support evidence relevant to consumer impact
- A dated product and legal review record identifying evidence, uncertainties and release decisions
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
- Competition and Consumer Amendment (Unfair Trading Practices) Act 2026Federal Register of Legislation · Primary · checked 2026-09-14 · C2026A00064
- Competition and Consumer Act 2010, including Schedule 2: Australian Consumer LawFederal Register of Legislation · Primary · checked 2026-09-14 · C2004A00109
- Unfair trading tricks and traps to be bannedTreasury Ministers · Primary · checked 2026-09-14
- Inquiry into the Competition and Consumer Amendment (Unfair Trading Practices) Bill 2026Senate Economics Legislation Committee · Primary · checked 2026-08-09