> 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/portal/profile/delete-your-devolutions-account.md).

# Delete your Devolutions Account

Permanently delete your Devolutions Account from Devolutions Portal using email, push notification, or password authorization methods.

Delete your Devolutions Account by following the steps below. Data can be [transferred](/portal/profile/change-your-devolutions-account-email-address.md) to another account before deletion.

{% hint style="danger" %}
Deleting a Devolutions Account **cannot be undone**. Once an account is deleted, it is irreversible. To understand the implications of this decision, read [How deleting Devolutions Account affects Devolutions Cloud.](https://docs.devolutions.net/cloud/knowledge-base/knowledge-base-articles/consequences-of-deleting-a-devolutions-account-on-devolutions-cloud)<br>
{% endhint %}

1. Go to the [Devolutions Portal](https://portal.devolutions.com/).
2. On the left menu, click on ***Profile***.
3. On the bottom right, select ***Delete account***.
4. Choose the method to authorize the delete process.
5. Follow the steps according to the selected method. Note that the deletion method depends on the security settings configured in your Devolutions Account and Devolutions Password Manager.
   * ***Email***: This option appears when there is no password or private key stored on Devolutions Password Manager.
   * ***Push notification***: The private key must be configured in Devolutions Password Manager to be able to delete by Push notification.
   * ***Password***: A password must be created to enable password deletion.
6. Click ***Delete Account***.
7. The account has been deleted.<br>


---

# 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/portal/profile/delete-your-devolutions-account.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.