All Products
Search
Document Center

Cloud Firewall:Self-service unsubscription

Last Updated:Nov 06, 2025

Cloud Firewall provides self-service features that allow you to unsubscribe from or release instances as needed. This topic describes the rules and procedures for self-service unsubscription.

Before you unsubscribe

After you unsubscribe from a subscription instance or release a pay-as-you-go instance, your configuration data is retained for 7 days. This data includes access control policies, protection policies, and traffic analysis policies. This lets you re-enable the instance within 7 days. However, log analysis statistics are not retained.

Warning

After an instance is released, all data is permanently deleted after 7 days and cannot be recovered.

Refund rules for self-service unsubscription

Billing method

Refund method

Refund rule

Subscription (Premium, Enterprise, and Ultimate editions)

Cases where refunds are supported

  • If you purchased the instance within the last five days, you can submit a ticket to apply for a refund.

  • For other special cases, contact your business manager.

Cases where refunds are not supported

Refunds are not supported if you purchased the instance more than five days ago and there are no product-related issues.

Self-service release

You can manually release a subscription Cloud Firewall instance from 15 days before to 7 days after its expiration. However, no refund is provided for an early release. For more information about how to release an instance, see Release a subscription instance.

Pay-as-you-go

Self-service release

Pay-as-you-go Cloud Firewall instances are billed in real time based on usage. Therefore, refunds are not applicable. If you no longer need a pay-as-you-go Cloud Firewall instance, you can release it. Before you release the instance, make sure that you have backed up or migrated your data and that your business is not affected. For more information about how to release an instance, see Release a pay-as-you-go instance.

Billing stops immediately after the instance is released. However, the bill for a pay-as-you-go instance is generated on day T+1 after the release. Therefore, you receive the final bill on day T+1.