Direct answer: Flywheel cancellation is a subscription-level process that starts in Billing and is completed after the Billing Team confirms the request. On the cancellation date, the sites and backups attached to that subscription become inaccessible, while the user’s Flywheel account itself can remain.
This Flywheel guide is organized around the exact transaction rather than a generic Cancel button. “Cancellation begins in Billing” establishes the first boundary, while “Ownership controls who can cancel” establishes the second. The Flywheel scenario “Collaborator tries to cancel an individually owned Flywheel subscription” is useful because Flywheel says only the subscription owner can cancel that individually owned plan.
Flywheel decision table
| Transaction detail | Practical Flywheel effect |
|---|---|
| Cancellation begins in Billing | Flywheel directs the subscription owner to Billing, the subscription Details page, and the Cancel subscription option. |
| Ownership controls who can cancel | An individually owned subscription can be canceled by its owner, while organization-owned subscriptions can be canceled by organization members with the required access. |
| Billing Team confirmation completes the process | After the cancellation request is submitted, Flywheel says its Billing Team contacts the customer by email to confirm. |
| Sites and backups are lost on the cancellation date | Flywheel lists all sites and retained backups connected to the subscription among the items the customer loses when cancellation is processed. |
Flywheel policy checkpoints that control the outcome
Cancellation begins in Billing
For Flywheel, map the purchase record tied to “Cancellation begins in Billing.” Flywheel directs the subscription owner to Billing, the subscription Details page, and the Cancel subscription option. That Flywheel checkpoint should be read on its own terms before any account, booking, subscription, or service change is submitted.
Use “Ownership controls who can cancel” as the next Flywheel marker. An individually owned subscription can be canceled by its owner, while organization-owned subscriptions can be canceled by organization members with the required access. Compare the two Flywheel markers before acting; the matching Flywheel action here is “Identify whether the subscription belongs to an individual user or an organization.” Save the resulting Flywheel confirmation so the later outcome can be checked against both rules.
Ownership controls who can cancel
For Flywheel, reconcile the service record tied to “Ownership controls who can cancel.” An individually owned subscription can be canceled by its owner, while organization-owned subscriptions can be canceled by organization members with the required access. That Flywheel checkpoint should be read on its own terms before any account, booking, subscription, or service change is submitted.
Use “Billing Team confirmation completes the process” as the next Flywheel marker. After the cancellation request is submitted, Flywheel says its Billing Team contacts the customer by email to confirm. Compare the two Flywheel markers before acting; the matching Flywheel action here is “Download a current site backup and record DNS or migration details before canceling.” Save the resulting Flywheel confirmation so the later outcome can be checked against both rules.
Billing Team confirmation completes the process
For Flywheel, trace the transaction record tied to “Billing Team confirmation completes the process.” After the cancellation request is submitted, Flywheel says its Billing Team contacts the customer by email to confirm. That Flywheel checkpoint should be read on its own terms before any account, booking, subscription, or service change is submitted.
Use “Sites and backups are lost on the cancellation date” as the next Flywheel marker. Flywheel lists all sites and retained backups connected to the subscription among the items the customer loses when cancellation is processed. Compare the two Flywheel markers before acting; the matching Flywheel action here is “Open Billing > Details, request cancellation, and keep the request confirmation.” Save the resulting Flywheel confirmation so the later outcome can be checked against both rules.
Sites and backups are lost on the cancellation date
For Flywheel, verify the timing record tied to “Sites and backups are lost on the cancellation date.” Flywheel lists all sites and retained backups connected to the subscription among the items the customer loses when cancellation is processed. That Flywheel checkpoint should be read on its own terms before any account, booking, subscription, or service change is submitted.
Use “The Flywheel user account can remain” as the next Flywheel marker. Canceling a hosting subscription does not itself delete the Flywheel login, organizations, saved payment methods, or blueprints. Compare the two Flywheel markers before acting; the matching Flywheel action here is “Watch for the Billing Team email that confirms the cancellation date.” Save the resulting Flywheel confirmation so the later outcome can be checked against both rules.
The Flywheel user account can remain
For Flywheel, match the billing trail tied to “The Flywheel user account can remain.” Canceling a hosting subscription does not itself delete the Flywheel login, organizations, saved payment methods, or blueprints. That Flywheel checkpoint should be read on its own terms before any account, booking, subscription, or service change is submitted.
Use “Single-site deletion can expose a cancellation choice” as the next Flywheel marker. For Tiny or Starter plans, deleting the hosted site can present the option to cancel the underlying subscription; keeping the subscription allows a new site to be created later. Compare the two Flywheel markers before acting; the matching Flywheel action here is “After that date, verify the subscription is gone while preserving any separate Flywheel account assets that should remain.” Save the resulting Flywheel confirmation so the later outcome can be checked against both rules.
Single-site deletion can expose a cancellation choice
For Flywheel, audit the account history tied to “Single-site deletion can expose a cancellation choice.” For Tiny or Starter plans, deleting the hosted site can present the option to cancel the underlying subscription; keeping the subscription allows a new site to be created later. That Flywheel checkpoint should be read on its own terms before any account, booking, subscription, or service change is submitted.
Use “Cancellation begins in Billing” as the next Flywheel marker. Flywheel directs the subscription owner to Billing, the subscription Details page, and the Cancel subscription option. Compare the two Flywheel markers before acting; the matching Flywheel action here is “Identify whether the subscription belongs to an individual user or an organization.” Save the resulting Flywheel confirmation so the later outcome can be checked against both rules.
Real Flywheel situations that change the answer
Collaborator tries to cancel an individually owned Flywheel subscription
The Flywheel case “Collaborator tries to cancel an individually owned Flywheel subscription” should not be generalized. Flywheel says only the subscription owner can cancel that individually owned plan.
Its companion Flywheel checkpoint is “Billing Team confirmation completes the process”: After the cancellation request is submitted, Flywheel says its Billing Team contacts the customer by email to confirm. Keep both Flywheel details with the transaction record.
Agency cancels an organization-owned subscription
Use “Agency cancels an organization-owned subscription” as a Flywheel case study. The expected timing outcome is: An authorized organization member can use the organization billing context to request cancellation.
Now compare this Flywheel case with “Sites and backups are lost on the cancellation date.” Flywheel lists all sites and retained backups connected to the subscription among the items the customer loses when cancellation is processed. That comparison explains which Flywheel condition controls.
Customer needs a backup after the cancellation date
In “Customer needs a backup after the cancellation date,” Flywheel gives this result: Flywheel lists subscription backups among the items lost when cancellation is processed, so backup retrieval should happen first.
The Flywheel rule “The Flywheel user account can remain” adds the second test. Canceling a hosting subscription does not itself delete the Flywheel login, organizations, saved payment methods, or blueprints. Save whichever Flywheel confirmation proves the real transaction followed it.
Customer deletes the only site on a Tiny plan
For this Flywheel transaction described as “Customer deletes the only site on a Tiny plan,” expect this post-cancel outcome: Flywheel can offer the option to cancel the subscription at the same time; declining that cancellation keeps an empty subscription available for another site.
Cross-reference the Flywheel point “Single-site deletion can expose a cancellation choice.” For Tiny or Starter plans, deleting the hosted site can present the option to cancel the underlying subscription; keeping the subscription allows a new site to be created later. Do not import a different provider’s rule into this Flywheel case.
How to carry out a Flywheel cancellation or refund request
Flywheel action 1: Identify whether the subscription belongs to an individual user or an organization
For Flywheel, perform “Identify whether the subscription belongs to an individual user or an organization” only after matching the service status to “Cancellation begins in Billing.” That Flywheel rule is: Flywheel directs the subscription owner to Billing, the subscription Details page, and the Cancel subscription option.
The case “Collaborator tries to cancel an individually owned Flywheel subscription” shows how Flywheel can behave in practice: Flywheel says only the subscription owner can cancel that individually owned plan. Use this Flywheel confirmation to verify the same branch applied.
Flywheel action 2: Download a current site backup and record DNS or migration details before canceling
The Flywheel workflow now reaches “Download a current site backup and record DNS or migration details before canceling.” Record the confirmation date before completing it, because “Ownership controls who can cancel” controls this Flywheel branch.
Afterward, compare the Flywheel result with “Agency cancels an organization-owned subscription.” An authorized organization member can use the organization billing context to request cancellation. A mismatch should be documented before another Flywheel request is sent.
Flywheel action 3: Open Billing > Details, request cancellation, and keep the request confirmation
Use “Open Billing > Details, request cancellation, and keep the request confirmation” as the next Flywheel action. Pair it with the Flywheel rule “Billing Team confirmation completes the process,” especially the deadline attached to that rule.
For the example “Customer needs a backup after the cancellation date,” Flywheel lists subscription backups among the items lost when cancellation is processed, so backup retrieval should happen first. That Flywheel example gives a concrete result to compare with the completed action.
Flywheel action 4: Watch for the Billing Team email that confirms the cancellation date
Before Flywheel action 4, write down the billing owner. Then carry out “Watch for the Billing Team email that confirms the cancellation date” under this Flywheel checkpoint “Sites and backups are lost on the cancellation date.”
Use “Customer deletes the only site on a Tiny plan” as the post-action Flywheel test. Flywheel can offer the option to cancel the subscription at the same time; declining that cancellation keeps an empty subscription available for another site. Preserve the Flywheel evidence until the expected change is visible.
Flywheel action 5: After that date, verify the subscription is gone while preserving any separate Flywheel account assets that should remain
Action 5 for Flywheel is “After that date, verify the subscription is gone while preserving any separate Flywheel account assets that should remain.” Its supporting Flywheel rule is “The Flywheel user account can remain,” and the key record is the product type.
The Flywheel situation “Collaborator tries to cancel an individually owned Flywheel subscription” supplies the comparison point: Flywheel says only the subscription owner can cancel that individually owned plan. Check the completed Flywheel record against that result.
Verify the final Flywheel status
The final Flywheel audit begins with the transaction outcome, then checks “Cancellation begins in Billing.” Flywheel directs the subscription owner to Billing, the subscription Details page, and the Cancel subscription option.
Next, compare this Flywheel outcome with “Single-site deletion can expose a cancellation choice.” For Tiny or Starter plans, deleting the hosted site can present the option to cancel the underlying subscription; keeping the subscription allows a new site to be created later.
The scenario “Customer deletes the only site on a Tiny plan” provides the Flywheel reality check: Flywheel can offer the option to cancel the subscription at the same time; declining that cancellation keeps an empty subscription available for another site.
Retain both the before-change Flywheel record and the after-change Flywheel confirmation until every expected event is complete.
Flywheel transaction worksheet
Flywheel worksheet 1: Cancellation begins in Billing
Map this Flywheel checkpoint “Cancellation begins in Billing” with this Flywheel case “Agency cancels an organization-owned subscription.” The official Flywheel point is: Flywheel directs the subscription owner to Billing, the subscription Details page, and the Cancel subscription option.
For “Agency cancels an organization-owned subscription,” Flywheel gives this practical result: An authorized organization member can use the organization billing context to request cancellation. The related Flywheel action is “Open Billing > Details, request cancellation, and keep the request confirmation.” Save this Flywheel confirmation that shows which result occurred.
Flywheel worksheet 2: Ownership controls who can cancel
Pair this Flywheel checkpoint “Ownership controls who can cancel” with this Flywheel case “Customer needs a backup after the cancellation date.” The official Flywheel point is: An individually owned subscription can be canceled by its owner, while organization-owned subscriptions can be canceled by organization members with the required access.
For “Customer needs a backup after the cancellation date,” Flywheel gives this practical result: Flywheel lists subscription backups among the items lost when cancellation is processed, so backup retrieval should happen first. The related Flywheel action is “Watch for the Billing Team email that confirms the cancellation date.” Save this Flywheel confirmation that shows which result occurred.
Flywheel worksheet 3: Billing Team confirmation completes the process
Match this Flywheel checkpoint “Billing Team confirmation completes the process” with this Flywheel case “Customer deletes the only site on a Tiny plan.” The official Flywheel point is: After the cancellation request is submitted, Flywheel says its Billing Team contacts the customer by email to confirm.
For “Customer deletes the only site on a Tiny plan,” Flywheel gives this practical result: Flywheel can offer the option to cancel the subscription at the same time; declining that cancellation keeps an empty subscription available for another site. The related Flywheel action is “After that date, verify the subscription is gone while preserving any separate Flywheel account assets that should remain.” Save this Flywheel confirmation that shows which result occurred.
Flywheel worksheet 4: Sites and backups are lost on the cancellation date
Trace this Flywheel checkpoint “Sites and backups are lost on the cancellation date” with this Flywheel case “Collaborator tries to cancel an individually owned Flywheel subscription.” The official Flywheel point is: Flywheel lists all sites and retained backups connected to the subscription among the items the customer loses when cancellation is processed.
For “Collaborator tries to cancel an individually owned Flywheel subscription,” Flywheel gives this practical result: Flywheel says only the subscription owner can cancel that individually owned plan. The related Flywheel action is “Identify whether the subscription belongs to an individual user or an organization.” Save this Flywheel confirmation that shows which result occurred.
What to save for this Flywheel transaction
- Flywheel original receipt, ticket, invoice, booking, or membership record
- Flywheel policy checkpoint “Cancellation begins in Billing” with the date that makes it relevant
- Flywheel billing or issuing channel tied to the transaction
- Flywheel cancellation, downgrade, return, or booking-change confirmation
- Flywheel effective end date or next controlling date
- Flywheel refund, credit, fee, or equipment-return reference when the policy creates one
Flywheel cancellation and refund FAQ
How does “Cancellation begins in Billing” affect a Flywheel cancellation?
Flywheel publishes this rule: Flywheel directs the subscription owner to Billing, the subscription Details page, and the Cancel subscription option. Compare that Flywheel rule with “Collaborator tries to cancel an individually owned Flywheel subscription,” where Flywheel says only the subscription owner can cancel that individually owned plan.
How does “Ownership controls who can cancel” affect a Flywheel cancellation?
Flywheel publishes this rule: An individually owned subscription can be canceled by its owner, while organization-owned subscriptions can be canceled by organization members with the required access. For a concrete Flywheel example, “Agency cancels an organization-owned subscription” means: An authorized organization member can use the organization billing context to request cancellation.
How does “Billing Team confirmation completes the process” affect a Flywheel cancellation?
Flywheel publishes this rule: After the cancellation request is submitted, Flywheel says its Billing Team contacts the customer by email to confirm. The Flywheel scenario “Customer needs a backup after the cancellation date” narrows the answer: Flywheel lists subscription backups among the items lost when cancellation is processed, so backup retrieval should happen first.
How does “Sites and backups are lost on the cancellation date” affect a Flywheel cancellation?
Flywheel publishes this rule: Flywheel lists all sites and retained backups connected to the subscription among the items the customer loses when cancellation is processed. Use the Flywheel situation “Customer deletes the only site on a Tiny plan” as the cross-check: Flywheel can offer the option to cancel the subscription at the same time; declining that cancellation keeps an empty subscription available for another site.
How does “The Flywheel user account can remain” affect a Flywheel cancellation?
Flywheel publishes this rule: Canceling a hosting subscription does not itself delete the Flywheel login, organizations, saved payment methods, or blueprints. In Flywheel practice, “Collaborator tries to cancel an individually owned Flywheel subscription” adds this result: Flywheel says only the subscription owner can cancel that individually owned plan.
How does “Single-site deletion can expose a cancellation choice” affect a Flywheel cancellation?
Flywheel publishes this rule: For Tiny or Starter plans, deleting the hosted site can present the option to cancel the underlying subscription; keeping the subscription allows a new site to be created later. The Flywheel case “Agency cancels an organization-owned subscription” gives the practical check: An authorized organization member can use the organization billing context to request cancellation.
Which Flywheel records are worth keeping after the request?
Keep the original Flywheel transaction record, the effective change date, and the final Flywheel confirmation. Store any approved Flywheel refund, credit, fee, or return reference with the payment or booking record.
What changes when a third party controls this Flywheel transaction?
Use this Flywheel source that assigns responsibility to the app store, travel agent, property, club, or other biller. The correct Flywheel route is the one that reaches the party that actually issued the charge, booking, or ticket.
Related RefundGuides pages for Flywheel readers
For Flywheel, these existing RefundGuides pages provide nearby website hosting navigation. They are supporting context only; the linked official Flywheel policy controls the transaction described here.
- Webflow Site Plan Cancellation Guide: Downgrade Timing and Refund Rules
- Bluehost Cancellation & Refund Guide: 30-Day Guarantee, Domains, Renewals and Add-Ons
- Wix Premium Plan Cancellation & Refund Guide: 14-Day Window, Renewals and Separate Services
Official Flywheel sources checked on 2026-09-15
Official Flywheel documentation below was checked on 2026-09-15. Recheck the applicable Flywheel source before a later purchase or cancellation because the controlling terms can change.