Restricted · 2025-09AnecdotalRetentionProduct

Remind users what they lose when cancelling

List storage, features, history or workflow the user will lose, or show their own usage history, on the cancel screen.

Also called: loss aversion in cancel flow

Claim and evidence

The claimList 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.

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

Diagram, not data
User clickscancelList what theywill loseShow their ownusage historyConfirm or stay
User clicks cancelList what they will loseShow their own usage historyConfirm or stay

Loss aversion makes concrete losses weigh more than abstract benefits. Personal history raises the perceived investment.

How to run it

  1. List top 3 assets lost on cancel
  2. Show real usage stats
  3. Keep wording factual
  4. Avoid false urgency

Before / after

Before
Cancel your subscription?
Cancel subscription
Go back
Cancel confirms with no context
After
Before you go
Your cloud storage and files
Access to Pro features
Projects you created
You can cancel now; nothing changes until the period ends
Cancel subscription
Keep my plan
Factual list of what the user will lose

Generalised wireframe of the pattern, not a copy of any company's screen.

Ways to run it

Design options to test, not promised results.

  1. Option AAssets lost

    List the storage, app access and workflow the user will lose, as Adobe does.

  2. Option BPersonal history

    Show the user's own listening or viewing history, as Amazon does, keeping the wording factual.

  3. Option CNeutral tone

    State losses plainly without countdowns or false urgency, keeping the cancel button visible.

Timeline

  1. 12021 Adobe — Lists benefits users would lose (storage, app access, workflow).
  2. 22021 Amazon — Uses listening/viewing history; the author flags dark-pattern risk.
  3. 32025-09 status checked: Restricted

Dated examples

  1. 2021

    Adobe

    Lists benefits users would lose (storage, app access, workflow).

    churnkey.co · 2021-09-09

  2. 2021

    Amazon

    Uses listening/viewing history; the author flags dark-pattern risk.

    churnkey.co · 2021-09-09

Does it still work?

Restrictedas of 2025-09

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

  1. churnkey.co · Churnkey Blog · Scott Hurff · 2021-09-09

Change log

  • 2026-11-20 — harvest v0.1 (retention)