Renewal, cancellation, and data
Pro renews through Stripe until you cancel. Cancelling stops future renewal, deleting the instance is separate, and data is removed after the node job.
How renewal works
Pro is a subscription collected by Stripe. Foxcore records the plan after the processor confirms it, usually through the billing webhook. The subscription renews on the processor’s schedule until you cancel it.
The panel does not store a separate price for a game title or a VPS. One Pro subscription covers the instance, and the size you chose is the memory and CPU cap. Tax, where the law requires it, is added by the processor.
Cancelling
Open Account → Settings → Billing and use Manage billing to reach the customer portal. Cancellation stops future renewal. If you cancel at period end, the page lists that date. When the paid period ends, the account falls back to Starter.
Cancelling does not destroy an instance. Your files stay until you delete the instance or the account, subject to the retention rules in the privacy policy.
- Open Account → Settings → Billing.
- Use Manage billing to open the customer portal.
- Cancel the subscription and note the period-end date.
- Export anything you need before you destroy the instance.
Deleting an instance
Destroy is an instance action, not a billing action. It removes the instance from Services after the destroy job finishes. Node-local files and backups are removed when the node completes that job.
If you still need the volume, do not destroy the instance. Stop it instead; a stopped instance keeps its files and its join host.
Invoices and payment problems
The customer portal holds cards, invoices, and cancellation. If a payment fails, the processor reports the status and Foxcore shows it on Billing. Support cannot take a card number in a ticket and does not need one.
If checkout is unavailable because the processor is not configured, Pro cannot be started; Starter stays in force. Nodes never talk to the processor.