After cancellation, customers need to know what they can still do. “Your plan is cancelled” does not explain whether they can read old work, export data, finish a queued task, or sign in to billing history.
Describe remaining rights as concrete actions with dates where needed. Keep that explanation tied to the same entitlement policy the server enforces.
Separate scheduled cancellation from ended service
A customer who stops renewal may retain access through the paid period. A customer whose period has ended may have a different set of rights. Show the effective date and avoid using the same vague disabled state for both.
For Stripe integrations, consult the current cancellation documentation for supported timing. The provider's subscription state is an input to the product's rights model, not a complete customer explanation by itself.
Design a fictional cancelled research workspace
Suppose the policy permits reading and export after paid creation ends, with a separate retention schedule. The cancellation page lists what remains available: view existing studies, review saved responses, download an export, and access billing history. It also states that publishing new paid studies is unavailable.
Test each listed action before and after the effective date. Try a direct request for a blocked action and a legitimate export for existing work. Inspect queued processing that spans the boundary and define whether it completes under the prior accepted entitlement.
If export availability ends later, show that date separately. Do not imply the customer can export indefinitely when generated links or account access expire sooner.
Make restoration and support understandable
If reactivation is supported, explain which plan or purchase restores which capabilities. A new purchase should not silently merge accounts or recreate deleted resources. If data has already been removed under policy, do not promise restoration without evidence.
Keep support reachable for customers who cannot complete the intended next action. Give staff enough reference information to distinguish expired access, missing entitlement, and a technical error without requesting private content unnecessarily.
The tradeoff is concise messaging versus lifecycle accuracy. A short notice can work when the policy is simple. More complex products may need an action table, but it should use customer tasks rather than internal provider status names.
The StackFlight product account describes individually paid study access. This cancelled-subscription workspace is fictional and should not be read as that product's current commercial terms.
Questions about post-cancellation access
Should cancelled users still sign in?
That depends on the policy, but sign-in may be necessary for billing, support, or permitted exports. Separate identity from paid operations.
Does cancellation delete data?
Not inherently. Data retention and deletion require their own explicit lifecycle, communication, and implementation checks.
What should be reviewed before release?
Compare every promised remaining action with server behaviour and effective dates. Bring inconsistencies to a customer-access review.