Cancellation flow
Cancellation flow covers how subscription services are closed according to published Billing terms. It defines timing, processing, and data-handling behavior after cancellation.
Cancellation scope
Subscription cancellation
Allowed any time with effect at end of current paid cycle
No cancellation fee or exit penalty
Cancellation requests are processed within 1 business day
Project termination assumptions
No retroactive cancellation after renewal date
No mid-cycle refund for unused subscription days
No automatic waiver of outstanding invoice obligations
Execution sequence
01
Submit request by email
Include account details and exact service to cancel (Host, Care, etc.).
02
Receive confirmation
Cancellation is confirmed in writing within one business day.
03
Service runs to cycle end
Access remains active until current paid period completes.
04
Post-cycle closure
Renewal stops; any service-specific data handling rules begin.
Continuity checklist
- For Kernel Host cancellation, request backup export before cutoff; data retention is 14 days post-cancellation.
- After 14 days (Kernel Host), associated data may be permanently deleted.
- If only Kernel Care is cancelled, maintenance stops but Kernel Host stays active unless cancelled separately.
Timing reminderSubmit cancellation before renewal date. Requests submitted after renewal cannot be applied retroactively to that cycle.