Renewal and cancellation FAQ

Automatic renewal is attempted during the final 24 hours before an active server's paid-through time. Processing runs periodically, so the debit is not guaranteed at one exact minute. A successful renewal extends service from the previous paid-through timestamp. Keep enough spendable ledger balance before the 24-hour window begins rather than waiting for the final minutes of the term.

A successful weekly renewal extends service by seven days. A successful monthly renewal extends it by exactly 30 days, not to the matching calendar date in the next month. The extension is added to the previous paid-through timestamp rather than the processing time. The renewal debit uses the unit price and discount recorded for that server's order.

If the ledger cannot cover the renewal, no successful renewal debit is recorded. The server remains within its paid term only until the existing paid-through timestamp. At expiry, its recorded state changes to Suspended, a grace deadline is set 72 hours later, and a power-off request is queued. Queued confirms receipt of that request, not physical completion.

The 72-hour grace period is a limited recovery window after the paid term expires. It is not an extra free rental period or a refund entitlement. The server is recorded as Suspended and a power-off request is queued. There is no customer power-on button. Keep current independent backups rather than assuming console or disk access will remain available throughout grace.

If enough spendable ledger balance is available before the grace deadline, automatic renewal can be retried. A successful debit returns the recorded server state to Active, extends paid-through from the previous expiry by seven or 30 days, and queues an internal power-on request. That queued request does not confirm physical recovery. Live deposits must also be enabled before new crypto funding can arrive.

When grace ends, the server record changes from Suspended to Reclaiming, automatic renewal is disabled, and a secure-wipe request is queued. Wipe progress and physical completion are not shown yet. Treat the grace deadline as the final point for recovery planning and assume that later data access will not be available. Keep independent backups before the paid term expires.

Not yet. New rentals have automatic renewal enabled, but there is no customer control for turning it off. The public contact form can record a request, although the account handle entered there does not authenticate ownership and request tracking is not available. Submit any enquiry well before the final 24-hour renewal window and do not assume the setting changed unless it is explicitly confirmed.

Not yet. There is no self-service cancellation or early-termination control. Weekly and 30-day monthly terms are prepaid. The Refund Policy states that a provisioned rental is generally non-refundable except where required by law or when the ordered configuration cannot be delivered and no substitute is agreed. You may record an enquiry through the contact form, but an immediate stop, credit, or refund is not guaranteed.

If provisioning fails, the Refund Policy says the order debit should be reversed with a separate ledger entry rather than deleting or editing the original debit. Automatic physical-failure detection and automatic reversal are not available yet. Keep the order reference and use the contact form to request review. A Queued provisioning state alone does not establish either successful delivery or confirmed failure.

Unused cleared ledger balance may be requested for withdrawal in a cryptocurrency previously used to fund the account. Submission places a hold for the requested USD amount and enters manual review. Network fees may reduce the amount sent under the policy. This is separate from refunding a completed rental term. Withdrawal completion tracking and a guaranteed sending time are not available yet.