> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/cloud/knowledge-base/knowledge-base-articles/devolutions-cloud-account-deletion.md).

# Devolutions Cloud account deletion

Learn how to delete a Devolutions Cloud account from the Devolutions Portal and the notification timeline before permanent deletion occurs.

If you are the owner of a Devolutions Cloud account and want to delete it, sign in to the Devolutions Portal and open the ***Products*** section. Click the three dots (options menu) next to the Devolutions Cloud account, and then select ***Delete***.

When the Devolutions Cloud account is deleted, the associated domain remains reserved for 30 days.

The deletion process is triggered when all licenses have expired and the Devolutions Cloud has been inactive for three consecutive years.

* **30 days before deletion**: A notification email is sent to all administrators.
* **1 day before deletion**: A reminder email is sent to all administrators.
* **On the day of deletion**: The Devolutions Cloud is deleted.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devolutions.net/cloud/knowledge-base/knowledge-base-articles/devolutions-cloud-account-deletion.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.