Claim and evidence
List storage, features, history or workflow the user will lose, or show their own usage history, on the cancel screen.
No dated example yet. Treat this tactic as a hypothesis.
Anecdotal
Practitioner experience without published numbers.
Restricted · 2025-09 Manipulative variants face scrutiny after the FTC's $2.5B Amazon Prime settlement (Sept 2025).
What the numbers show
No published number for this tactic has passed our word-for-word check yet, so there is no chart.
Why it works
Loss aversion makes concrete losses weigh more than abstract benefits. Personal history raises the perceived investment.
How to run it
- List top 3 assets lost on cancel
- Show real usage stats
- Keep wording factual
- Avoid false urgency
Before / after
Generalised wireframe of the pattern, not a copy of any company's screen.
Ways to run it
Design options to test, not promised results.
- Option AAssets lost
List the storage, app access and workflow the user will lose, as Adobe does.
- Option BPersonal history
Show the user's own listening or viewing history, as Amazon does, keeping the wording factual.
- Option CNeutral tone
State losses plainly without countdowns or false urgency, keeping the cancel button visible.
Timeline
- 12021 Adobe — Lists benefits users would lose (storage, app access, workflow).
- 22021 Amazon — Uses listening/viewing history; the author flags dark-pattern risk.
- 32025-09 status checked: Restricted
Dated examples
- 2021
- 2021
Does it still work?
Manipulative variants face scrutiny after the FTC's $2.5B Amazon Prime settlement (Sept 2025). source
Risks
- Can drift into dark patterns
- Regulatory exposure
Sources
Change log
- 2026-11-20 — harvest v0.1 (retention)