> For the complete documentation index, see [llms.txt](https://docs.acecloud.ai/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.acecloud.ai/knowledge-base/billing/hidden-content.md).

# Hidden Content

#### Auto-Renewal, Expiry, and Resource Lifecycle Policy

**1) Auto-Renewal Defaults and Applicability**

**Metered Resources (Hourly / Spot)**

* Auto-renewal is **ON by default** and **cannot be turned OFF**.
* Because auto-renewal cannot be disabled, **reactivation does not apply** to metered (usage-based) resources.

**Non-Metered Resources (Fixed-Term Plans: Monthly / Quarterly / Half-Yearly / Yearly)**

* Fixed-term subscriptions **auto-renew by default**.
* You may choose to **turn OFF auto-renewal.**
* If auto-renewal is OFF, the subscription will **expire at the end of its term unless renewed manually**.

**2) Subscription Expiry Notifications (Email)**

To help prevent service disruption, we send **consolidated email reminders** for subscriptions nearing expiry:

* **7 days before expiry**
* **3 days before expiry**
* **1 day before expiry**

These emails include:

* A list of expiring subscriptions
* Recommended actions to ensure uninterrupted service

**3) What Happens After Expiry (Deactivation & Restrictions)**

If a fixed-term subscription expires (for example, if auto-renewal is OFF or renewal fails):

* The resource is **deactivated**, and restrictions are applied.
* You will receive an email confirming deactivation and outlining the restrictions, including:
  * Compute instances are **shut down**
  * GPU resources are **shelved**

**4) Deletion Timeline and Notifications**

If no corrective action is taken after deactivation:

* **2 days before deletion**: An email reminder is sent notifying you of the scheduled deletion.
* **7 days after expiry**:
  * The resource has been **permanently deleted**
  * A confirmation email is sent

**5) How to Prevent or Resolve Impact**

**To Prevent Deactivation (Recommended)**

* Keep **auto-renewal ON** for fixed-term subscriptions to ensure uninterrupted service.

**To Prevent Deletion After Deactivation**

* **Reactivate the subscription** within the retention window.
  * Reactivation restores the subscription and cancels the scheduled deletion (subject to platform eligibility and successful billing).

**Billing on Reactivation**

* Reactivation may include:
  * Charges for the **deactivated period**, and
  * Charges for the **renewed subscription term**, as applicable.

**6) Resource Dependency and Automatic Renewal**

* If a resource **is dependent on another resource** and **cannot be deleted independently** (for example, a storage volume attached to a compute instance),
* That dependent resource will be **automatically renewed for the next billing cycle**, even if auto-renewal is otherwise turned OFF.
* This ensures service integrity and prevents unintended data loss or system inconsistency.