diff --git a/modules/life-cycle-deletion.adoc b/modules/life-cycle-deletion.adoc
new file mode 100644
index 0000000000..10c1ae8201
--- /dev/null
+++ b/modules/life-cycle-deletion.adoc
@@ -0,0 +1,17 @@
+// Module included in the following assemblies:
+//
+// * rosa_architecture/rosa_policy_service_definition/rosa-life-cycle.adoc
+:_mod-docs-content-type: CONCEPT
+[id="rosa-delete-policy_{context}"]
+= Deletion policy
+
+Red{nbsp}Hat reserves the right to delete {product-title} clusters within 15 days if the service notifications requiring actions are not addressed. These actions include upgrading the cluster to a supported OpenShift version or resolving cluster health issues so that the service can auto-upgrade the cluster to a supported OpenShift version.
+
+{product-title} services will notify you when the cluster is unhealthy and when the OpenShift version is approaching EOL.
+
+[IMPORTANT]
+====
+{product-title} clusters configured with delete protection enabled can still be deleted based on the deletion policy.
+====
+
+If a {product-title} cluster is deleted, any applications or business hosted on the cluster will be impacted. Additionally, cloud resources may remain in the AWS account after cluster deletion, which will continue to incur costs.
\ No newline at end of file
diff --git a/rosa_architecture/rosa_policy_service_definition/rosa-hcp-life-cycle.adoc b/rosa_architecture/rosa_policy_service_definition/rosa-hcp-life-cycle.adoc
index 281a4f4b27..8868fceb35 100644
--- a/rosa_architecture/rosa_policy_service_definition/rosa-hcp-life-cycle.adoc
+++ b/rosa_architecture/rosa_policy_service_definition/rosa-hcp-life-cycle.adoc
@@ -26,5 +26,7 @@ include::modules/life-cycle-patch-versions.adoc[leveloffset=+1]
 include::modules/life-cycle-limited-support.adoc[leveloffset=+1]
 include::modules/life-cycle-supported-versions.adoc[leveloffset=+1]
 include::modules/life-cycle-install.adoc[leveloffset=+1]
+include::modules/life-cycle-deletion.adoc[leveloffset=+1]
+
 include::modules/life-cycle-mandatory-upgrades.adoc[leveloffset=+1]
 include::modules/life-cycle-dates.adoc[leveloffset=+1]
diff --git a/rosa_release_notes/rosa-release-notes.adoc b/rosa_release_notes/rosa-release-notes.adoc
index b81aecf8da..30c44a3d67 100644
--- a/rosa_release_notes/rosa-release-notes.adoc
+++ b/rosa_release_notes/rosa-release-notes.adoc
@@ -15,12 +15,12 @@ toc::[]
 == New changes and updates
 [id="rosa-q3-2025_{context}"]
 === Q3 2025
-
 ifdef::openshift-rosa-hcp[]
+* ** New cluster deletion policy.**
+{product-title} clusters now have a new deletion policy. This policy is based on a set time period of customer non-response to service notifications. For more information, see xref:../rosa_architecture/rosa_policy_service_definition/rosa-hcp-life-cycle.adoc#rosa-delete-policy_rosa-hcp-life-cycle[Deletion policy]. For specific revised terms and conditions, refer to link:https://www.redhat.com/licenses/Appendix-4-Red-Hat-Online-Services-20250805.pdf[Product Appendix 4].
+
 * **Shared VPC for ROSA with HCP clusters.** You can create {product-title} clusters in shared, centrally-managed AWS virtual private clouds (VPCs). For more information, see xref:../rosa_hcp/rosa-hcp-shared-vpc-config.adoc#rosa-hcp-shared-vpc-config[Configuring a shared VPC for ROSA with HCP clusters].
-endif::openshift-rosa-hcp[]
 
-ifdef::openshift-rosa-hcp[]
 * **Deprecated `--private-link` flags for {product-title} clusters**. Architectural changes to the ROSA CLI 1.2.55 make networking more flexible for {product-title} clusters. The `--private-link` flag previously used when creating a {product-title} cluster is now deprecated in favor of the `--private` and `--default-ingress-private` flags. Now, users can choose to have a combination of a public or private API with a public or private ingress. For more information, see xref:../rosa_hcp/rosa-hcp-aws-private-creating-cluster.adoc#rosa-hcp-aws-private-create-cluster_rosa-hcp-aws-private-creating-cluster[Creating a private cluster on {product-title}].
 endif::openshift-rosa-hcp[]
 
@@ -39,6 +39,12 @@ If your cluster uses the OpenShift SDN network plugin, you cannot upgrade to fut
 //+
 //For more information about migrating to OVN-Kubernetes, see xref:../networking/ovn_kubernetes_network_provider/migrate-from-openshift-sdn.adoc#migrate-from-openshift-sdn[Migrating from OpenShift SDN network plugin to OVN-Kubernetes network plugin].
 //endif::openshift-rosa[]
+//remove conditional when networking book is merged
+
+ifdef::openshift-rosa[]
++
+For more information about migrating to OVN-Kubernetes, see xref:../networking/ovn_kubernetes_network_provider/migrate-from-openshift-sdn.adoc#migrate-from-openshift-sdn[Migrating from OpenShift SDN network plugin to OVN-Kubernetes network plugin].
+endif::openshift-rosa[]
 
 * **AWS Trainium and Inferentia instance types now supported.** You can now use {AWS} Trainium and Inferentia instance types for your {product-title} clusters. For more information, see
 ifdef::openshift-rosa[]